500 Internal Server Error | WordPress.org German

The error message “500 – Internal Server Error” only says that something is not working. The error messages are displayed when debug mode is not in the wp-config.php with the line define( 'WP_DEBUG', true ); is activated, only written to the error log of the web server. If you read the error messages there, you might be able to say more specifically where the problem is. The error can also be caused by an incorrect configuration (e.g. in the .htaccess) are triggered and does not necessarily have to be related to WordPress.

Experience has shown that programming errors are more common in plugins, sometimes in themes and rarely in the WordPress core. A common error analysis method is to temporarily disable the plugins and themes and then re-enable them one at a time to isolate the error by exclusion. The Health Check plugin is helpful here. After installation and activation, it offers you a troubleshooting mode under Tools > Website status, which hides the described deactivation of the theme and plugins. The advantage is that your website visitors will not notice anything about the deactivation and you can look for the cause in peace.

A little extra information would help us better assess your site. To do this, please go to Tools > Website Health > Report, wait a moment until the loading indicator at the top is complete and then copy the website report to your clipboard using the button. You can then please paste it here as a new answer unchanged (please with the accent marks at the beginning and end).

thread creator
timm66

(@timm66)

Hi

The admin page doesn’t work either.
I can only access it via ssh.

The .htaccess looks normal.

good bye
Timm

OK, then “If I restart Apache, the page is displayed…” was probably misinformation?

You can also manually disable the plugins and your theme to test if they are the cause. You can find information in our FAQ.

What happened to the server’s debug mode and error log?

If I were to count how many times I thought that .htaccess on my server it would look “quite normal”… 😀

thread creator
timm66

(@timm66)

Hi

no, that’s still the case, after systemctl restart apache2 it works for one call. I once debug to true and deleted all plugins (via console) and there comes a message with $determined_locale = get_locale();
You can go to the page, meanwhile I left it on true.

The .htaccess file is the one that is in the root of the website, right? So not in a wp folder.

Canke
Timm

Which PHP version are you using? You can query this if you have a file phpinfo.php create with content <?php phpinfo(); and then call up https://example.com/phpinfo.php` in the browser – that would also be a good test of whether your server generally works with PHP.

the .htaccessfile is in the web root directory.

Please post the content of the wp-config.php – Please delete lines with access data and SALT keys before sending.

  • This reply was modified 1 year, 4 months ago by Bego Mario Garde. Reason: Addendum: please post wp-config.php

thread creator
timm66

(@timm66)

Hi

phpinfo, you can have a look, I just uploaded it, the file is coming.

https://tms-itdienst.at/phpinfo.php

7.4.9

good bye
Timm

OK, then the server is basically running, PHP 7.4.9 should also be fine.
At the moment I suspect an outdated locale entry in the wp-config.php or a failed update of the core. In the latter case, it would make sense if you manually download a fresh WordPress version, unpack it, on the server the directory wp-includes and wp-admin delete and then push back up from the fresh files. wp-content and the file wp-config.php may not to be deleted.

the phpinfo.php can you please delete it.

thread creator
timm66

(@timm66)

<?php

/**
 * The base configuration for WordPress
 *
 * The wp-config.php creation script uses this file during the
 * installation. You don't have to use the web site, you can
 * copy this file to "wp-config.php" and fill in the values.
 *
 * This file contains the following configurations:
 *
 * * MySQL settings
 * * Secret keys
 * * Database table prefix
 * * ABSPATH
 *
 * @link https://codex.wordpress.org/Editing_wp-config.php
 *
 * @package WordPress
 */

// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define( 'DB_NAME', 'tms_Webauftritt' );

/** MySQL database username */
define( 'DB_USER', '' );

/** MySQL database password */
define( 'DB_PASSWORD', '' );

/** MySQL hostname */
define( 'DB_HOST', 'localhost' );

/** Database Charset to use in creating database tables. */
define( 'DB_CHARSET', 'utf8mb4' );

/** The Database Collate type. Don't change this if in doubt. */
define( 'DB_COLLATE', 'utf8mb4_unicode_ci' );

/**#@+
 * Authentication Unique Keys and Salts.
 *
 * Change these to different unique phrases!
 * You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
 * You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
 *
 * @since 2.6.0
 */
define( 'AUTH_KEY',         '' );
define( 'SECURE_AUTH_KEY',  '' );
define( 'LOGGED_IN_KEY',    '' );
define( 'NONCE_KEY',        '' );
define( 'AUTH_SALT',        '' );
define( 'SECURE_AUTH_SALT', '' );
define( 'LOGGED_IN_SALT',   '' );
define( 'NONCE_SALT',       '' );

/**#@-*/

/**
 * WordPress Database Table prefix.
 *
 * You can have multiple installations in one database if you give each
 * a unique prefix. Only numbers, letters, and underscores please!
 */
$table_prefix = '****_';

/**
 * For developers: WordPress debugging mode.
 *
 * Change this to true to enable the display of notices during development.
 * It is strongly recommended that plugin and theme developers use WP_DEBUG
 * in their development environments.
 *
 * For information on other constants that can be used for debugging,
 * visit the Codex.
 *
 * @link https://codex.wordpress.org/Debugging_in_WordPress
 */
define( 'WP_DEBUG', false );
define( 'WP_MEMORY_LIMIT', '756M');
/* That's all, stop editing! Happy publishing. */

/** Absolute path to the WordPress directory. */
if ( ! defined( 'ABSPATH' ) ) {
	define( 'ABSPATH', dirname( __FILE__ ) . '/' );
}

/** Sets up WordPress vars and included files. */
require_once( ABSPATH . 'wp-settings.php' );
  • This reply was modified 1 year, 4 months ago by Bego Mario Garde. Reason: Code formatted

Can you please see if anything changes if you

define( 'DB_COLLATE', '' );

use?

I only entered utf8 for DB_CHARSET.

Otherwise, everything looks pretty normal.

thread creator
timm66

(@timm66)

You mean enter that additionally, or instead of utf8?

thread creator
timm66

(@timm66)

Achso delete that below, I’ll do it clearly.

/** Database Charset to use in creating database tables. */
// define( 'DB_CHARSET', 'utf8mb4' );
define( 'DB_CHARSET', 'utf8' );

/** The Database Collate type. Don't change this if in doubt. */
//define( 'DB_COLLATE', 'utf8mb4_unicode_ci' );
define( 'DB_COLLATE', '' );

I would first comment it out like this – then you can roll it back faster if the change doesn’t help. Admittedly a bit of trial and error. It probably boils down to a manual update.

thread creator
timm66

(@timm66)

The .htaccess looks like this:

#This Apache config file was created by Duplicator Installer on 2019-09-18 12:19:29.
#The original can be found in archived file with the name htaccess.orig

# BEGIN WordPress
# Die Anweisungen (Zeilen) zwischen <code>BEGIN WordPress</code> und <code>END WordPress</code> sind
# dynamisch generiert und sollten nur über WordPress-Filter geändert werden.
# Alle Änderungen an den Anweisungen zwischen diesen Markierungen werden überschrieben.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress
  • This reply was modified 1 year, 4 months ago by Bego Mario Garde. Reason: Code formatted

OK, then please change this in the wp-config.php also undo.

.htaccess is also OK.

WordPress Internal Server Error Previous post Troubleshooting: Eliminate WordPress ‘Internal Server Error’ 500
Next post HTTP Error 500 (Internal Server Error): Meaning & how to fix the error