📖 ~1 min read
Table of contents
Symptom & Impact
Browser cannot load Cockpit, reducing operations visibility and slowing routine admin tasks.
Environment & Reproduction
After hardening changes, package removal, firewall resets, or TLS policy changes.
Root Cause Analysis
`cockpit.socket` inactive, firewalld not allowing service, or reverse proxy/TLS mismatch.
Quick Triage
Run `systemctl status cockpit.socket`, `ss -tulpen | grep 9090`, and `firewall-cmd –list-services`.
Step-by-Step Diagnosis
Use `journalctl -u cockpit –since -1h`, `journalctl -u cockpit.socket –since -1h`, and `curl -k https://localhost:9090`.
Solution – Primary Fix
Port 9090 is listening, cockpit responds locally, and remote access succeeds from allowed networks.
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
Install or reinstall cockpit via `dnf`, enable socket, and permit `cockpit` service in firewalld.
Verification & Acceptance Criteria
Log in through browser and confirm system metrics, services, and terminal module render correctly.
Rollback Plan
Remove temporary broad firewall access and revert to prior secure exposure model if needed.
Prevention & Hardening
Restrict source ranges, keep cockpit updated, and monitor failed authentication attempts.
Related Errors & Cross-Refs
`dnf -y install cockpit && systemctl enable –now cockpit.socket && firewall-cmd –add-service=cockpit –permanent && firewall-cmd –reload`
Related tutorial: View the step-by-step tutorial for rhel-8.
View all rhel-8 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
RHEL 8 web console documentation and Red Hat hardening guidance for Cockpit exposure.
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.
