π ~1 min read
Table of contents
Symptom & Impact
Browser cannot connect to https://host:9090 for Cockpit.
Environment & Reproduction
Check systemctl status cockpit.socket and ss -tulpn | grep 9090.
Root Cause Analysis
Verify local access first, then external client connectivity.
Quick Triage
Socket unit inactive, firewalld rule missing, or cert issue during TLS handshake.
Step-by-Step Diagnosis
Enable and start cockpit.socket, then verify listener state.

Solution – Primary Fix
Add cockpit service in firewalld and reload rules.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
systemctl is-enabled cockpit.socket should be enabled and active.
Verification & Acceptance Criteria
Confirm zone matches interface and remote path allows 9090/tcp.
Rollback Plan
Default policy supports cockpit; inspect AVCs only if custom hardening applied.
Prevention & Hardening
Use journalctl -u cockpit.socket and cockpit-ws logs for handshake errors.
Related Errors & Cross-Refs
Include cockpit health checks in server acceptance tests.
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
Disable temporary exposure if security review has not approved access.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today β we respond within one business day.