View Plans
Help

How to fix the 503 Service Unavailable error

“503 Service Unavailable” means the server is up but cannot handle the request right now. It is usually temporary: too much traffic, all PHP processes busy, a stuck plugin or script, or maintenance. Visitors can wait and reload. Site owners should check the error log and turn off whatever changed last.

Updated · HostUpIndia team

What causes a 503 Service Unavailable error

A 503 is a temporary status. The server is running, but it is too busy or offline for maintenance, so it turns the request away. Some servers add a Retry-After header that says when to try again.

A 500 error is different: the server tried to run the page and failed. See how to fix the WordPress 500 error. A 502 or 504 comes from a proxy in front of the server: see 502 Bad Gateway and 504 Gateway Timeout. A page that says “508 Resource Limit Is Reached” means the account hit its hosting limits: see how to fix the 508 error.

  • A traffic spike, such as a sale, a widely shared post or a newsletter going out.
  • All PHP processes busy. A hosting account can run only so many at once, and slow requests hold on to them.
  • A plugin, theme or script stuck on a slow database query or an outside service.
  • Maintenance by your host, or a WordPress update that did not finish.
  • A CDN or proxy in front of the site that cannot get an answer from your server.
  • A DDoS attack or a flood of bots and crawlers.

Seeing a 503 error on a site you visit

The problem is on the website’s server, not your device or connection.

  • Wait a minute or two, then reload the page once.
  • Don’t refresh again and again. Each reload adds to the load on a busy server.
  • If it still shows, try again later. Most 503 errors are short-lived.
  • If it is your own site, follow the steps below.

Find the cause of the 503 error

Narrow it down before you change anything. Note the time the error appeared, since the logs are listed by time.

  • Load the home page, a simple page and the page that failed. If only one page fails, the plugin or script behind it is the likely cause.
  • If every page fails, look at traffic, process limits, maintenance and the CDN.
  • Check your email and client area for a maintenance notice from your host.
  • In cPanel, open Metrics › Errors and read the entries from the time of the 503. Note any script, timeout or memory message.
  • In File Manager, open the error_log file in your site’s folder, usually public_html, if there is one. It lists PHP errors with the file at fault.
  • If your cPanel shows Resource Usage under Metrics, open it and check whether the account reached its CPU, memory or process limit at that time.
  • If the site uses a CDN such as Cloudflare, pause it for the site and reload after a few minutes.
  • If the 503 stops, check the CDN’s settings and status page. If it stays, the cause is on your server.
  • Turn the CDN back on when you are done.

Fix a 503 caused by a plugin or script

A 503 that began after an update or a new plugin usually comes from that change. Turn it off by renaming its folder, in cPanel File Manager or over FTP.

  • Before you change files, open cPanel › Backup and download a home directory backup and a database backup.
  • In File Manager, open Settings and turn on Show Hidden Files.
  • If WordPress says “Briefly unavailable for scheduled maintenance”, an update did not finish. Delete the .maintenance file in your WordPress folder, then run the update again.
  • In wp-content/plugins, rename the folder of the plugin you added or updated last, for example plugin-name to plugin-name-off.
  • Load the site. If it works, update or replace that plugin before you turn it on again.
  • Still a 503? In wp-content, rename plugins to plugins-off and load the site.
  • If it works, log in and open Plugins so WordPress deactivates them, then rename the folder back to plugins.
  • Activate plugins one at a time, loading the site after each. The one that brings the 503 back is the cause.
  • Not WordPress? Undo the last change to your code, or restore those files from a backup made before the 503 began.

Fix a 503 caused by traffic, bots or cron jobs

If the 503 comes and goes with busy times, the account is running out of capacity. Cut the load first, then decide whether you need more.

  • In cPanel, open Cron Jobs and look for tasks that run every minute or overlap.
  • Set those tasks to run less often, such as every 15 minutes, if the task allows.
  • On WordPress, download a copy of wp-config.php from File Manager before you edit it.
  • Add define( 'DISABLE_WP_CRON', true ); to wp-config.php, above the line that says “stop editing”.
  • Add a cron job in cPanel that runs every 15 minutes, with your own domain in place of example.com: wget -q -O - https://example.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1
  • Open Metrics › Visitors and look for one IP address or bot making many requests.
  • Block an abusive IP address in cPanel’s IP Blocker. If the site is behind a CDN, block it in the CDN instead.
  • Turn on page caching so most visits are served without running PHP. On LiteSpeed, use the LiteSpeed Cache plugin for WordPress.
  • For a large attack, put the site behind a CDN with DDoS protection and tell your host.
  • If the 503 continues with normal traffic and clean logs, open a support ticket with the time, the page and what you have tried.
  • If the account reaches its limits on normal days, move to a plan with more CPU and RAM.

HostUpIndia Web & cPanel Hosting

HostUpIndia Web & cPanel Hosting runs on LiteSpeed with NVMe storage, and each plan card lists its CPU and RAM, so you know what your site gets. Every plan includes cPanel for the steps above, terminal (SSH) access, free SSL and daily backups kept 30 days.

Plans start at ₹49 a month on 3-year billing. Prices exclude 18% GST. See Web & cPanel plans.

  • Moving from another host? The in-house team moves your site for you: free website migration.
  • Support tickets and email are received 24 hours a day, 7 days a week; WhatsApp is open for questions from 10 am to 7 pm IST, Monday to Saturday.
  • More help guides.