Website shows 503 Service Unavailable (or 502, 504)
On this page
A 503 error means the web server received the request but the program that builds the page (PHP, or your Node.js, Python or Ruby application) could not answer. Unlike a 500 error, the code often never started, so there may be nothing in your error log.
Symptoms
- The page shows 503 Service Unavailable or 503 — Service unavailable ("The website is busy or being updated. Please try again in a moment.").
- Sometimes 502 — Bad gateway or 504 — Gateway timeout instead.
- It happens at busy times, or on every page of one website, or only on the path of an application.
Causes
Most likely first:
- The account reached its memory or process limit. A process was stopped, or no new PHP process could start.
- A Node.js, Python or Ruby application is stopped or crashed (for the website or path it serves).
- The website is very busy or a page is very slow, so requests wait until they time out.
- The web server was applying a change — for a few seconds after you added a domain or changed a setting.
- The whole server is short of memory or a service is down (only your host can see and fix this).
Fix
1. Account limits reached
- Open Resource Usage (section Advanced).
- Look at Server resources. Limits reached lists the days on which your sites hit a limit, for example "3× memory", "2× processes" or "slowed 12 min".
What the limits do:
- Memory: over the limit, the biggest process of your account is stopped. The visitor whose request it was gets an error.
- Processes: PHP, cron jobs, SSH sessions and applications share one number of processes. When it is full, new PHP processes cannot start.
To fix it, find what uses the resources: a cron job that runs too often or never ends, a plugin that loops, a bot hammering a search page (see Visitors, section Advanced). Turn on the Page cache for WordPress sites (WordPress page). If your sites reach the limits every day, ask your host for a bigger plan. See also slow website and CPU limit.
2. An application is stopped
- Open Node.js / Python / Ruby (section Files).
- Find the application for that website and path.
- Click Logs to see why it stopped, fix the cause, then click Start (or Restart).
Your application must listen on the port given in $PORT, address 127.0.0.1. If it listens on another port or address, the web server cannot reach it and visitors get an error.
3. Very busy or very slow pages
One account can run a limited number of PHP requests at the same time. When every one of them is waiting for a slow page (a long report, an external API that does not answer), the next visitors wait too. Open Errors (section Advanced) and look for Maximum execution time lines; see Maximum execution time exceeded.
4. A change was being applied
After you add a domain, change the PHP version or install a certificate, the web server restarts gracefully. Wait a minute and reload the page.
5. Server problem
Open Site Check (section Advanced), choose the website and click Check. If Answer on this server also shows 503 while your Resource Usage shows no limits reached, contact your host through Support.
Administrators: check Service Manager and Server Status (section Server). The watchdog restarts a service that stops or hangs and lists what it did. The web server's own error log of each website is in /usr/local/lsws/logs/domains/<domain>.error.log.
Still not working?
If your host has turned on the AI assistant, run Site Check and click Ask the AI assistant what is wrong, or Fix with the assistant. Otherwise send the Site Check result to your host through Support.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- Website slow: CPU, memory or process limit reached
Your website is slow or stalls at busy times. See whether the account reaches its CPU, memory or process limits in Resource Usage and make it lighter.
- Website shows 500 Internal Server Error (HTTP 500)
Find why your website answers "500 Internal Server Error" or a blank page, read the PHP error behind it in the control panel and fix the usual causes.
- Website not working after changing nameservers (DNS)
You changed nameservers or DNS records and the site still shows the old server or nothing. Check where the domain points, how long DNS takes and what to fix.