5

After the upgrade of my Ubuntu server, I tried open my wordpress website and I got this error in my error.log

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.

message a get when i open the website.

<?php
/**
 * Front to the WordPress application. This file doesn't do anything, but loads
 * wp-blog-header.php which does and tells WordPress to load the theme.
 *
 * @package WordPress
 */

/**
 * Tells WordPress to load the WordPress theme and output it.
 *
 * @var bool
 */
define('WP_USE_THEMES', true);

/** Loads the WordPress Environment and Template */
require( dirname( __FILE__ ) . '/wp-blog-header.php' );

I tried these 2 links bellow but my .htaccess is diferent so did not work.

Apache 2.4 - Request exceeded the limit of 10 internal redirects due to probable configuration error

Request exceeded the limit of 10 internal redirects due to probable configuration error.?

.htaccess /root

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php/$1 [L]
</IfModule>

.htaccess /blog

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /blog/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /blog/index.php [L]
</IfModule>

# END WordPres

apache:

Server version: Apache/2.4.18 (Ubuntu)

someone know how to solve this?

thank you.

Community
  • 1
  • 1
raduken
  • 2,091
  • 16
  • 67
  • 105
  • Maybe, you must move `.htaccess` to `/blog`. – Olaf Dietsche Jan 17 '17 at 16:12
  • hello, this .htaccess it is inside /blog – raduken Jan 17 '17 at 16:15
  • 4
    Did you move your wordpress install? I don't see how just upgrading your server would cause the error? What else did you change? – Panama Jack Jan 17 '17 at 17:03
  • I upgraded everything today, new ubuntu version, sql, mysql, apache, everything, I was just pressing ok ok ok ok :) hahaha – raduken Jan 17 '17 at 18:24
  • 1
    For people who end up here via Google, the solution to `AH00124: Request exceeded the limit of 10 internal redirects due to probable` is probably here https://stackoverflow.com/a/48022336/279564 – Rafa Jun 12 '20 at 22:07

5 Answers5

2

UPDATE .htaccess from given following line of codes

<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```
Vineet Kumar
  • 333
  • 4
  • 7
1

Try to increase the limit however I guess its a loop. The following article should lead you into the correct direction:

https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory

Try with two different .htaccess. In the root folder:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /blog/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /blog/index.php [L]
</IfModule>

# END WordPress

... or just make sure you redirect to the subfolder.

In subfolder:

# 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

Check your permalink settings home_url and blog_url. This may also cause an endless loop. Update your permalinks and search wp_options in order to insert the correct url / domain for your blog.

It also may be an Ubuntu specific configuration error try to raise limits or check for missing libraries like mod_rewrite.

Blackbam
  • 17,496
  • 26
  • 97
  • 150
1

was no php module for apache, and apache was interpreting php as a text.

to solve this i did:

apt-get install libapache2-mod-php

/etc/init.d/apache2 restart

apt-get install php7.0-mysql 

/etc/init.d/apache2 restart
raduken
  • 2,091
  • 16
  • 67
  • 105
1

Being on a shared hoster without access to configuration files, I could solve it in my case by re-saving the permalinks in the wp-admin backend.

WoodrowShigeru
  • 1,418
  • 1
  • 18
  • 25
0

I had a problem with this error message and I solved it.

I had this problem when upgrading from MacOS Catalina to Big Sur.

@vineetkumar and @blackbam put me on the right track.

Here is the modification I had to make in /private/etc/apache2/extra/httpd-vhosts.conf :

 <VirtualHost *:443>
   ServerName vhost_for_https
   ServerAlias localhost
-  DocumentRoot "/Library/WebServer/Documents/anais_website"
+  DocumentRoot "/Library/WebServer/Documents"
   SSLEngine on
   SSLCertificateFile /private/etc/apache2/ssl/certificate.crt
   SSLCertificateKeyFile /private/etc/apache2/ssl/privateKey.key
-  <Directory "/Library/WebServer/Documents/anais_website">
+  <Directory "/Library/WebServer/Documents">
     Options +Indexes +Includes +FollowSymLinks +MultiViews
     AllowOverride All
     Require local
     Require ip 192.168.1.71
  </Directory>
</VirtualHost>
Etienne Tonnelier
  • 2,119
  • 1
  • 15
  • 14