Err_too_many_redirecs when I configure https redirection

Keywords: WordPress - AWS - Technical issue - Secure Connections (SSL/HTTPS)
bnsupport ID: d6d8a33a-bbc6-4f68-7718-380f9504c17a
I am following the steps described in the following guide

but I get the following error ERR_TOO_MANY_REDIRECTS


Hello @jselva,

Note you need to follow approach B. Change this line:

  RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L

With the current domain you want to use. For example:

 RewriteRule ^/(.*)$1 [R,L]

Also, don’t forget to update you wp-config.php file accordingly:

Note: Use

define('WP_SITEURL', 'https://DOMAIN/');
define('WP_HOME', 'https://DOMAIN/');

if you only want to serve it via HTTPS.


It didn’t work, and I can’t find the file either

Hi @jselva,

Could you please run the support tool again so we can check the latest status?




Hello @jselva,

I can access your site correctly:

$ curl -LI
HTTP/1.1 200 OK
Date: Wed, 07 Apr 2021 08:40:49 GMT
Server: Apache
Last-Modified: Tue, 09 Mar 2021 19:39:36 GMT
ETag: "7b9d-5bd1fb5d97c40"
Accept-Ranges: bytes
Content-Length: 31645
Vary: Accept-Encoding
Content-Type: text/html

Could you try this same command? Did you receive the redirections when accessing the main page?


The redirection happens when I follow the steps to activate the https redirect, the site is in production so I can’t leave it down for a long time.


this is the result

Hello @jselva,

Ok, now I fully understand the issue. Could you apply the changes that produce the error, run the support tool again, and share it with us? My suspicion is that there may be another redirection inside <VirtualHost *:443> that could produce the issue.

After that, you can recover the previous files to keep it working.


@davidg sure


Hello @jselva,

I have launched a new machine using your /opt/bitnami/apache2/conf/bitnami/bitnami.conf file and it is working as expected so that file is ok.

As we can see in your screenshots, it is Apache the one that is producing that weird too_many_redirects error. Did you remember to have changed another file? For newer machines, we save the original files and the support tool provides us with the changes that have been implemented, but in your case we don’t have that information.

I have detected these changes on your /opt/bitnami/apps/wordpress/conf/httpd-app.conf file:

#    RewriteEngine On
    #RewriteBase /wordpress/
#    RewriteRule ^index\.php$ - [S=1]
#    RewriteCond %{REQUEST_FILENAME} !-f
#    RewriteCond %{REQUEST_FILENAME} !-d
#    RewriteRule . index.php [L]

Could you change it with the following lines?

    RewriteEngine On
    #RewriteBase /wordpress/
    RewriteRule ^index\.php$ - [S=1]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . index.php [L]

The support of the machine reported that the domain is, which points to 3.XXX.XX.49. However, I can see that points to, as you can see in the link below:

Could you double-check what is your instance IP by executing this from your machine?:


Also, it would be great and faster if you could launch a test machine so we can test your Apache changes directly, but up to you.


@davidg it didn’t work, this is my configuration file /opt/bitnami/apps/wordpress/conf/httpd-app.conf



Hello @jselva,

Then, you would need to point to your machine IP ( instead of



but to the ip ( I do not have external access


skip previous comment, it was internal problem, I will make the change and try