🟡 Medium   ⏱ 5–30 min  Last verified: 19 May 2026
Affected versions: RHEL 10.0 RHEL 10.1

📖 ~1 min read

Table of contents
  1. Problem Summary
  2. Symptoms
  3. Diagnostics
  4. Root Cause
  5. Primary Fix
  6. Verification
  7. Prevention
  8. Rollback
  9. Automation
  10. Command Reference
  11. Escalation
  12. Related Notes

Problem Summary

Opened ports work temporarily but close after system reboot.

Symptoms

firewall-cmd –list-ports differs between runtime and permanent configs.

Diagnostics

Run firewall-cmd –runtime-to-permanent check and inspect active zone.

Root Cause

Rules were added without –permanent or placed in wrong zone.

Primary Fix

Re-add ports with –permanent 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.

Illustrative mockup for rhel-10 — rhel10-b02-p29-1
Illustrative mockup — Progressive Robot — Illustrative mockup — Progressive Robot

Verification

After reboot, confirm firewall-cmd –list-all still shows expected rules.

Illustrative mockup for rhel-10 — rhel10-b02-p29-2
Illustrative mockup — Progressive Robot — Illustrative mockup — Progressive Robot

Prevention

Standardize zone assignment and persistent rule automation.

Rollback

Remove accidental rules using firewall-cmd –permanent –remove-port.

Automation

Manage rules via firewall system role or Ansible modules.

Command Reference

firewall-cmd –add-service=http –permanent; firewall-cmd –reload

Escalation

Provide zone XML from /etc/firewalld and service exposure requirements.

NetworkManager connection zone bindings can override expectations.

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.

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.