Why is my WordPress blog not accessible?

After installing your WordPress blog, please log into its administration area.

Please enter your full URL here ideas as WordPress address and blog address one. Then redirect your domain to the blog directory in the domain administration.

background: If you set the redirection first, your own blog will not be found and you will not be able to call up the administration. Your URL must then be entered manually in the database used via phpMyAdmin. The same applies to a blog that you create under a subdomain.

Blog address at a subdomain

error 500

A 500 error message indicates an internal server error that is preventing the website from being reached. There are different types of 500 error codes (500, 501, 502, 503, 504 and others).

Below is a description of the most common error messages:

Error message (status code) importance
500 internal server error The server encountered an unexpected condition that prevented it from fulfilling the request (i.e. bringing up the website).
501 Not implemented The server does not support or recognize the functionality required to fulfill the request.
502 Bad Gateway The server received an invalid response from an inbound server it accessed while trying to fulfill the request.
503 Service Unavailable The server is currently unable to process the request due to a temporary overload or scheduled maintenance. Note: The existence of the 503 status code does not mean that a server must use it when it becomes overloaded. Some servers may simply refuse the connection. (e.g. in WordPress maintenance mode, ie the crawler can come back later to see if the website is then reachable again.)
504 gateway timeout The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needs to access to complete the request.
505 HTTP version not supported The server does not support or refuses to support the major version of HTTP used in the request message. The server indicates that it is unable or unwilling to complete the request with the same major version as the client, except with this error message.

If your WordPress website is showing a 500 Internal Server error, there are two possible sources of error:

Either it is an error on the user side or there is a problem with the server.

Below are possible solutions:

1. Reload page
First try reloading the page by pressing the F5 or ctrl/ctrl and F5 keys. If the server was overloaded, the page will appear again. Also open your website in a different browser, such as Chrome or Mozilla, to rule out a problem.

Additionally, you can have your domain verified at the following website: downforeveryoneorjustme.com. This website indicates if the website is actually down by checking the HTTPS status code returned by the server.

2. Clear browser cache
You can either clear your entire browser cache, or you can only update one site at a time. Use the appropriate keyboard shortcut for the following browsers:

  • Windows and Linux browsers: CTRL + F5
  • Apple Safari: SHIFT + Reload toolbar button
  • Chrome and Firefox for Mac: CMD + SHIFT + R

If you want to reset everything, you can clear the entire browser cache.

3. Database connection failed
500 Internal Server errors can also appear due to a database connection failure.
The entire page is blank because no data can be retrieved to render the page because the connection is down. However, this also prevents access to the WordPress dashboard.
Possible problems are:

  • Incorrect database credentials: The WordPress site uses separate login information to connect to the MySQL database.
  • Database is corrupted: With so many moving parts with themes, plugins and users constantly deleting and installing, databases sometimes get corrupted. This may be due to a missing or individually corrupted table, or some information was accidentally deleted.
  • Corrupted files in the WordPress installation.
  • Problems with the database server: eg overload.

4. Check server logs

The logs are in the /wp-content directory. To see where the error is, you can proceed as follows:

  • Add the following code to the wp-config.php file to enable logging:
  • In the wp-config.php set the DEBUG value from FALSE to TRUE.
  • DEBUG mode is disabled by default. However, you can enable it with the following entries in the wp-config.php file:

define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define(‘WP_DEBUG_DISPLAY’, false);

  • The first entry can usually be found in wp-config.php. Missing entries are to be expanded.
  • With this you should be able to find out relatively quickly where the error is and disable it.

WP_DEBUG is generally used to (de)activate the DEBUG mode. If you activate WP_DEBUG_LOG, a file named error.log written. Please note that writes to this directory are allowed. With WP_DEBUG_DISPLAY you can control whether debug messages should be output via HTML.

5. Check plugins and themes
Third-party plugins and themes can easily cause 500 Internal Server errors. Often the error appears immediately after installing such an application or running an update. To clear that up, you can first disable all plugins.

You won’t lose any data if you disable all plugins.

If disabling solves the problem, investigate the culprit. The best way to do this is to activate all plugins individually and reload the page after each activation. If the 500 Internal Server error appears again, you have found the wrongly configured plugin and can, for example, contact the plugin developer or post a support request in the WordPress repository.

Alternatively, in your SFTP program, you can rename the plugins folder to plugins_old, for example, and reload and check the web page. If that works, test each plugin individually by renaming the plugins folder back to “Plugins” and then renaming each plugin folder within the folder until you find the offending plugin.

Make sure the plugins, themes and WordPress app are up to date.

6. Reinstall WordPress
In the very last step, you can completely reinstall the WordPress app in case, for example, WordPress core files have been damaged. First, back up your data (text, images, media files, etc.) and remove the installation. After that, you can reinstall WordPress.

If you set the redirection first, your own blog will not be found and you will not be able to call up the administration. Your URL must then be entered manually in the database used via phpMyAdmin. The same applies to a blog that you create under a subdomain.