Jan 17, 2022
Nabilla R. & Freddy M.
How to Fix 503 Service Unavailable Error: 7 Steps That Work
Every time visitors access a website, the web browser sends a request to the web server. Sometimes, instead of complying with the request, the server sends a blank page with an HTTP status code. This indicates an error.
Don’t worry, however – most sites experience errors at least once in their lifetime. The 503 service unavailable error is one of the most frequently encountered problems. Web servers return the HTTP 503 error whenever they are unable to process a request.
Like any server issues, the 503 service unavailable error can negatively impact a site when left unsolved. Thus, this guide will dive into the possible causes of this error and how to fix it effectively.
First, let’s start with what exactly the 503 service unavailable error is.
|Error code||503 service unavailable error|
|Error type||Server-side error|
|Error variations||503 Service Unavailable|
Error 503 Service Unavailable
503 Service Temporarily Unavailable
HTTP Error 503
HTTPS Error 503
HTTP Server Error 503
HTTP Error 503. The service is unavailable.
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
|Error causes||Resource usage exhaustion|
Server communication problems
Sudden traffic spikes
Distributed Denial of Service (DDoS) attack
Incorrect DNS configuration
Plugin or theme incompatibility
What Is 503 Service Unavailable Error and What Causes It?
Web browsers and web servers interact using the HTTP (Hypertext Transfer Protocol) status codes.
Whenever you access a website, your browser sends requests to the web server hosting the content. The web server then fetches the requested resources along with an HTTP response status code.
Here are the five server response codes:
- 1xx – informational
- 2xx – success
- 3xx – redirection
- 4xx – client-side error
- 5xx – server-side error
Usually, the servers only send back the requested website and browsers don’t display HTTP status codes, indicating that the connection is successful. However, whenever an error occurs, the servers will forward an error message along with the error code.
The 503 service unavailable error is one among these error codes. It’s common and happens on the server side, showing that the server temporarily cannot handle the request.
Below are the most common ways the HTTP error 503 messages can appear in:
- 503 Service Unavailable
- Error 503 Service Unavailable
- 503 Service Temporarily Unavailable
- HTTP Error 503
- HTTPS Error 503
- HTTP Server Error 503
- HTTP Error 503. The service is unavailable.
- The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Unlike other server-side errors, the HTTP error 503 service unavailable means that your web server operates properly but can’t be reached at the moment. Typically, it’s caused by a high number of requests sent to the server, which exhausts available resources.
In most cases, the 503 service unavailable error will disappear as soon as the traffic goes down. Hence, allowing visitors to view your content after a little while. However, when the error persists for an extended period, it might be an indication of a more serious problem within your server.
Therefore, the next section will show you the seven effective ways to find the root cause and resolve the 503 service unavailable error.
7 Steps to Find Root Cause and Resolve the 503 Error:
From checking your resource usage to viewing server logs, we will walk you through seven ways to diagnose and fix the HTTP 503 errors.
1. Check Resource Usage
The resources that a server uses are RAM, CPU, I/O, entry processes, and website inodes. Checking these metrics can help you confirm whether the issue is related to limited resources. For example, you can monitor incoming traffic and detect whenever an unusual traffic surge occurs.
Hostinger’s hPanel has excellent functionality to monitor resource usage. Users can access the dashboard and navigate to Order -> Order Usage.
From there, you will find various metrics related to your website’s resource usage, including:
- CPU – the amount of CPU power consumed by your site.
- Memory limit – total memory used by your website to process requests.
- Processes – the number of processes running on your hosting account.
- Throughput (I/O) – the speed of data transfers between the hard disk and RAM.
- Total requests – the amount of HTTP and HTTPS requests of all hosting accounts.
- Bandwidth – data transferred within a specific period of time.
These metrics can help you solve the 503 service unavailable error. For example, look at the following metric:
In the graph above, the red line represents your current plan’s limit, and the blue one shows the amount of memory used by your website. When your website exceeds the memory limit, it will slow down your overall performance, triggering the HTTP error 503.
A good rule of thumb is to upgrade your web hosting plan to increase these three server components:
- CPU. Although the CPU can process numerous requests simultaneously, a constant strain can exhaust the CPU and slow down your site’s performance. Therefore, if you have a large volume of requests, it’s best to upgrade your CPU capacity.
- RAM. A website with large traffic needs to have more RAM to keep it up and running. The more memory your website has, the less strain it will have on your CPU, allowing the server to run faster and process more requests.
- Bandwidth. The more bandwidth you have, the faster data travels between your site, users, and the internet. If your site has a lot of dynamic content, such as images and videos, you will need a higher bandwidth allowance for optimized loading time.
2. Check for Ongoing Maintenance
Regular server maintenance is vital to optimize site performance and minimize security risks.
Use tools like GTMetrix to get insights on optimizing your site performance.
Generally, a web server or application is set to shut down whenever it’s going through maintenance.
With that in mind, the HTTP error 503 service unavailable might occur during this unexpected maintenance. For instance, some web hosts usually provide their users with automatic updates whenever a new WordPress version is released. The system automatically issues the 503 service unavailable error during the process.
Contact your hosting provider to check if the 503 error is caused by scheduled maintenance. Hostinger users can simply go to our status page and see real-time updates of the system.
Alternatively, you can choose to modify your server configuration options and disable automatic updates. That way, you will have complete control over your server maintenance.
Below are the steps to disable automatic updates via Hostinger’s hPanel:
- Access your hPanel dashboard and go to Website -> Auto Installer. Then, select WordPress.
- Next, fill in all necessary information, from your domain name to administrator login credentials.
- At the bottom of the page, you will see three automatic update options. Continue by selecting Turn off automatic application updates.
- Click Install and wait for the process to complete.
3. Stop Running Processes
Another common problem causing the 503 service unavailable error is exceeding the maximum process limit. When your web server processes too many processes simultaneously, it can overload and stop working.
To get your site back online, you will need to stop running processes. For VPS hosting users, you can kill a process using the kill command line.
Meanwhile, shared hosting users can navigate to the hosting control panel and go to the Order Usage page. From there, scroll down to the bottom of the page until you find the Stop running processes option.
Clicking on the Stop button will kill all ongoing processes on your website. Keep in mind that this solution is just a temporary fix – you still have to do further investigation to identify what is causing many processes to run simultaneously.
Start by examining your WordPress themes and plugins as they can use up resources and conflict with each other.
If you encounter the HTTP 503 error after installing a specific plugin, it means you have found the culprit. However, if you can’t identify which plugin is causing the problem, you might need to disable all plugins and enable them one by one.
Aside from plugins, poorly-coded WordPress themes can also trigger the 503 errors. To fix this, try to change your WordPress theme to a default one, such as Twenty Nineteen or Twenty Twenty.
If you keep exceeding the maximum process limit, some scripts or applications might be using more resources than your current plan provides. In this case, you will need to either optimize your website or upgrade your hosting plan altogether.
4. Reset Firewall
A web application firewall (WAF) blocks any suspicious traffic from coming into your site. In other words, the firewall protects your website against malicious activities, from brute force and DDoS attacks to cross-site scripting and SQL injections.
That being said, improper firewall configuration can detect false positives and block connections from a specific client. For example, your firewall might mistake a safe request from a content delivery network (CDN) as malicious, blocking critical traffic and triggering the 503 errors.
Resolve this problem by resetting your firewall configuration. Hostinger VPS users can go to the admin panel, navigate to the VPS Management section, and click Reset Firewall.
However, the steps will vary depending on your hosting provider. It’s best to contact the support team and ask for assistance.
5. Check Server Logs and Fix the Code
If the 503 error still persists, try checking your error log.
Server-side logs record information about your website’s activities, from web pages requested by visitors to errors happening in the system. Using information from the logs, you can identify and fix errors more efficiently.
Usually, your hosting provider features the website error log through the admin dashboard. Hostinger users should access hPanel and go to Advanced -> PHP Configuration.
The next step is to switch to the PHP Options tab and check the logErrors option.
Scroll down to save the changes. Go to the public_html directory, open the wp_content folder, and view the error log file whenever an error occurs.
Additionally, you can also enable error logging by adding the
WP_DEBUG PHP constant in the wp-config.php file.
To get started, open your website root directory and locate the wp-config.php file. Hostinger users can access hPanel and go to Files -> File Manager.
- Click on the public_html folder and choose wp-config.php.
- Add the following code inside the file:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
- Once you’re done, click the Save and close button.
Moreover, you can check the server error log on your web server software by accessing the following file accordingly:
- Nginx server:
- Apache server:
6. Restart Your Server and Networking Equipment
The 503 service unavailable error can happen due to connectivity issues between the server chain hosting your application.
Thus, if you have root access to your website, one of the easiest ways to fix the 503 service temporarily unavailable error is to reboot your server. If your site is hosted on multiple servers, make sure to refresh each server to return it to normal.
To do so, Hostinger users can access the Server Management page and click on the Reboot button.
If the 503 service unavailable error persists, the problem might come from temporary issues within your computer devices and home connection. This can happen due to network misconfiguration that prevents your devices from processing requests.
In this case, a simple restart can get the job done – switch off all networking equipment, wait for a second, and turn it back on again. Once done, reconnect your computer to the network and reload your website.
7. Check Your DNS
Another possible factor causing the 503 error is a DNS-related issue, such as unresolved IP addresses, unresponsive DNS servers, or a corrupted DNS cache.
One effective way to fix this issue is to flush your DNS. The way to flush DNS cache depends on your operating system. Below, we will show you how to perform this task on Windows, macOS, and Google Chrome.
On Windows, open the command prompt and input the following directive:
The command will clear out the DNS files and restart the DNS resolver cache. A confirmation message will appear once the DNS is successfully flushed.
Mac users can press F4 to access Terminal and run the following command:
sudo killall -HUP mDNSResponder
Note that different macOS versions will require different commands.
Google Chrome users can flush their DNS cache on their web browser.
Open the program and enter the following URL into the address bar:
It will take you to the internal settings page. From there, select the Clear host cache option.
Temporarily switching your DNS servers is another method to try. Your DNS servers are assigned by your ISP by default, but you can always change them to third-party servers, such as Google Public DNS.
Troubleshooting Other 5xx Errors
The 503 error is an HTTP status code that appears whenever the server is unable to handle a request. Usually, this error occurs during server maintenance. However, the 503 errors can also be a result of resource outages.
Although the error usually goes away on its own, it can negatively impact your site performance and user experience if left unattended. With this in mind, we have looked at seven effective ways to solve this problem and return your site to normal.
Let’s do a quick recap:
- Check resource usage – monitor your resource metrics to confirm if the issue is related to excessive use. If necessary, upgrade your hosting plan.
- Check for ongoing maintenance – contact your hosting service provider to see if scheduled maintenance is in progress.
- Stop running processes – kill ongoing processes that are overwhelming your server’s capacity.
- Reset firewall – revert an improperly configured firewall by resetting it through your hosting admin panel.
- Check server logs and fix the code – comb through your website error logs and resolve any unusual codes.
- Restart your server and networking equipment – reboot your server and networking equipment to resolve any possible misconfiguration.
- Check your DNS – flush your DNS cache and temporarily switch your server to public DNS.
All in all, we hope these troubleshooting steps help you remove the HTTP error 503 and get your website back up. Should you have any further questions, don’t hesitate to leave them in the comment section below.