RHEL 9: Apache httpd Returns 403 Forbidden

📖 ~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

Site responds but returns 403, often after content move or vhost changes.

Environment & Reproduction

Run `apachectl -t`, inspect `Directory` blocks, and test file access paths.

Root Cause Analysis

Verify `httpd` modules and versions with `rpm -qa | grep ^httpd`.

Quick Triage

Check `systemctl status httpd` and confirm it binds expected sockets.

Step-by-Step Diagnosis

Use `journalctl -u httpd -b` and access/error logs for deny reasons.

Solution – Primary Fix

Correct directory directives, UNIX permissions, and apply `restorecon -Rv` for web roots.

Solution – Alternative Approaches

Ensure `firewalld` allows `http`/`https` and routes traffic to the host.

Verification & Acceptance Criteria

Keep enforcing mode; adjust contexts or booleans instead of disabling SELinux.

Rollback Plan

Reload httpd and reboot to confirm stable access across restarts.

Prevention & Hardening

Use deployment scripts that set ownership and context consistently.

Related Errors & Cross-Refs

Revert last vhost/content permission changes from versioned backup.

Related tutorial: View the step-by-step tutorial for rhel-9.

View all rhel-9 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Review Apache authorization model and RHEL SELinux web policy docs.