RHEL 9 Cockpit web console inaccessible on port 9090

📖 ~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 cannot be reached remotely even though package installation is complete.

Environment & Reproduction

Browser timeout on port 9090 or TLS warning with no server response.

Root Cause Analysis

cockpit.socket inactive, firewall block, certificate issue, or wrong interface binding.

Quick Triage

Run systemctl status cockpit.socket and ss -tlnp to confirm listener state.

Step-by-Step Diagnosis

Activate cockpit.socket and confirm it listens on expected addresses.

Solution – Primary Fix

Use firewall-cmd –add-service=cockpit with permanent policy and reload.

Solution – Alternative Approaches

Verify cert paths and labels if custom certificates are deployed.

Verification & Acceptance Criteria

Confirm routing and upstream ACLs allow access from management networks.

Rollback Plan

Review journalctl -u cockpit and related units for startup or TLS errors.

Prevention & Hardening

Restrict cockpit to trusted source ranges instead of exposing globally.

Related Errors & Cross-Refs

Automate cockpit deployment with tested firewall and cert settings.

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

Open cockpit from approved admin host and verify successful login.