{"id":56796,"date":"2025-12-06T17:55:08","date_gmt":"2025-12-06T22:55:08","guid":{"rendered":"https:\/\/www.inmotionhosting.com\/support\/?p=56796"},"modified":"2025-12-09T12:14:25","modified_gmt":"2025-12-09T17:14:25","slug":"how-to-stop-and-disable-firewalld","status":"publish","type":"post","link":"https:\/\/www.inmotionhosting.com\/support\/security\/how-to-stop-and-disable-firewalld\/","title":{"rendered":"How to Stop and Disable Firewalld"},"content":{"rendered":"
\"How<\/figure>\n\n\n

Firewalld is a lightweight Linux firewall, but sometimes you may need to stop or disable it. This guide explains when it\u2019s safe to turn it off, how to stop or disable it with Systemd, and what to do on UFW-based systems. Since disabling a firewall leaves your server exposed, safer alternatives include adjusting rules, opening only needed ports, or using zones. Always re-enable protection or ensure another firewall layer is in place. <\/p><\/div>\n\n\n

Firewalld<\/a> is a popular, lightweight command-line firewall for Linux server and desktop systems. We\u2019ve covered how to open necessary ports and services in Firewalld<\/a>. We\u2019ve also covered how to manage zones and more advanced Firewalld configurations<\/a>.<\/p>\n\n\n\n

While you can stop or disable Firewalld, it\u2019s important to remember that this removes a key security layer<\/strong>. Disabling the firewall should only be temporary, and only when you have another layer of protection in place (such as a cloud firewall, hardware firewall, or security rules inside your application).
<\/p>\n\n\n\n

Below, we cover how to temporarily stop Firewalld<\/a> and disable Firewalld<\/a> from starting upon system reboot<\/a>.<\/p>\n\n\n\n

firewalld.service<\/code> and firewalld<\/code> can be used interchangeably with the Systemd commands below.<\/p>\n\n\n\n

When to Disable Firewalld<\/strong><\/h2>\n\n\n\n

Before making changes, it helps to understand why someone might disable the firewall in the first place. In most cases, Firewalld should remain active to protect your server from unauthorized access. However, there are a few specific scenarios where stopping or disabling it can make troubleshooting and configuration easier.<\/p>\n\n\n\n

There are a few common situations where you may need to turn off Firewalld:<\/p>\n\n\n\n

    \n
  • Troubleshooting connection issues<\/strong>: If a service (like SSH, HTTP, or MySQL) is not responding, disabling Firewalld can confirm whether the firewall is blocking the traffic.
    <\/li>\n\n\n\n
  • Testing another firewall application<\/strong>: If you plan to use a different firewall such as ConfigServer Security & Firewall (CSF), you may need to disable Firewalld first.
    <\/li>\n\n\n\n
  • Temporary configuration changes<\/strong>: During migrations or setup, you may need to work without Firewalld until custom rules are added.
    <\/li>\n<\/ul>\n\n\n\n

    Warning:<\/strong> Leaving your server without a firewall exposes all open ports to the internet. Always re-enable Firewalld or use another firewall solution after troubleshooting.<\/p>\n\n\n\n

    Safer Alternatives to Disabling Firewalld<\/strong><\/h2>\n\n\n\n

    Even if disabling seems like the simplest fix, it\u2019s not always the best choice for long-term security. In many cases, you can achieve the same goal by adjusting rules instead of turning the firewall off completely. These approaches allow you to continue troubleshooting without leaving your system fully exposed.<\/p>\n\n\n\n

    Instead of shutting the firewall down completely, consider these options:<\/p>\n\n\n\n

    Open only the required ports<\/strong> with firewall-cmd or firewall-offline-cmd. For example:<\/p>\n\n\n\n