{"id":22422,"date":"2026-08-28T07:57:49","date_gmt":"2026-08-28T05:57:49","guid":{"rendered":"https:\/\/www.curiaweb.ch\/?post_type=docs&#038;p=22422"},"modified":"2026-08-28T07:57:49","modified_gmt":"2026-08-28T05:57:49","password":"","slug":"how-to-fix-wordpress-error-500","status":"publish","type":"docs","link":"https:\/\/www.curiaweb.ch\/en\/hilfe\/wordpress\/wordpress-fehler-500-beheben\/","title":{"rendered":"Fixing Error 500 in WordPress: Finding Causes and Solving Systematically"},"content":{"rendered":"<p class=\"wp-block-paragraph\">A <strong>500 Internal Server Error<\/strong> is one of the more unpleasant WordPress errors because the message initially reveals very little about the actual cause. The web server received the request, but could not successfully process it due to an internal problem.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a WordPress website, among other things, PHP errors, plugins, themes, faulty rules in <code>.htaccess<\/code>, an exhausted storage limit, or problems after a modification or update may be involved.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It is therefore important not to confuse the HTTP 500 status with the actual cause of the error.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Briefly explained:<\/strong> A 500 error does not automatically mean that WordPress is broken. First, check when and where the error occurs. Then, check the error logs and the changes made immediately before. Only based on this information should you [check\/handle] plugins, theme, PHP, <code>.htaccess<\/code> or investigate other components in a targeted manner.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">What does HTTP 500 Internal Server Error mean?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">HTTP status codes describe the result of a request between client and server.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A status code from the 5xx group indicates a server-side error. In <strong>500 Internal Server Error<\/strong> the server could not complete the request as intended due to an internal error.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Thus, the report initially describes only the result \u2013 not its specific cause.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, the following areas can be involved in WordPress:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>PHP<\/li>\n\n\n\n<li>WordPress Core<\/li>\n\n\n\n<li>Plugins<\/li>\n\n\n\n<li>Themes or child themes<\/li>\n\n\n\n<li><code>.htaccess<\/code> or rewrite rules<\/li>\n\n\n\n<li>PHP memory limit<\/li>\n\n\n\n<li>Files and file permissions<\/li>\n\n\n\n<li>Server configuration<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">What does a 500 error look like?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the browser, web server, and hosting environment, the visible message may vary.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical designations include, for example:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>500 Internal Server Error<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">or simply:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>HTTP ERROR 500<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sometimes, instead of an explicit 500 page, a largely blank page or another generic error message appears.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, it is helpful to consider the actual HTTP status and existing server logs.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Check if an HTTP 500 error is actually present<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before you modify WordPress, you should determine the error pattern as precisely as possible.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An HTTP 500 is something different than:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>404 Not Found<\/li>\n\n\n\n<li>403 Forbidden<\/li>\n\n\n\n<li>502 Bad Gateway<\/li>\n\n\n\n<li>503 Service Unavailable<\/li>\n\n\n\n<li>504 Gateway Timeout<\/li>\n\n\n\n<li>DNS error<\/li>\n\n\n\n<li>SSL certificate error<\/li>\n\n\n\n<li>Error establishing a database connection<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If the website cannot be reached at all fundamentally, you should first perform the broader diagnosis under <a href=\"\/en\/help\/wordpress\/wordpress-website-nicht-erreichbar\/\">WordPress website not accessible: systematically check causes<\/a> use.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2. Which areas of the website are affected?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Do not test only the home page.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, access the following areas:<\/p>\n\n\n\n<figure class=\"wp-block-embed\"><div class=\"wp-block-embed__wrapper\">\nhttps:\/\/deine-domain.ch\n<\/div><\/figure>\n\n\n\n<figure class=\"wp-block-embed\"><div class=\"wp-block-embed__wrapper\">\nhttps:\/\/deine-domain.ch\/eine-unterseite\n<\/div><\/figure>\n\n\n\n<figure class=\"wp-block-embed\"><div class=\"wp-block-embed__wrapper\">\nhttps:\/\/deine-domain.ch\/wp-admin\n<\/div><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">This allows the error to be narrowed down further.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Possible situations are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Entire website shows error 500<\/li>\n\n\n\n<li>only the admin area shows error 500<\/li>\n\n\n\n<li>only the frontend is affected<\/li>\n\n\n\n<li>only a single page is affected<\/li>\n\n\n\n<li>Error only occurs with a specific action<\/li>\n\n\n\n<li>Error occurs only sporadically<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">An error that occurs exclusively when submitting a specific form, for example, has a different starting point than a website that responds with HTTP 500 on every request.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">3. What was changed immediately before the error?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The temporal relationship is one of the most important clues when troubleshooting.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Consider whether immediately before the occurrence of the error, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>WordPress has been updated<\/li>\n\n\n\n<li>a plugin was installed<\/li>\n\n\n\n<li>a plugin was activated<\/li>\n\n\n\n<li>a plugin was updated<\/li>\n\n\n\n<li>a theme has been updated<\/li>\n\n\n\n<li>the theme was changed<\/li>\n\n\n\n<li>PHP has been changed<\/li>\n\n\n\n<li><code>.htaccess<\/code> has been edited<\/li>\n\n\n\n<li><code>wp-config.php<\/code> has been changed<\/li>\n\n\n\n<li>PHP code was inserted<\/li>\n\n\n\n<li>a code snippet was activated<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If the error started immediately after a specific change, you should start diagnosing there.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Practical Tip:<\/strong> During troubleshooting, try to change only one component at a time whenever possible. Otherwise, the website might suddenly start working again, but the actual cause will remain unknown.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">4. Check error logs<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In the case of an HTTP 500 error, server or PHP error logs are often much more helpful than the visible browser message.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An error log may contain indications of, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>PHP Fatal Error<\/li>\n\n\n\n<li>Syntax error<\/li>\n\n\n\n<li>non-existent functions or classes<\/li>\n\n\n\n<li>Out of memory<\/li>\n\n\n\n<li>Plugin files<\/li>\n\n\n\n<li>Theme files<\/li>\n\n\n\n<li>Problems with PHP extensions<\/li>\n\n\n\n<li>File or path issues<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Above all, entries whose timestamps match the occurrence of the error are crucial.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, if the error was triggered at 2:32 PM, old warnings from several days prior are usually not the first starting point.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">5. Evaluate file path in error log<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The file path mentioned in a PHP error message can provide an important clue.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A path like:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>wp-content\/plugins\/sample-plugin\/...<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">indicates that code from a plugin is involved in the error.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A path like:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>wp-content\/themes\/beispiel-theme\/...<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">leads in contrast toward the theme or child theme.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, a file path is not always complete proof of the actual root cause. A component can trigger an error that only becomes visible when calling code from another component.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">6. Use WordPress debugging<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When existing server logs are not sufficient, WordPress debugging features can provide additional information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Important constants are:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>WP_DEBUG<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>WP_DEBUG_LOG<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>WP_DEBUG_DISPLAY<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">With the appropriate configuration, WordPress can output error messages, for example, in:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>wp-content\/debug.log<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">log.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">How you can use debugging in a controlled manner on a live website and read logs correctly is covered in detail at <a href=\"\/en\/help\/wordpress\/wordpress-debugging-fehlerprotokolle\/\">Enable WordPress debugging and use error logs<\/a>.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Attention:<\/strong> Detailed PHP error messages should not be permanently displayed publicly on a production website. Error logs can contain internal paths and further technical information.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">7. Check for a plugin as the cause of a 500 error<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Plugins are among the potential causes of an HTTP 500 error in WordPress.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A plugin is particularly suspicious if the error occurs immediately after:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Installation<\/li>\n\n\n\n<li>Activation<\/li>\n\n\n\n<li>Update<\/li>\n\n\n\n<li>Modification of its configuration<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">begun.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the WordPress admin area is still accessible, first deactivate the plugin in question and test the faulty request again.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the error disappears, it should subsequently be clarified why the plugin caused the problem.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">8. Disable plugin when admin area is inaccessible<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a plugin causes the error and the WordPress admin area also no longer works, the plugin in question can be deactivated via file access if you have the appropriate experience.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Plugins are usually located under:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>wp-content\/plugins\/<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An example plugin directory could be:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>wp-content\/plugins\/beispiel-plugin\/<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If this directory is temporarily renamed, WordPress will no longer be able to load the plugin under its previous path.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This method should be used selectively when the affected plugin is known or at least strongly suspected.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">9. If no specific plugin is known<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If no specific plugin is known as the cause, a systematic conflict check may be necessary.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This involves systematically disabling plugins and then gradually re-enabling them until the error can be reproduced.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The goal is not simply to somehow get the website running without plugins. The crucial thing is to identify the component or combination actually involved.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can find the detailed procedure under <a href=\"\/en\/help\/wordpress\/wordpress-plugin-theme-conflicts\/\">Identifying and Resolving Plugin or Theme Conflicts in WordPress<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">10. Check theme as a cause<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The active theme can also contain PHP code that triggers an HTTP 500 error.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is particularly relevant if the error occurs after:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>a theme update<\/li>\n\n\n\n<li>a theme change<\/li>\n\n\n\n<li>a modification of the child theme<\/li>\n\n\n\n<li>to a change in <code>functions.php<\/code><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">occurred.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the admin area is accessible, a suitable current WordPress default theme can be temporarily activated for diagnosis.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the website works again as a result, the previously active theme should be examined in more detail.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">11. Manually investigate topics<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the admin area is not accessible, the theme files are usually located under:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>wp-content\/themes\/<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The directory of the active theme can be temporarily renamed for targeted diagnostics.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, for WordPress to be able to fall back on a different theme afterwards, a suitable alternative theme must be installed.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Important:<\/strong> A theme change can significantly alter the appearance and certain functions of the website. In this case, it serves diagnostic purposes and should not be confused with a final design decision.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">12. .htaccess as a possible cause<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">On Apache-based or compatible web server configurations, WordPress can use the file:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>.htaccess<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">for rewrite rules and further configurations.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Faulty directives or rules can cause an HTTP 500 error under certain conditions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This can happen, for example, after:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>manual processing<\/li>\n\n\n\n<li>Changes made by a plugin<\/li>\n\n\n\n<li>Insertion of inappropriate server rules<\/li>\n\n\n\n<li>Migration between different server environments<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">occur.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">13. Do not simply delete .htaccess<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If <code>.htaccess<\/code> if suspected to be the cause, you should back up the existing file first.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">One possible diagnosis is to temporarily rename it, for example to:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>.htaccess-backup<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">and then test the website again.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the website works again afterwards, this is a strong indication that a rule in the previous file was involved.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Attention:<\/strong> A <code>.htaccess<\/code>- File may contain security rules, redirects or other custom configurations besides WordPress permalinks. Therefore, do not overwrite it without checking.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">14. Regenerate WordPress permalink rules<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When the admin area is accessible again and a standard WordPress permalink configuration is used, the rewrite rules can be [reset\/flushed] via:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Settings \u2192 Permalinks<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">be rewritten by saving the settings.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is particularly relevant for permalink and rewrite issues.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If your actual error pattern concerns HTTP 404, you can find the detailed procedure under <a href=\"\/en\/help\/wordpress\/wordpress-fehler-404-beheben\/\">Fix 404 error in WordPress and repair permalinks<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">15. Error after a PHP version change<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the HTTP 500 error occurred immediately after changing the PHP version, the compatibility of the WordPress components should be checked.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, an older plugin or theme may contain PHP code that no longer works with a newer PHP version.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Conversely, modern plugins may require features that are not available with a very old PHP version.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, do not randomly switch PHP back and forth between different versions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We cover the safe procedure under <a href=\"\/en\/help\/wordpress\/change-wordpress-php-version\/\">Change PHP version for WordPress and check compatibility<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">16. PHP Memory Limit as the cause<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a PHP process requires more memory than allowed, the execution can fail with a fatal error.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An error log frequently contains a message with a component such as:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>Allowed memory size ... exhausted<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the environment, such an error can also manifest as an HTTP 500.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, that does not automatically mean that the memory limit should simply be set as high as possible.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">High memory consumption can indicate, for example, a plugin, a complex operation, or a programming error.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We discuss the exact diagnosis under <a href=\"\/en\/help\/wordpress\/wordpress-php-memory-limit\/\">PHP Memory Limit in WordPress: Identify and fix errors<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">17. Differentiate between WP_MEMORY_LIMIT and PHP memory_limit<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In the event of memory issues, it is important not to confuse various limit values with one another.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">PHP has, among other things, the setting:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>memory_limit<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress also knows constants such as:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>WP_MEMORY_LIMIT<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">and for certain administrative processes:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>WP_MAX_MEMORY_LIMIT<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, a value entered in WordPress cannot arbitrarily override a higher-level server-side limit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, it should first be determined which limit value was actually reached.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">18. Syntax error in PHP code<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A single syntax error can cause PHP to no longer execute a file correctly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This can happen, for example, if immediately before, code in:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>functions.php<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>wp-config.php<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">or another PHP file was inserted or modified.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Even a faulty code snippet can cause a fatal error.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the error occurs immediately after a manual code change, this change should be checked first and, if necessary, reverted to the previous working state.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">19. Typical PHP errors in the log<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">During diagnosis, various types of PHP errors can occur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Particularly relevant, for example, are reports such as:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>PHP Fatal error<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>Uncaught Error<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>Call to undefined function<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>Class ... not found<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>Allowed memory size ... exhausted<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The exact message along with the file path and line number provides significantly more information than the general HTTP 500 status.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">20. Error after WordPress update<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the error occurs immediately after a WordPress core update, you shouldn&#x27;t automatically assume that WordPress itself is faulty.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An update can, for example, resolve an existing incompatibility with:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>an older plugin<\/li>\n\n\n\n<li>an older theme<\/li>\n\n\n\n<li>custom code<\/li>\n\n\n\n<li>an unsuitable PHP version<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">make visible.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, check error logs and involved components first.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">21. Incomplete WordPress Update<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If an update is interrupted, files may not be completely updated under certain circumstances.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This can result in an inconsistent installation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, before replacing WordPress core files, you should check whether there are actually any signs of missing or damaged core files.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The distinction between WordPress Core and the following is particularly important:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>wp-content\/<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dort befinden sich unter anderem Plugins, Themes und Uploads. Dieser Bereich darf bei einer Core-Reparatur nicht un\u00fcberlegt \u00fcberschrieben werden.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">22. Fehlerhafte oder fehlende Dateien<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ein HTTP-500-Fehler kann auch auftreten, wenn ben\u00f6tigte PHP-Dateien fehlen, besch\u00e4digt oder nicht lesbar sind.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Possible causes can include, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>unterbrochener Upload<\/li>\n\n\n\n<li>fehlgeschlagenes Update<\/li>\n\n\n\n<li>manuelles L\u00f6schen<\/li>\n\n\n\n<li>unvollst\u00e4ndige Migration<\/li>\n\n\n\n<li>fehlerhafte Wiederherstellung<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Das Error Log enth\u00e4lt in solchen F\u00e4llen h\u00e4ufig Hinweise auf die betroffene Datei.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">23. Dateiberechtigungen pr\u00fcfen \u2013 aber nicht blind ver\u00e4ndern<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ungeeignete Datei- oder Verzeichnisberechtigungen k\u00f6nnen verhindern, dass der Webserver ben\u00f6tigte Dateien korrekt lesen oder ausf\u00fchren kann.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Die konkrete Konfiguration h\u00e4ngt jedoch von der Hosting-Umgebung ab.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Attention:<\/strong> Setze nicht pauschal alle Dateien oder Verzeichnisse auf weit offene Berechtigungen wie <code>777<\/code>, nur um einen Fehler zu beseitigen. Das kann ein erhebliches Sicherheitsproblem erzeugen und ist keine fachgerechte Reparatur.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">24. Besitzer und Berechtigungen sind nicht dasselbe<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Neben klassischen Dateiberechtigungen kann auf Serverebene auch relevant sein, welchem Benutzer beziehungsweise welcher Gruppe Dateien geh\u00f6ren.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bei einer normalen WordPress-Verwaltung im Hosting sollte dies nicht wahllos manuell ver\u00e4ndert werden.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Probleme k\u00f6nnen beispielsweise nach manuellen Servermigrationen oder Datei\u00fcbertragungen mit ungeeigneten Benutzerrechten auftreten.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">25. PHP-Erweiterungen und Serverumgebung<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Plugins oder Themes k\u00f6nnen bestimmte PHP-Erweiterungen voraussetzen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Fehlt eine ben\u00f6tigte Erweiterung, kann die Software je nach Programmierung mit einer verst\u00e4ndlichen Meldung reagieren \u2013 oder mit einem PHP-Fehler abbrechen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Das Error Log kann dann beispielsweise auf eine nicht vorhandene Funktion oder Klasse hinweisen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Installiere oder aktiviere PHP-Erweiterungen nicht auf Verdacht. Pr\u00fcfe zun\u00e4chst die Anforderungen der betroffenen Software.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">26. Fehler nur bei einer bestimmten Aktion<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ein HTTP 500 muss nicht bei jedem Seitenaufruf auftreten.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">M\u00f6glicherweise erscheint der Fehler nur bei:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Speichern eines Beitrags<\/li>\n\n\n\n<li>\u00d6ffnen einer bestimmten Seite<\/li>\n\n\n\n<li>Import gro\u00dfer Datenmengen<\/li>\n\n\n\n<li>Export<\/li>\n\n\n\n<li>Erstellen eines Backups<\/li>\n\n\n\n<li>Ausf\u00fchren eines bestimmten Plugins<\/li>\n\n\n\n<li>Absenden eines Formulars<\/li>\n\n\n\n<li>WooCommerce-Aktion<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">In diesem Fall ist die konkrete Aktion ein wichtiger Teil der Diagnose.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Reproduziere den Fehler nach M\u00f6glichkeit kontrolliert und pr\u00fcfe unmittelbar danach die entsprechenden Logeintr\u00e4ge.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">27. Fehler nur im WordPress-Adminbereich<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn das Frontend funktioniert, aber bestimmte Bereiche unter:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>\/wp-admin\/<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">einen HTTP-500-Fehler erzeugen, sollte untersucht werden, welche Komponenten speziell dort ausgef\u00fchrt werden.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ein Plugin kann beispielsweise ausschlie\u00dflich bei administrativen Aktionen zus\u00e4tzlichen Code laden.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Auch ein h\u00f6herer Speicherbedarf bestimmter Backend-Prozesse kann eine Rolle spielen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">28. Fehler nur im Frontend<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Funktioniert der Adminbereich, aber das Frontend zeigt HTTP 500, k\u00f6nnen unter anderem Theme, Templates, Frontend-Plugins oder bestimmte Inhalte beteiligt sein.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Teste unterschiedliche Seiten und pr\u00fcfe, ob der Fehler \u00fcberall oder nur bei bestimmten Seitentypen auftritt.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">29. Fehler nur auf einer einzelnen Seite<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn fast die gesamte Website funktioniert und nur eine bestimmte URL einen HTTP-500-Fehler erzeugt, ist ein globaler Serverausfall eher unwahrscheinlich.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Untersuche dann insbesondere:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Inhalt der Seite<\/li>\n\n\n\n<li>verwendete Bl\u00f6cke<\/li>\n\n\n\n<li>Shortcodes<\/li>\n\n\n\n<li>Template<\/li>\n\n\n\n<li>Page Builder<\/li>\n\n\n\n<li>Forms<\/li>\n\n\n\n<li>Plugins, die nur auf dieser Seite aktiv werden<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Ein Blick ins Error Log unmittelbar nach dem Aufruf dieser URL ist besonders hilfreich.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">30. Sehr lange Prozesse und Timeouts<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Eine aufwendige PHP-Anfrage kann technische Zeitlimits erreichen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Das kann beispielsweise bei:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>grossen Importen<\/li>\n\n\n\n<li>Backups<\/li>\n\n\n\n<li>Image processing<\/li>\n\n\n\n<li>umfangreichen Datenoperationen<\/li>\n\n\n\n<li>externen API-Abfragen<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">occur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bevor Ausf\u00fchrungszeiten einfach erh\u00f6ht werden, sollte gepr\u00fcft werden, warum der Prozess so lange ben\u00f6tigt.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">31. Ressourcenlimits richtig einordnen<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Je nach Hosting-Umgebung stehen einer Website definierte Ressourcen zur Verf\u00fcgung.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Das Erreichen eines Limits kann Anfragen beeinflussen. Ein Ressourcenlimit ist jedoch nicht automatisch die eigentliche Ursache.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Beispielsweise kann ein einzelnes fehlerhaftes Plugin ungew\u00f6hnlich viel CPU oder Arbeitsspeicher beanspruchen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Die richtige Frage lautet deshalb nicht nur:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>Welches Limit wurde erreicht?<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">sondern auch:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>Warum wurde dieses Limit erreicht?<\/code><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">32. Cache verursacht normalerweise keinen PHP-Fatal-Error<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Cache-Systeme k\u00f6nnen eine zuvor erzeugte Fehlerseite zwischenspeichern oder nach einer Reparatur einen veralteten Zustand anzeigen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Das Leeren des Caches kann deshalb nach einer Fehlerbehebung sinnvoll sein.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Es ersetzt aber keine Diagnose eines serverseitigen Fehlers.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Practical Tip:<\/strong> Wenn das Error Log einen konkreten PHP Fatal Error nennt, konzentriere dich zun\u00e4chst auf diesen Fehler. \u201eCache l\u00f6schen\u201c ist keine Reparatur f\u00fcr fehlerhaften PHP-Code.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">33. Security-Plugins und Serverregeln<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Sicherheitsl\u00f6sungen k\u00f6nnen Server- beziehungsweise Rewrite-Regeln ver\u00e4ndern oder Zugriffe beeinflussen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn ein HTTP-500-Fehler unmittelbar nach einer \u00c4nderung an einer Sicherheitsl\u00f6sung auftritt, sollte auch diese Konfiguration gepr\u00fcft werden.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Deaktiviere Sicherheitsmechanismen jedoch nicht pauschal und dauerhaft, ohne die Auswirkungen zu kennen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">34. Weiterleitungsregeln pr\u00fcfen<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Fehlerhafte Regeln in <code>.htaccess<\/code> oder anderen Konfigurationsebenen k\u00f6nnen ebenfalls Probleme verursachen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Besonders nach Migrationen solltest du pr\u00fcfen, ob alte Regeln f\u00fcr:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Domains<\/li>\n\n\n\n<li>Verzeichnisse<\/li>\n\n\n\n<li>HTTPS<\/li>\n\n\n\n<li>www beziehungsweise non-www<\/li>\n\n\n\n<li>Safety features<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">noch zur neuen Umgebung passen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">35. Fehler nach einer Website-Migration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn HTTP 500 unmittelbar nach einem Umzug auftritt, k\u00f6nnen zus\u00e4tzliche Ursachen infrage kommen:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>andere PHP-Version<\/li>\n\n\n\n<li>andere PHP-Konfiguration<\/li>\n\n\n\n<li>inkompatible <code>.htaccess<\/code>-Regeln<\/li>\n\n\n\n<li>missing files<\/li>\n\n\n\n<li>unvollst\u00e4ndige \u00dcbertragung<\/li>\n\n\n\n<li>unterschiedliche Servermodule<\/li>\n\n\n\n<li>falsche Dateiberechtigungen<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Vergleiche deshalb die alte und neue Umgebung, bevor du WordPress neu installierst.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">36. WordPress nicht vorschnell neu installieren<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Eine Neuinstallation von WordPress ist bei einem HTTP-500-Fehler normalerweise nicht der erste sinnvolle Schritt.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn beispielsweise ein Plugin einen Syntaxfehler verursacht, \u00e4ndert eine Neuinstallation des WordPress-Core nichts an diesem Plugin.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ebenso repariert eine Neuinstallation keine ungeeignete PHP-Version oder fehlerhafte individuelle Serverregel.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Diagnose sollte deshalb vor Neuinstallation kommen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">37. Backup nicht automatisch zur\u00fcckspielen<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Auch ein vollst\u00e4ndiger Restore ist nicht bei jedem Fehler 500 die beste erste Ma\u00dfnahme.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn das Error Log beispielsweise eindeutig ein einzelnes Plugin nennt, kann dessen Deaktivierung wesentlich zielgerichteter sein.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bei dynamischen Websites kann ein Restore zudem neuere Daten \u00fcberschreiben.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ein Backup ist besonders wertvoll, wenn:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Dateien besch\u00e4digt wurden<\/li>\n\n\n\n<li>eine \u00c4nderung nicht sauber r\u00fcckg\u00e4ngig gemacht werden kann<\/li>\n\n\n\n<li>ein bekannter funktionierender Stand wiederhergestellt werden muss<\/li>\n\n\n\n<li>gr\u00f6\u00dfere \u00c4nderungen an Dateien oder Datenbank vorgenommen wurden<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">38. Fehler 500 nach Backup-Restore<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn der Fehler erst nach einer Wiederherstellung auftritt, sollte gepr\u00fcft werden, ob:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>alle Dateien vollst\u00e4ndig wiederhergestellt wurden<\/li>\n\n\n\n<li>Datenbank und Dateien zum selben Stand geh\u00f6ren<\/li>\n\n\n\n<li>die PHP-Version passt<\/li>\n\n\n\n<li><code>.htaccess<\/code> zur aktuellen Serverumgebung passt<\/li>\n\n\n\n<li>Dateiberechtigungen korrekt sind<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Ein Restore ist nur dann zuverl\u00e4ssig, wenn der wiederhergestellte Zustand technisch konsistent ist.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">39. Fehlerprotokoll nach jeder \u00c4nderung erneut pr\u00fcfen<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn du eine vermutete Ursache behoben hast, rufe die betroffene URL erneut auf und pr\u00fcfe anschlie\u00dfend das Log.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dadurch kannst du feststellen:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ob derselbe Fehler erneut auftritt<\/li>\n\n\n\n<li>ob ein neuer Fehler sichtbar wird<\/li>\n\n\n\n<li>ob die Anfrage jetzt erfolgreich verarbeitet wird<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Bei komplexen Fehlerketten kann nach Behebung des ersten Fehlers ein zweiter sichtbar werden.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">40. HTTP 500 und kritischer WordPress-Fehler<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ein PHP-Fatal-Error kann sich sowohl als allgemeiner HTTP-500-Fehler als auch \u00fcber WordPress&#8216; eigene Fehlerbehandlung bemerkbar machen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn WordPress ausdr\u00fccklich meldet, dass auf der Website ein kritischer Fehler aufgetreten ist, solltest du auch Recovery Mode und Administrator-E-Mail ber\u00fccksichtigen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Daf\u00fcr haben wir die separate Anleitung <a href=\"\/en\/help\/wordpress\/wordpress-critical-error-white-screen\/\">WordPress shows a white screen or a critical error: What to do?<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">41. Systematische Reihenfolge bei einem WordPress-Fehler 500<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Genaue Fehlermeldung und betroffene URL notieren.<\/li>\n\n\n\n<li>Pr\u00fcfen, welche Bereiche der Website betroffen sind.<\/li>\n\n\n\n<li>Feststellen, was unmittelbar vor dem Fehler ge\u00e4ndert wurde.<\/li>\n\n\n\n<li>Error Logs zum passenden Zeitpunkt kontrollieren.<\/li>\n\n\n\n<li>Genannten Dateipfad und Fehlertyp auswerten.<\/li>\n\n\n\n<li>Bei Bedarf WordPress-Debugging kontrolliert einsetzen.<\/li>\n\n\n\n<li>Verd\u00e4chtiges Plugin oder Theme gezielt pr\u00fcfen.<\/li>\n\n\n\n<li><code>.htaccess<\/code> untersuchen, wenn Hinweise darauf bestehen.<\/li>\n\n\n\n<li>PHP-Version kontrollieren.<\/li>\n\n\n\n<li>Memory-Limit pr\u00fcfen, wenn das Log eine Speicher\u00fcberschreitung zeigt.<\/li>\n\n\n\n<li>Manuelle Code\u00e4nderungen kontrollieren.<\/li>\n\n\n\n<li>Dateien und Berechtigungen nur bei konkretem Verdacht untersuchen.<\/li>\n\n\n\n<li>Fix the root cause specifically.<\/li>\n\n\n\n<li>Betroffene Anfrage erneut testen.<\/li>\n\n\n\n<li>Error Log nochmals kontrollieren.<\/li>\n\n\n\n<li>Frontend und Adminbereich abschlie\u00dfend pr\u00fcfen.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">42. Was du bei einem Fehler 500 besser nicht tun solltest<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>WordPress nicht sofort neu installieren<\/li>\n\n\n\n<li>nicht wahllos alle Plugins l\u00f6schen<\/li>\n\n\n\n<li>nicht gleichzeitig PHP, Theme und Plugins ver\u00e4ndern<\/li>\n\n\n\n<li><code>.htaccess<\/code> nicht ohne Sicherung \u00fcberschreiben<\/li>\n\n\n\n<li>Dateiberechtigungen nicht pauschal auf <code>777<\/code> put<\/li>\n\n\n\n<li>Memory Limit nicht ohne Diagnose beliebig erh\u00f6hen<\/li>\n\n\n\n<li>keine zuf\u00e4lligen PHP-Erweiterungen aktivieren<\/li>\n\n\n\n<li>keinen alten Datenbankstand ohne Pr\u00fcfung einspielen<\/li>\n\n\n\n<li>detaillierte Fehlermeldungen nicht dauerhaft \u00f6ffentlich anzeigen<\/li>\n\n\n\n<li>Server- oder Sicherheitsregeln nicht blind aus fremden Anleitungen \u00fcbernehmen<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">43. Welche Informationen helfen dem CURIAWEB-Support?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn deine WordPress-Website bei CURIAWEB einen HTTP-500-Fehler zeigt, helfen m\u00f6glichst konkrete Angaben bei der Diagnose.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Teile insbesondere mit:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>affected domain<\/li>\n\n\n\n<li>betroffene URL<\/li>\n\n\n\n<li>exact error message<\/li>\n\n\n\n<li>ungef\u00e4hren Zeitpunkt des Fehlers<\/li>\n\n\n\n<li>whether the error occurs permanently or sporadically<\/li>\n\n\n\n<li>whether the frontend and admin area are affected<\/li>\n\n\n\n<li>welche \u00c4nderung unmittelbar davor vorgenommen wurde<\/li>\n\n\n\n<li>ob Plugin, Theme oder PHP k\u00fcrzlich aktualisiert beziehungsweise ge\u00e4ndert wurden<\/li>\n\n\n\n<li>relevanten Logeintrag, sofern vorhanden<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Ein kurzer relevanter Logabschnitt mit Zeitstempel ist normalerweise hilfreicher als ein vollst\u00e4ndiges Fehlerprotokoll mit tausenden \u00e4lteren Eintr\u00e4gen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not send passwords unsolicited.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Summary<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A <strong>500 Internal Server Error<\/strong> bedeutet, dass der Server eine Anfrage aufgrund eines internen Fehlers nicht erfolgreich verarbeiten konnte. Der Statuscode selbst sagt noch nicht, welche WordPress-Komponente daf\u00fcr verantwortlich ist.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bei WordPress geh\u00f6ren PHP-Fehler, Plugins, Themes, <code>.htaccess<\/code>, inkompatible PHP-Versionen, Speicherprobleme und fehlerhafte Dateien zu den m\u00f6glichen Ursachen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Der wichtigste Diagnoseschritt ist deshalb die Auswertung des passenden Error Logs. Fehlertyp, Dateipfad, Zeilennummer und Zeitpunkt liefern h\u00e4ufig wesentlich konkretere Hinweise als die sichtbare 500-Fehlerseite.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00c4ndere anschlie\u00dfend nur die Komponente, f\u00fcr die ein konkreter Verdacht besteht, und teste nach jeder \u00c4nderung erneut. Eine systematische Diagnose ist zuverl\u00e4ssiger und sicherer als WordPress neu zu installieren, s\u00e4mtliche Plugins zu deaktivieren oder Servereinstellungen auf Verdacht zu ver\u00e4ndern.<\/p>","protected":false},"excerpt":{"rendered":"<p>Ein 500 Internal Server Error geh\u00f6rt zu den unangenehmeren WordPress-Fehlern, weil die Meldung zun\u00e4chst kaum etwas \u00fcber die eigentliche Ursache verr\u00e4t. Der Webserver hat die Anfrage erhalten, konnte sie aber aufgrund eines internen Problems nicht erfolgreich verarbeiten. Bei einer WordPress-Website k\u00f6nnen unter anderem PHP-Fehler, Plugins, Themes, fehlerhafte Regeln in .htaccess, ein ausgesch\u00f6pftes Speicherlimit oder Probleme [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_joinchat":[],"footnotes":""},"doc_category":[80],"doc_tag":[],"class_list":["post-22422","docs","type-docs","status-publish","hentry","doc_category-wordpress"],"year_month":"2026-09","word_count":3357,"total_views":"5","reactions":{"happy":"0","normal":"0","sad":"0"},"author_info":{"name":"Silvio Mazenauer","author_nicename":"admin-curia","author_url":"https:\/\/www.curiaweb.ch\/en\/author\/admin-curia\/"},"doc_category_info":[{"term_name":"WordPress","term_url":"https:\/\/www.curiaweb.ch\/en\/hilfe-kategorie\/wordpress\/"}],"doc_tag_info":[],"knowledge_base_info":[],"knowledge_base_slug":[],"_links":{"self":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22422","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/comments?post=22422"}],"version-history":[{"count":1,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22422\/revisions"}],"predecessor-version":[{"id":22424,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22422\/revisions\/22424"}],"wp:attachment":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/media?parent=22422"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_category?post=22422"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_tag?post=22422"}],"curies":[{"name":"WP","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}