FreeBSD 13 Apache httpd Permission Denied on Document Root

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Apache on FreeBSD 13 can fail serving content when filesystem permissions do not match runtime user access.

Environment & Reproduction

HTTP 403 errors occur, and error_log reports permission denied for document root files.

Root Cause Analysis

Incorrect owner/group, restrictive modes, missing execute bit on parent directories, or jail path mismatch.

Quick Triage

Run namei -l on document root path, inspect httpd.conf Directory directives, and check error logs.

Step-by-Step Diagnosis

Confirm runtime user and group used by Apache worker processes. image_ref=0

Solution – Primary Fix

Set ownership and modes appropriately, adjust Directory Require rules, then service apache24 restart. image_ref=1

Solution – Alternative Approaches

Persist startup with sysrc apache24_enable=”YES” and manage daemon lifecycle with service apache24.

Verification & Acceptance Criteria

Keep vhost and directory policies explicit and avoid permissive global overrides.

Rollback Plan

Verify pf pass rules for web ports and backend connectivity if reverse proxy is involved.

Prevention & Hardening

Use curl -I and browser checks to confirm expected content and status codes are restored.

Related Errors & Cross-Refs

Audit permissions during deployments and monitor web logs for recurring access denials.

Related tutorial: View the step-by-step tutorial for freebsd-13.

View all freebsd-13 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

See Apache official docs, FreeBSD package guidance, and filesystem permissions references.