CentOS Stream 10 – Common Problem 106 – 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 returns 401 or refuses connection on port 9090.

Environment & Reproduction

Reported after SELinux upgrades, firewalld changes, or PAM lockouts.

Root Cause Analysis

Cockpit socket disabled, firewall closed, or user lacks wheel rights.

Quick Triage

Check systemctl status cockpit.socket and recent journalctl entries.

Step-by-Step Diagnosis

Test with curl -k https://localhost:9090 against the local socket.

Solution – Primary Fix

Enable cockpit.socket, allow service in firewalld, and verify PAM stack.

Solution – Alternative Approaches

Bind to specific IP with ListenStream override if 9090 collides.

Verification & Acceptance Criteria

Cockpit responds and admin login lands on the dashboard.

Rollback Plan

Disable cockpit.socket and remove firewalld service if rollback required.

Prevention & Hardening

Limit access via firewall sources and Cockpit role mapping.

Related Errors & Cross-Refs

Related to sssd auth and 2FA module failures.

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

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

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Cockpit Project administration documentation.