Request exceeded the limit of 10 internal redirects due to probable configuration error.
“Request exceeded the limit of 10 internal redirects” (AH00124) in WordPress: causes and what to check
# Common log entries
AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary.
Apache writes this line to its error log, code AH00124, when rewrite rules send a request back through the rules more than 10 times. Visitors see a 500 Internal Server Error. In WordPress, the loop almost always comes from the rules in .htaccess.
Which of these do you see?
The rules rewrite to a path that does not exist, and that path is rewritten again.
Added rules conflict with the WordPress block and send requests in a loop.
Rules written for the old server behave differently on the new one.
Common causes
References
- Apache HTTPD / .htaccess (Advanced Administration Handbook)
- Common WordPress errors (Advanced Administration Handbook)
Rather not fix it yourself? Let WP119 handle it automatically.
A corrupted .htaccess is handled automatically: the system rebuilds the rewrite rules. Fixes are made on a copy of your site in the recovery station and written back only after re-verification passes. In your site’s database, the protected tables (members, comments, orders and form submissions) are copied as structure only. In SSH and FTP mode, the system creates a pre-recovery backup on your host before writing back and restores from it if verification after write-back fails. If the recovery cannot be completed, the recovery fee is refunded in full.
- Initial assessment: Site URL entry
- Copy to the recovery station: Work on a copy
- Diagnosis: Item-by-item checks
- Recovery and verification: Home and inner pages
- Write-back or delivery: Only after verification passes
Use WP119 when the site returns a 500 error and the server log shows this line.
Check my site →