How to fix 503 service unavailable error?

 

503 errors are usually caused by a conflict (a plugin, theme, or script that conflicts with another plugin/script), excessive resource usage, or CDN issues. The error message is vague; often, these errors are not related to the web server.

 

Applies To:
This guide applies to Web Hosting, Semi Dedicated Hosting, Reseller Hosting, and managed servers.

 

Error Message


The exact error might be different on your website:

"503
Service Unavailable
The server is temporarily busy, try again later!"

Or,

"503
The server is too busy to handle your request.
Please wait a few minutes and try again."

 

Step 1: Check CDN


If you are getting a 503 error and using Cloudflare, Quic.cloud, or any other CDN, refer to the following guide:

Fix 503 errors when using Cloudflare

 

Step 2: Check Conflict with LiteSpeed Cache


When a plugin includes features that overlap with LiteSpeed Cache, this can cause a conflict and trigger a 503 error. Please refer to the following guide to check and fix a conflict:

How to check plugin conflict with LiteSpeed Cache?

 

Step 3: Check Resource Usage


If you are getting a 503 error, check the resource usage for CPU, Physical Memory, I/O Usage, IOPS, Entry Processes, and Number of Processes:

  1. Log in to cPanel.

  2. Your average usage is listed under the "Statistics" section on the right sidebar in cPanel.

  3. If any of the above items are above 90%, you might be hitting resource limits, which in turn triggers the error.

  4. You can also view past resource usage:

    How to view resource usage?

In many cases, resource usage can be reduced by optimizing the website, plugins, and themes.

If your resource usage is high, try to reduce the resource consumption.

If your resource usage remains high after applying the suggestions in the guide above, contact us for a closer look.

If resource usage is not high, proceed to the next step.

 

Step 4: Run a PHP Info Page


  1. Go to cPanel > File Manager.

  2. Navigate to the public_html directory.

    public_html is the root directory of your primary domain.
    The root directory is different for other domains and subdomains. You can view the root directories in cPanel > Domains.

  3. Click "+ File" from the top menu and enter phpinfo.php in "New File Name".

  4. Select the phpinfo.php file and click "Edit" from the top menu.

  5. Type in the following lines in the file:

    <?php
    echo phpinfo();
    ?>

  6. Click "Save Changes".

  7. Visit https://yourdomain.com/phpinfo.php to view the page.

    Replace yourdomain.com with your actual domain.

  8. This is a very basic PHP page that should not throw any 503 error.

    If you do not get any error, there is no issue running PHP on your account.

    If you get any error, contact us.

If you do not get any error, proceed to the next step.

 

Step 5: Inspect Error Log


A misconfigured, malformed, or incompatible plugin, theme, or script can cause the error. View the PHP errors to find out what is causing them and disable or update the offending plugin/theme/script:

How to view PHP errors?

If that does not solve the error, contact the devs of the offending plugin, theme, or PHP script for support.

 

  • 257 Users Found This Useful
Was this answer helpful?

Related Articles

How to fix errors after migrating WordPress?

  Migrations from cPanel-based servers are usually seamless. But sometimes a few issues might...

Fix there has been a critical error on this website error in WordPress

  The error "There has been a critical error on this website." often occurs when the PHP mail()...

Fix WordPress redirect error - ERR_TOO_MANY_REDIRECTS

A redirect loop or too many redirects error can occur if multiple redirects from different...

How to fix 403 forbidden error in WordPress?

In this article, we will show you how to easily fix the 403 forbidden error in WordPress. What...

How to deactivate plugins when not able to access WordPress admin?

Often during troubleshooting, you may need to deactivate all plugins and activate them one by...