Why is my website showing a 503 service unavailable error?
Summary
This guide helps you troubleshoot and resolve: Why is my website showing a 503 service unavailable error?. Follow the steps below to fix the issue.
Common Causes
An HTTP 503 Service Unavailable error means your web server is temporarily unable to handle requests. This is typically a server-side issue rather than a problem with your computer or internet connection. For small businesses, a 503 error can interrupt sales, enquiries, and daily operations, so understanding the cause and knowing when to escalate is important.
Common triggers include planned server maintenance by your hosting provider, unexpected traffic spikes overwhelming server resources, resource exhaustion on shared hosting plans, faulty application scripts or plugin conflicts, database connection failures, DNS misconfigurations, CDN errors, and DDoS attacks or malicious traffic.
Quick Fix Steps
- Refresh your browser page after a few minutes to see if the error clears.
- Check your hosting provider's status page or social media channels for announced maintenance.
- Try accessing your website from a different network or mobile device to rule out local caching issues.
- If you recently installed a plugin, theme, or script, disable it and test again.
- Review your hosting control panel for resource usage alerts or suspension notices.
Detailed Instructions
Checking Hosting Resource Usage
- Log in to your hosting control panel, such as cPanel, Plesk, or your provider's custom dashboard.
- Navigate to the resource usage or statistics section. In cPanel, go to Metrics > Resource Usage.
- Review current CPU, memory, and entry process usage against your plan limits.
- Look for
503entries in the error logs, usually found under Metrics > Errors. - Interpret the metrics by checking if usage consistently hits 80 to 90 percent of your allocated limit. Occasional spikes are normal, but sustained high usage indicates your site has outgrown its current plan.
- If resource limits are consistently reached, consider optimising your website code and database or upgrading to a higher hosting plan.
Troubleshooting WordPress Sites
- Access your website files via FTP or your hosting control panel's file manager.
- Rename the
/wp-content/plugins/folder to/wp-content/plugins_old/to disable all plugins. - Refresh your website. If the 503 error clears, reactivate plugins one at a time via the WordPress admin dashboard under Plugins > Installed Plugins to identify the faulty script.
- If the error persists, rename your active theme folder located in
/wp-content/themes/to force WordPress to use a default theme. - Check your
.htaccessfile for incorrect rewrite rules that may cause server loops. Rename the file to.htaccess_oldand refresh your site to test. - Restore any renamed folders once testing is complete.
Checking DNS and CDN Configuration
- Log in to your domain registrar or DNS management console.
- Verify that your A record and CNAME records point to the correct IP address provided by your hosting provider.
- If you use a CDN such as Cloudflare, log in to your CDN dashboard and check the origin server status.
- Temporarily pause the CDN or switch to DNS Only mode to determine if the 503 error is originating from the CDN edge servers rather than your hosting server.
- Check for any firewall rules or WAF settings that may be blocking legitimate traffic.
Reviewing Server Error Logs
- Open your hosting control panel and navigate to Metrics > Errors.
- Look for specific log entries such as
Resource limit reached,Gateway timeout, orService unavailable. - Note the timestamp of the errors to correlate them with traffic spikes or maintenance windows.
- Provide these log entries to your hosting provider when escalating the issue.
Preventing Future 503 Errors
- Set up server uptime monitoring tools to receive alerts when your website becomes unavailable.
- Optimise your website by compressing images, minifying CSS and JavaScript, and enabling caching.
- Keep your content management system, themes, and plugins updated to the latest versions.
- Review resource usage metrics monthly to identify growth trends before limits are reached.
- Consider upgrading your hosting plan if your website regularly exceeds 80 percent of its allocated CPU or memory resources.
When to Escalate
Contact your hosting provider if:
- The 503 error persists for more than an hour
- You see resource limit warnings in your control panel
- Error logs indicate server-level issues beyond your control
- Your website is critical to business operations and downtime is affecting customers
If you host with us, you don't need to do this yourself — just Open a Ticket and our Brisbane team will get it sorted.
Still Having Issues?
💻 Open a Ticket