• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue AH00124: Request exceeded the limit of 10 internal redirects.....

LionKing

Regular Pleskian
Server operating system version
Linux Ubunto 22.04
Plesk version and microupdate number
Plesk Obsidian Web Host Edition Version 18.0.57 Update #5
I'm seeing this error in our main company website is crashing I'm not sure what is causing it...


AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.

I've changed the log level to "All" in PHP settings. But so far it doesn't reveal any clues to me.

Any ideas? :rolleyes:

Thanks in advance.
Kind regards
 
The preferred URL in Hosting Settings or the SSL settings do not match the configuration of the website. Example: As the "preferred URL" you have defined the "www." spelling, but in your Wordpress you have defined the domain without "www".
 
We always use the non www versions on our servers because there is no need to use "www".
Someone thought it was cool with "www" when the internet was built but totally unnecessary from practical use.

So how can we remove/fix this issue @Peter Debik ?
Kind regards
 
Have you considered looking into your configuration and - for example - setting the preferred URL in "Hosting Settings" to "none"? Did you actually have a different setting there? Did you check your SSL settings - for example the permanent SSL redirect and the SSL settings in your website to match?
 
Hi
I have tested your suggestion but it does not make a difference when you set it to "none". The error message still shows up.

I did a search for this issue again and found this Plesk KB article which actually refers to the .htaccess file:
Website fails to load due to internal redirects: 500 Internal Server Error - Support Cases from Plesk Knowledge Base

However the suggestion:
# BEGIN WordPress RewriteEngine On RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}] RewriteBase / RewriteRule ^index.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L]
refers to single/standalone version of WordPress. Not the WordPress Multisite version (Which we use in our company), .htacess file so I do not know what would look like.
 
Did you also check your SSL/non-SSL setting? Are web server and Wordpress in sync for that?
 
Not only in Hosting settings. You need to define this in Hosting Settings, but you also must make sure that the website uses the same setting. It's the same principle as for www/non-www URLs. You either use https or http, but not a mixture of both.
 
Not only in Hosting settings. You need to define this in Hosting Settings, but you also must make sure that the website uses the same setting. It's the same principle as for www/non-www URLs. You either use https or http, but not a mixture of both.
When we set this up (installed WordPress multisite etc.) we already this did this. We never use "www" version as it is obsolete. So the webserver and our installation is a 100% match.
 
I think "internal redirects" issues are more likely the result of some conflicting or bad .htaccess configurations/settings. These links might be useful:
 
I think "internal redirects" issues are more likely the result of some conflicting or bad .htaccess configurations/settings. These links might be useful:
Thank you, I will definitely check that.
 
Back
Top