π ~1 min read
Table of contents
Symptom & Impact
Application is reachable only until reboot because firewall changes were not made permanent.
Environment & Reproduction
Admin opened port using runtime command only.
firewall-cmd --add-port=8443/tcp
reboot
Root Cause Analysis
Runtime and permanent firewalld configurations are separate stores.
Quick Triage
Compare runtime and permanent settings.
firewall-cmd --list-ports
firewall-cmd --permanent --list-ports
Step-by-Step Diagnosis
Confirm active zone and inspect persisted XML rule files.
firewall-cmd --get-active-zones
ls -l /etc/firewalld/zones

Solution – Primary Fix
Add permanent rule and reload firewalld.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.
sudo firewall-cmd --permanent --add-port=8443/tcp
sudo firewall-cmd --reload
sudo systemctl enable --now firewalld

Solution – Alternative Approaches
Use predefined services instead of raw ports for maintainability.
firewall-cmd --permanent --add-service=https
Verification & Acceptance Criteria
Port remains open across reboot and service is reachable.
firewall-cmd --permanent --list-ports
ss -ltnp | grep 8443
Rollback Plan
Remove permanent rule if exposure is no longer required.
sudo firewall-cmd --permanent --remove-port=8443/tcp
sudo firewall-cmd --reload
Prevention & Hardening
Require change reviews for firewall updates and keep least-privilege zones.
Related Errors & Cross-Refs
Related to wrong zone binding and cloud security group mismatches.
Related tutorial: View the step-by-step tutorial for rhel-10.
View all rhel-10 tutorials on the Tutorials Hub β
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
firewalld zone model and persistent rule management docs.
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.