Htaccess rewriterule error 500

Yes, there is a rewrite loop for every URI coming from a subdomain here that doesn’t map to a filename or directory.

For example if the client comes in with mail.indst.eu/nofile

• Hit subdomain rule mail.indst.eu for condition !^/mail -> rewrite to mail.indst.eu/mail/nofile
• No longer matches !^/mail, doesn’t hit any external redirect rules, so falls through towards the end.
  • Doesn’t match the rewrite exclusion for existing files or one of the hardcoded exclusions
  • Hits the non-host-bound all-uri rule, gets rewritten to mail.indst.eu/index.php
• Now it matches again the subdomain rule mail.indst.eu for condition !^/mail -> rewrite to mail.indst.eu/mail/index.php
• No longer matches !^/mail, doesn’t hit any external redirect rules, so falls through towards the end.
• Hits the non-host-bound all-uri rule, apparently mail/index.php is not an existing file, so /mail/index.php gets rewritten to /index.php, now we are in an alternating repeat between /index.php and /mail/index.php

/nofile
/mail/nofile (does not exist)
/index.php
/mail/index.php (does not exist)
/index.php
/mail/index.php (does not exist)
...repeat last two...

If you place an index.php in the subdirectories used by the subdomains, then a non-existing file uri on a subdomain will end up at the matching subdomain/index.php files, which for some applications may be what you want.
If you want a serverlevel 404 response, then you have to exclude the subdomain hosts from the catchall rewrite to index.php.

For example

RewriteCond %{HTTP_HOST} !^mail.indst.eu$
RewriteCond %{HTTP_HOST} !^www.statesanalytics.com$
RewriteRule ^.*$ index.php [NC,L]

OR, which might be more succint, and allow more subdomains:

RewriteCond %{REQUEST_URI} !^/mail
RewriteCond %{REQUEST_URI} !^/sa
RewriteRule ^.*$ index.php [NC,L]

Then a non existing uri at mail.indst.eu/starting-path is server level non existing if it doesn’t exist in mail/starting-path

There are other techniques to prevent such loops. If you know that there would always at most be one internal redirect for example, and all rewriterules reside in this one .htaccess then you can do this as first rewriterule in your .htaccess:

RewriteCond %{ENV:REDIRECT_STATUS} !^$
RewriteRule ^(.*)$ - [L]

That stops further internal redirects from this .htaccess. But it would require you to put the external redirect rules that you have before the internal redirect rules. It would not stop the RedirectMatch rules.

Or, if you know that a catchall rewrite to index.php should always be the last word the end mod_rewrite processing with [END]. But in this case that would mean a 404 on the subdomain ends up with the main directory index.php which may not be what you want.

RewriteRule ^.*$ index.php [END]

but when I encounter a 500 Internal Server Error, it gives the default Internal Server Error

The problem is that custom 500 error documents defined «late» in .htaccess simply don’t get triggered for the majority of server errors — which is what’s likely happening here. As Aakash has already quoted, this may come under the realm of a «malformed request». If you check your error log it should state: «core:error».

You stand a better chance of the custom 500 error document being served if it is defined «early» in the main server config (or VirtualHost container).

In fact, it is a bit tricky to simulate a real error that will trigger the custom 500 error document defined in .htaccess.

However, you can manually trigger a 500 error, which will call your custom error handler with something like the following:

RewriteCond %{ENV:REDIRECT_STATUS} ^$
RewriteRule ^ - [R=500]

The check against the REDIRECT_STATUS env var ensures that the internal request for the error document itself does not trigger another 500 error, but a direct request for the error document would also trigger a 500 error. This check is not necessary if you already have an exception in place for error documents.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

This does literally mean that in addition to the 500 error that resulted from the initial request, another 500 error was encountered when trying to serve the custom error document (that is called via an internal subrequest).

The custom error document itself is also processed by the Apache config/.htaccess.

Generally, exceptions need to be made for custom error documents so they can be served without additional processing.

More info: I can get it to throw 500 if I type a trailing slash on a .html page that has had the «.html» removed…

Not sure that this is really part of your question, but this 500 error is the result of a rewrite loop. Specifically:

RewriteCond %{REQUEST_FILENAME}.html -f
RewriteRule ^(.+)$ $1.html [L,QSA]

Request: http://example.com/test/ (with the extra slash)

In this case the %{REQUEST_FILENAME} is /path/to/test (no trailing slash), so the condition %{REQUEST_FILENAME}.html -f is true (/path/to/test.html does exist).

However, the URL-path that is captured by the RewriteRule pattern does contain the trailing slash ie. test/ — it is not the same as the REQUEST_FILENAME in this instance. So the URL gets incorrectly rewritten to test/.html.

And the rewriting starts over again from the top (because the URL has changed)… test/.html.html, test/.html.html.html, etc. (Because the REQUEST_FILENAME is always /path/to/test.)

Did this answer your question?

Thanks for the feedback

There was a problem submitting your feedback. Please try again later.

You may have encountered the infamous 500 internal server error on your WordPress site and going berserk trying to get rid of the error notice. But don’t worry! The easy fixes mentioned in this detailed guide will help you knock the error away in minutes.

Every website on the internet is vulnerable to errors, and so is your WordPress site. The errors may range from bugs in your themes and plugins or due to WordPress hosting issues. While some errors can be fixed with minor tweaks, others may take plenty of your time and would even require external help.

Among the common WordPress errors, the 500 internal server error may appear out of nowhere, limiting access to your website. This blog lists the common causes and fixes to help get acquainted with the error and its solution.

What Is the WordPress 500 Internal Server Error?

The WordPress 500 internal error is an application-side issue and mostly occurs on the server level. Mostly it is caused due to plugin/theme issues, corrupted .htaccess file, database, caching issues, hosting issues, or due to a PHP memory limit.

When you visit a specific URL, the server takes your request to show you the page. In the case of an internal server error, the server fails to show you the page resulting in an error message.

– Example of Internal Server Error

What Causes the 500 Internal Server Error in WordPress?

The 500 internal server error can appear on any site, not just WordPress sites. Mostly it is caused due to plugin or theme issues, but it may also occur due to exhausted PHP memory limit, corrupted files, or coding issues.

The root of this error is on the server side, so the fix also lies there.

How to Fix the 500 Internal Server Error on Your WordPress Site

Since the 500 internal server error on WordPress occurs for various reasons, it has multiple fixes. I recommended following the fixes listed below chronologically to fix the error quickly.

Backup Your WordPress Site

First and foremost, create a backup of your WordPress site. You don’t want to lose anything, so better be safe.

Even if you have implemented extensive security precautions, like using a secure WordPress hosting service or regularly updating WordPress core and plugins, your website data could still be compromised.

Even an innocent coding error can bring down your site. That’s why backing up your WordPress site is critical. You can do it manually or by using the trusted WordPress backup plugins.

Refresh Your Page

Sometimes, even reloading the page can knock the internal server error away, so why not try the simplest solution first?

A server can get overloaded and goes down for some time, and the issue is often fixed with a mere refresh. So, start with a page refresh in your quest to fix the 500 error.

Clear the Browser Cache

Another easy fix to the 500 internal server error is by clearing the cookies and cache. Sometimes, cache files may get corrupted, restricting your access to the site. This step can also help you in bypassing the 404 error and the White Screen of Death.

But before this, you should check if the site is down everywhere via websites like Is it Down Right Now. If it’s only down for you, then you may proceed to clear your browser cache. The method to clear cache & cookies is different for each browser. You can clear them by going to the settings.

If you’re a Chrome user, use the shortcut key combination of Ctrl+Shift+Delete, and proceed with clearing the cookies and cached images.

Reload your page after clearance, and check if the problem persists. If yes, then move on to the next method.

Check Your .htaccess File

A .htaccess file is a key file in all PHP-based applications that controls your website’s configuration. If your .htaccess file is corrupted, it can lead to a 500 internal server error. This file is usually affected by a module or a broken theme installation.

You can fix the error in these cases by accessing the .htaccess file. Follow the steps below to access and fix the .htaccess file.

• If you are a Cloudways user, log in to the Cloudways platform.
• Click servers and select your server.
• Copy your Master Credentials from Server Management, and paste them into the FTP client.

• Click Quickconnect.
• Click applications > public_html
• You’ll see a file named .htaccess in the root directory.

• Now that you have located your .htaccess file, you can download it from the live server to a local location on your PC.
• Open this file in any text editor like Sublime Text 3, Notepad++, Dreamweaver, etc.
• Go to .htaccess on WordPress.org
• Copy and paste the version of the code that fits best for your website
• Save the .htaccess file and upload it to your web server.

The code differs for different WordPress configurations and installations. If you have used WordPress Multisite in WordPress 3.5 or later, then you need to use the following code:

# BEGIN WordPress Multisite
# Using subfolder network type: https://wordpress.org/support/article/htaccess/#multisite
RewriteEngine On
RewriteBase /
RewriteRule ^index.php$ - [L]
# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*.php)$ $2 [L]
RewriteRule . index.php [L]

# END WordPress Multisite

You may deactivate your plugin one after another, refresh, check if the website is working again, and then activate that plugin. This whole process will help you identify the faulty plugin.

Once you’ve found the culprit, you can either remove it or replace it with an updated plugin. If you still get the error even after checking all your plugins, move on to the next step.

Theme Audit

Sometimes a WordPress theme can lead to a 500 internal server error, even if you are using the best WordPress themes. Follow the steps below to switch to the default WordPress theme:

• Go to your WordPress dashboard.
• Click Appearance > Themes.
• Activate the Twenty Twenty-Two theme.
• Your old theme will automatically be deactivated upon a new theme’s activation.

You can change your theme via the FTP client if you can’t access your WordPress dashboard.

• Log in to your FTP client.
• Locate the folder named “theme.” (You may find it in wp-content).
• Rename the “theme” folder.
• Refresh your WordPress site to see if the error still persists.
• If you don’t see the error, it’d mean that your theme caused it, so opt for a new theme.

If you still see the error, try out the next solution.

@ini_set(‘upload_max_size’ , ’64M’);
@ini_set(‘post_max_size’, ’64M’);
@ini_set(‘max_execution_time’, ‘300’);

php_value upload_max_filesize 64M
php_value post_max_size 64M

define(‘WP_MEMORY_LIMIT’, ’64M’);
ini_set(‘post_max_size’, ’64M’);
ini_set(‘upload_max_filesize’, ’64M’);

memory_limit = 64M
upload_max_filesize = 64M
post_max_size = 64M
file_uploads = On

Share your opinion in the comment section.
COMMENT NOW

The error 500 – Internal Server Error is a very common issue in webservers. It can be caused by several reasons. In this article, we will explore the possible causes and present alternatives on how to fix 500 internal server error. This error is similar to the 404.

Article contents:

1.0 The causes of the 500 error
2.0 How to fix 500 internal server error in WordPress sites

2.1 Solution 1 – Reset the .htaccess via WordPress
2.2 Solution 2 – Manually reset the .htacess file
2.3 Solution 3 – Update and deactivate plugins
2.4 Solution 4 – Try to change your theme

3.0 How to fix the 500 error in non-Wordpress sites

3.1 Solution 5 – Check your .htaccess syntax
3.2 Solution 6 – Rename your .htaccess file
3.3 Solution 7 – Enable error displaying in PHP
3.4 Solution 8 – Check your error logs

4.0 Conclusion

The causes of the HTTP error 500

Whenever a web server delivers a web page to the client, it throws HTTP status codes. Each status code means the result of such a request. For example, the HTTP status 200 means success: when a page was delivered and shown correctly.

For example, the status code 404, means the error Page not found. Then, the HTTP error 500 means an internal server error message. Such error 500 is one of the widest HTTP errors and may have several possible causes. In this article, we will approach the most common causes. And of course, show the fixes for them.

Such specific error is most commonly caused by server side issues. Even one single PHP script syntax errors, file permissions or htaccess misconfiguration can cause such error. This error doesn’t depend on the operating system – both Windows and Linux based web servers will present such HTTP status code. Even external resources can cause the 500 error.

How to fix 500 internal server error in WordPress sites

Most of the problems generating the 500 server error in WordPress are caused by issues in the .htaccess file. Some of the problems are caused by plugins or templates. To troubleshoot this issue, we will, first of all, reset the .htaccess file. Then, if it persists, we will look into a problem with plugins or the templates.

The .htaccess file is a common file that defines redirections and behaviours in the web server. cPanel has a default .htaccess file, which is placed inside the root folder of your WordPress blog. For example, our blog is on the root folder of the website. So, the .htaccess file is located inside public_html.

Most of the error 500 issues in WordPress are caused by plugins or a misconfiguration in the .htaccess file. We suggest resetting this file.

There are two methods:

Solution 1: Reset the .htaccess via WordPress admin panel

First of all, open the Permalinks section. It’s located under Settings.

Whenever you make changes to your permalinks structure, WordPress automatically resets the .htaccess file. Please note that resetting this configuration may affect your SEO. Now, we recommend changing the option on this screen. After that, click Save. This way, WordPress will reset your .htaccess file and the error 500 may be solved.

Solution 2: Manually reset the .htaccess file

If you use WordPress, you may want to reset your .htaccess to default. Make sure to copy and keep a backup of your old/current .htacess file.

This is how the default .htaccess file of WordPress looks like. Just empty the .htaccess and. Then, copy and paste this content to your .htaccess:

# BEGIN WordPress

<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

Solution 3: Solve problems in plugins

To help our customers on how to fix 500 internal server error, we have to troubleshoot and try to find the cause of the problem. It’s very common to have plugins or templates generating this issue.

First of all, click on the Installed Plugins option. It’s located under Plugins.

Then, you have to try to update each plugin with such a message. To update, simply click Update now. If after updating every plugin, you still have the 500 internal server error, we recommend deactivating the plugins one by one until you find the problematic one. Simply click on Deactivate.

Solution 4: Change the theme

Sometimes a changed was applied to the theme, and some PHP file may be damaged. To fix the 500 server error, there is another possibility: changing the WordPress theme. To do that, simply go to Themes under the Appearance menu.

Then, locate a different theme, and click Activate.

How to fix this error in non-Wordpress sites

There is a vast possibility of causes of the 500 error in sites that don’t use WordPress. In this section, we will show the most common causes and solutions on how to fix the 500 internal server error problem. Most of the times, this problem is caused by issues in your .htaccess file. This file is always located in your root folder (public_html).

Solution 6 – Check the .htaccess file syntax

Simply edit this .htaccess file, and look for any misconfiguration. We recommend this .htaccess tester. This way, you can copy and paste the contents of your current .htaccess file. This site shows which lines have a bad syntax. It will highlight in red all the problematic lines, for you to fix them.

Solution 7: rename the .htaccess file

You can simply rename this file. It will deactivate it in the server. Just change its name to something like .htacess-old, for example. This way you can see the behaviour of your site without it.

Solution 8: enable error displaying in PHP

By default, PHP shows the 500 errors this way. There is an option that you can enable, in order to force PHP to show on screen the exact error message.

Simply add these lines to the beginning of your PHP file, inside the <?php and ?> tags.

error_reporting(E_ALL);
ini_set('display_errors', 'On');

Now you can see the exact error message, in order to fix the 500 internal server error issue:

Solution 9: Check the error logs in the server

Lastly, if none of the previous solutions worked, we recommend checking the error logs. They will probably show you the reason of the 500 internal server error. In your cPanel control panel, open the Errors option, which is located under Metrics.

Then, all the error messages will be shown.

Conclusion

The 500 internal server error is one of the widest problems in web hosting. There are several possibilities and causes for that. We have helped many hosting customers on how to fix 500 internal server error issue so far. As we explained, there are easy and quick fixes and the toughest ones.

The last possibility is to check the log files if none of the solutions worked for you. Then, after checking the error logs, you can simply search in Google for the exact error message. For sure there will be pages showing their fixes. Least but not last, you may want to check this other article about how to use customized error pages in your site.