Need Assistance?

In only two hours, with an average response time of 15 minutes, our expert will have your problem sorted out.

Server Trouble?

For a single, all-inclusive fee, we guarantee the continuous reliability, safety, and blazing speed of your servers.

How to Fix the Plesk Error “Not Starting NGINX as it is Disabled in Config”

Introduction

When managing a Plesk-powered server, you might encounter the error — this guide focuses on Fixing the Plesk Error “Not Starting NGINX as it is Disabled in Config” to help you resolve it efficiently.

Not starting nginx as it is disabled in config

-This happens when Nginx, set up as a reverse proxy in Plesk, is disabled in its own config—even though Plesk might show it as “enabled.” The result? Nginx refuses to start, websites break, and you’re left troubleshooting. Luckily, resolving this is straightforward with a few SSH commands. Let’s walk through it.

Step‑by‑Step Fix

Step1: Connect via SSH

Log into your server using SSH (e.g., ssh root@your-server-ip).
Step2: Check Nginx status in Plesk

#plesk sbin nginxmng -s

This reports if Plesk believes Nginx is “Enabled” or “Disabled.”


Step3: Reset Nginx configuration via Plesk by running:

#plesk sbin nginxmng --disable
#plesk sbin nginxmng --enable

These commands disable and re-enable Nginx support in Plesk, resetting the integration and config

Step4: Check Nginx syntax:

#nginx -t

Ensures there are no syntax errors in Nginx configurations.

Start the service

#systemctl start nginx

Step5: Verify it’s running

#systemctl status nginx

Look for an active (“running”) status.

Why This Works

  • Plesk uses its nginxmng utility to manage the NGINX_ENABLED flag in Nginx’s config files, such as /etc/default/nginx or /etc/sysconfig/nginx.
  • Disabling and re-enabling Nginx forces Plesk to reset these settings and reconfigure Apache–Nginx port listening
  • After resetting, standard systemctl commands will successfully start the service.

Conclusion

The Plesk error “Not starting nginx as it is disabled in config” simply means that Nginx has been flagged off at the system level. To fix it:

  1. SSH into your server.
  2. Run nginxmng –disable then –enable.
  3. Test config, start the service, and confirm it’s running.

Following these steps resets the configuration and gets your Nginx reverse proxy back online quickly. If hiccups persist, double-check logs and configs—but this method solves the vast majority of cases.

If you’re still facing issues after troubleshooting the error, our expert team is ready to assist you. We offer comprehensive Plesk Server Management Services, along with Web Server Hardening Services and Web Server Optimization Services, to ensure your server runs smoothly and securely. contact us today for fast and reliable support.

Liked!! Share the post.

Get Support right now!

Start server management with our 24x7 monitoring and active support team

Let us know your requirement.

Can't get what you are looking for?

Get Support Right Away!

Thank You

We have received your query and will get back to you soon.