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 access https://host:9090 and connection is refused or times out.

Environment & Reproduction

cockpit package is missing, cockpit.socket is inactive, or firewalld blocks port 9090.

Root Cause Analysis

Run rpm -q cockpit, sudo systemctl status cockpit.socket, and ss -tulpen | grep 9090.

Quick Triage

Install cockpit via sudo dnf install -y cockpit and enable socket activation.

Step-by-Step Diagnosis

Allow service with sudo firewall-cmd –add-service=cockpit –permanent and reload firewalld.

Solution – Primary Fix

Re-test browser access and review sudo journalctl -u cockpit -u cockpit.socket for errors.

Solution – Alternative Approaches

Confirm login page loads and authenticated sessions can view system metrics.

Verification & Acceptance Criteria

Disable cockpit.socket if exposure is not desired and remove firewall service entry.

Rollback Plan

Include cockpit baseline and access policy in standard RHEL 9 server profile.

Prevention & Hardening

Track cockpit socket failures and repeated login anomalies in journald.

Related Errors & Cross-Refs

Manage cockpit install and firewall configuration through repeatable provisioning playbooks.

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 cockpit project docs and RHEL 9 web console administration references.