Home › Knowledgebase › KB-1238

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.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

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.

Warning: Before making any changes to your website files, scripts, or configuration settings, create a full backup of your website files and database. Disabling plugins or modifying core files on a live production site can cause further downtime or data loss if not performed correctly. Always test changes in a staging environment where possible.

Quick Fix Steps

  1. Refresh your browser page after a few minutes to see if the error clears.
  2. Check your hosting provider's status page or social media channels for announced maintenance.
  3. Try accessing your website from a different network or mobile device to rule out local caching issues.
  4. If you recently installed a plugin, theme, or script, disable it and test again.
  5. Review your hosting control panel for resource usage alerts or suspension notices.

Detailed Instructions

Checking Hosting Resource Usage

  1. Log in to your hosting control panel, such as cPanel, Plesk, or your provider's custom dashboard.
  2. Navigate to the resource usage or statistics section. In cPanel, go to Metrics > Resource Usage.
  3. Review current CPU, memory, and entry process usage against your plan limits.
  4. Look for 503 entries in the error logs, usually found under Metrics > Errors.
  5. 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.
  6. If resource limits are consistently reached, consider optimising your website code and database or upgrading to a higher hosting plan.

Troubleshooting WordPress Sites

  1. Access your website files via FTP or your hosting control panel's file manager.
  2. Rename the /wp-content/plugins/ folder to /wp-content/plugins_old/ to disable all plugins.
  3. 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.
  4. If the error persists, rename your active theme folder located in /wp-content/themes/ to force WordPress to use a default theme.
  5. Check your .htaccess file for incorrect rewrite rules that may cause server loops. Rename the file to .htaccess_old and refresh your site to test.
  6. Restore any renamed folders once testing is complete.

Checking DNS and CDN Configuration

  1. Log in to your domain registrar or DNS management console.
  2. Verify that your A record and CNAME records point to the correct IP address provided by your hosting provider.
  3. If you use a CDN such as Cloudflare, log in to your CDN dashboard and check the origin server status.
  4. 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.
  5. Check for any firewall rules or WAF settings that may be blocking legitimate traffic.

Reviewing Server Error Logs

  1. Open your hosting control panel and navigate to Metrics > Errors.
  2. Look for specific log entries such as Resource limit reached, Gateway timeout, or Service unavailable.
  3. Note the timestamp of the errors to correlate them with traffic spikes or maintenance windows.
  4. Provide these log entries to your hosting provider when escalating the issue.

Preventing Future 503 Errors

When to Escalate

Contact your hosting provider if:

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?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket