Tjeneste-oppgradering: Følg linken for nærmere status vedrørende migrering, for generelle spørsmål og svar se vårt hjelpesenter.

Why is there a 503 error on my website?


Added: 07.01.2013 13:31:44     Last updated: 21.09.2021 14:30:38

What is a 503 error message?
A 503 error message is the web server that provides an HTTP response from, for example, a browser. It provides little information about where the problem is and therefore troubleshooting often has to be done to correct the problem.
The error message can be displayed in several ways:

  • 503 Service Unavailable
  • 503 Service Temporarily Unavailable
  • 503 Error
  • HTTP 503
  • HTTP Server Error 503
  • Http / 1.1 Service Unavailable
  • HTTP Error 503

What is often the cause of the error message?
There can be many causes for the error message, but in most cases these occur due to the errors listed below. Therefore, start by checking list below and go down until the problem is identified:

  • WordPress plugin or theme.
  • Disk space in the web space is full.
  • PHP version.
  • Wrong in the script or code.
  • All account resources are used.
  • The site is under attack such as brute force attack or DDoS.

How to troubleshoot and fix the problem?
As mentioned earlier, it may be difficult to find the cause, but here are some suggestions that should be tried before contacting support.

  • Disable WordPress plugins.
    Rename the plugin folder to for example plugins.old or plugins.deactivated and reload the page.
  • Change PHP version.
  • Change theme in WordPress.
    This is done in phpmyadmin under the _options table in the option_value column. Set a default theme such as twentynineteen.
  • Enable WP debug. Change WP_DEBUG to true in the wp-config.php file.
  • Check the disk usage inside cPanel.
  • Check the error_log file in the root of your domain name. Often, such error messages are written to this file.
  • Check the use of resources in your account.
  • Refresh the webpage sometimes within a few minutes in case there may be problems locally on the web server.
  • Run a diagnosis trough our customer pages.

If the problem persists, contact support so that we can check further and provide other recommendations to fix the problem.