RHEL 9: Cockpit Web Console Not Reachable

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

Browser cannot load Cockpit on port 9090, or connection is refused/timeouts occur.

Environment & Reproduction

Run `systemctl status cockpit.socket` and verify listener with `ss -tulpen | grep 9090`.

Root Cause Analysis

Confirm installation with `dnf list installed cockpit` and required components.

Quick Triage

Enable and start `cockpit.socket` using `systemctl enable –now cockpit.socket`.

Step-by-Step Diagnosis

Inspect `journalctl -u cockpit -b` and socket logs for TLS or auth failures.

Solution – Primary Fix

Correct certificates if needed and allow cockpit in `firewalld` with permanent rule reload.

Solution – Alternative Approaches

Check active zone includes `cockpit` service and proper interface assignment.

Verification & Acceptance Criteria

Review AVC events only when custom hardening changed cockpit defaults.

Rollback Plan

Reboot and ensure cockpit socket auto-starts and remains reachable.

Prevention & Hardening

Monitor cockpit certificate expiry and periodic firewall audits.

Related Errors & Cross-Refs

Disable cockpit exposure temporarily while restoring previous trusted certificate chain.

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

Use RHEL cockpit documentation and `man cockpit-ws` for diagnostics.