Cockpit Web Console Unreachable After Hardening

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

Cockpit on port 9090 fails to load even though host is otherwise reachable.

Environment & Reproduction

Run `systemctl status cockpit.socket` and `ss -tulpn | grep 9090` to verify listener state.

Root Cause Analysis

Ensure `cockpit`, `cockpit-system`, and dependencies are installed from supported repos.

Quick Triage

Confirm socket activation and dependent services via `systemctl list-dependencies cockpit.socket`.

Step-by-Step Diagnosis

Inspect `journalctl -u cockpit –since -2h` and socket logs for startup failures.

Solution – Primary Fix

Backup cockpit config overrides and active access controls before editing.

Solution – Alternative Approaches

Allow `cockpit` service in `firewalld` and verify the interface belongs to correct zone.

Verification & Acceptance Criteria

Check for AVC denials involving cockpit processes and restore altered context labels.

Rollback Plan

Enable socket, apply firewall rule, and restart cockpit components as needed.

Prevention & Hardening

Open https://host:9090 and confirm successful authentication and dashboard load.

Related Errors & Cross-Refs

Document hardening baselines to preserve cockpit prerequisites during compliance changes.

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

Provide cockpit journal, firewall export, and SELinux AVC evidence.