Cockpit Web Console Unreachable 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

Browser cannot connect to https://host:9090 though SSH to host works.

Environment & Reproduction

cockpit.socket inactive, package missing, or firewalld blocks port/service.

Root Cause Analysis

Check rpm -q cockpit and install with dnf install cockpit if absent.

Quick Triage

Run systemctl enable –now cockpit.socket and verify listening with ss -tulpen.

Step-by-Step Diagnosis

Run firewall-cmd –add-service=cockpit –permanent and reload rules.

Solution – Primary Fix

Retry browser and inspect journalctl -u cockpit for TLS or auth messages.

Solution – Alternative Approaches

Use ausearch -m AVC if cockpit access appears blocked by policy decisions.

Verification & Acceptance Criteria

Confirm client trusts cert presented by cockpit-ws on managed hosts.

Rollback Plan

Ensure intermediate security groups or ACLs permit TCP/9090.

Prevention & Hardening

Admins lose convenient web management and must rely solely on CLI.

Related Errors & Cross-Refs

Restrict cockpit exposure to admin networks and enforce MFA where possible.

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

Include cockpit socket and firewall checks in server readiness tests.