CentOS Stream 9 – Common Problem 115 – Diagnosis and Fix

📖 ~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 web UI is unreachable on https://host:9090.

Environment & Reproduction

cockpit.socket masked or firewalld blocking the cockpit service.

Root Cause Analysis

Default install enables the unit but a hardening profile may disable it.

Quick Triage

systemctl status cockpit.socket and firewall-cmd –list-services.

Step-by-Step Diagnosis

ss -ltnp | grep 9090 to confirm listener.

Solution – Primary Fix

systemctl enable –now cockpit.socket; firewall-cmd –add-service=cockpit –permanent; –reload.

Solution – Alternative Approaches

Bind cockpit to an alternate port via systemd drop-in and adjust the firewall.

Verification & Acceptance Criteria

curl -k https://localhost:9090 returns the login HTML.

Rollback Plan

Disable cockpit again with systemctl disable –now cockpit.socket.

Prevention & Hardening

Restrict Cockpit access via firewalld zones or IP allowlists.

Related Errors & Cross-Refs

Related: SELinux booleans and PAM session limits.

Related tutorial: View the step-by-step tutorial for centos-stream-9.

View all centos-stream-9 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Cockpit documentation and Red Hat web console chapter.