Www.kimbholmes.org redirected you too many times. Try clearing your cookies. ERR_TOO_MANY_REDIRECTS

jota 2018-05-11 10:32:44 UTC #2

This section of our documentation explains that you need to add the SetEnvIf x-forwarded-proto https HTTPS=on line at the top of the file so please edit the httpd-prefix.conf file properly

https://docs.bitnami.com/aws/how-to/configure-elb-ssl-aws/#step-4-modify-the-web-server-configuration-on-the-bitnami-application-instance

SetEnvIf x-forwarded-proto https HTTPS=on

RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]

DocumentRoot "/opt/bitnami/apps/wordpress/htdocs"
...

Then, restart Apache

sudo /opt/bitnami/ctlscript.sh restart apache

As you may know, the process to configure a load balancer in AWS with Bitnami is described in this page of our documentation, did you follow it?

https://docs.bitnami.com/aws/how-to/configure-elb-ssl-aws

Thanks

kaczocht 2018-05-11 15:48:10 UTC #3

Hi Jota,

Yes those were the documents that I originally followed. The SetEnvIf line was originally at the top just above the DocumentRoot line until I found a document that directed the RewriteEngine On block for https to be added to the top. I moved the SetEnvIf line to the top and restarted apache and still get the redirected you too many times error.

Originally I had the DNS from the load balancer IPs added as my A record for the domain but AWS somehow changed one of them to point to another site. I then changed it to the public IP address of the site instead of the A record. This morning I put the A records back to the load balancer DNS IP addresses but it still has an issue. Regardless, the CNAME has been directing to the correct load balancer IP addresses. Here is the setup as of this morning following the httpd-prefix.conf file listing below.

Here is the current httpd-prefix.conf:
GNU nano 2.5.3 File: ...tnami/apps/wordpress/conf/httpd-prefix.conf

SetEnvIf x-forwarded-proto https HTTPS=on
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]

DocumentRoot "/opt/bitnami/apps/wordpress/htdocs"
#Alias /wordpress/ "/opt/bitnami/apps/wordpress/htdocs/"
#Alias /wordpress "/opt/bitnami/apps/wordpress/htdocs"

RewriteEngine On
RewriteCond "%{HTTP_HOST}" ^ec2-([0-9]{1,3})-([0-9]{1,3})-([0-9]{1,3})-([0-9]{1$
RewriteRule "^/?(.*)" "%{REQUEST_SCHEME}://%1.%2.%3.%4%5/$1" [L,R=302,NE]

#Init xip redirection
RewriteEngine On
RewriteCond "%{HTTP_HOST}" ^([0-9]{1,3})\.([0-9]{1,3})\.([0-9]{1,3})\.([0-9]{1,$
RewriteRule "^/?(.*)" "%{REQUEST_SCHEME}://%1.%2.%3.%4.xip.io%5/$1" [L,R=302,NE]
#End xip redirection

Include "/opt/bitnami/apps/wordpress/conf/httpd-app.conf"

Google Domains Setup:

Response returned by Route 53
Response from Route 53 based on the following options.

DNS request sent to Route 53
www.kimbholmes.org. IN A
EDNS0 client subnet IP
24
DNS response code
NOERROR
Protocol
UDP
Response returned by Route 53
18.188.208.207
18.218.137.245

I don't see anything amiss but I've made a few changes to force the redirect. This change was made to .htaccess:

# Begin force ssl
<IfModule mod_rewrite.c>
 RewriteEngine On
 RewriteCond %{SERVER_PORT} 443
 RewriteRule ^(.*)$ https://kimbholmes.org/$1 [R,L]
</IfModule>

I will review my changes and revert.

kaczocht 2018-05-11 16:04:57 UTC #4

I reverted the .htaccess change to force https and it still same issue.

kaczocht 2018-05-11 16:30:51 UTC #5

Here are the listener rules:

Listener ID
Security policy
SSL Certificate
Rules
HTTP : 80
arn...8cc416d1ba77f462
N/A
N/A
Default: forwarding to kimbholmes-blog
View/edit rules

HTTPS : 443
arn...b28bba0bf2123217
ELBSecurityPolicy-2016-08
Default: 72a1cbf8-d30c-4a03-86ef-bbe58064c666 (ACM)
View/edit certificates
Default: forwarding to kimbholmes-blog
View/edit rules

kaczocht 2018-05-11 16:42:48 UTC #6

AWS keeps changing the DNS for the load balancers. I had the network setup in wordpress
Domain Mapping Configuration
As a super admin on this network you can set the IP address users need to point their DNS A records at or the domain to point CNAME record at. If you don't know what the IP address is, ping this blog to get it.

If you use round robin DNS or another load balancing technique with more than one IP, enter each address, separating them by commas.

Server IP Address: 18.220.10.234,18.220.169.45

Those addresses are now: 18.188.208.207,18.218.137.245

Even with that change it still gives too many redirects.

marcos 2018-05-15 10:14:57 UTC #7

Hi @kaczocht,

Is it right to assume that you are using WordPress Multisite (and not WordPress)?

We have seen issues like these before when the specific site (kimbholmes.org) is not properly configured in WordPress Multisite: https://community.bitnami.com/t/when-clicking-the-go-to-administration-on-dashboard-why-it-goes-to-wp-signup-php/56276/8?u=marcos

What is happening is that you have configured your blog to use the domain as your main site. Therefore, when you try to access it via an unknown IP, it will redirect you to the wp-signup.php page of the original blog, because it don't know which blog it is referring to.

This is the expected behavior of WordPress. It can also be customized, e.g. if you want to force a 404 when accessing the blog via an unknown domain/IP.

Note that, in your case, your administration page would be /wp-admin from your main domain.

We recommend you to check how you have configured your sites, and to ensure that there is a site with the "kimbholmes.org" domain.

Please let us know if you have any questions.

Best regards,
Marcos

kaczocht 2018-05-17 18:50:59 UTC #8

Hi Marcos,

Yes I am using WordPress Multisite. I have three domains that I eventually want to put there but I can't get the first one to work. The bnconfig tool will not run for me. It's rights were already set properly to execute and I even ran the chmod u+x on it again but it still comes back with "command not found":

bitnami@ip-172-31-21-198:/opt/bitnami/apps/wordpress$ ls -l
total 7804
drwxr-xr-x 2 bitnami root      4096 Feb 13 16:06 bin
-r-xr--r-- 1 root    root   7963316 Feb 13 15:38 bnconfig
drwxr-xr-x 4 bitnami root      4096 May 14 03:54 conf
drwxrwxr-x 5 bitnami daemon    4096 May 14 04:28 htdocs
drwxr-xr-x 2 root    root      4096 Feb 13 16:05 licenses
-rw-r--r-- 1 root    root        19 Feb 13 16:09 properties.ini
drwxrwxr-x 2 bitnami daemon    4096 May 10 21:49 tmp

bitnami@ip-172-31-21-198:/opt/bitnami/apps/wordpress$ $ sudo bnconfig --machine_hostname kimbholmes.org
$: command not found
bitnami@ip-172-31-21-198:/opt/bitnami/apps/wordpress$ $ sudo ./bnconfig --machine_hostname kimbholmes.org
$: command not found
bitnami@ip-172-31-21-198:/opt/bitnami/apps/wordpress$

Thanks,
Tim

kaczocht 2018-05-18 16:29:59 UTC #9

Hi Marcos,

Copy

bitnami@ip-172-31-21-198:/opt/bitnami/apps/wordpress$ ls -l
total 7804
drwxr-xr-x 2 bitnami root      4096 Feb 13 16:06 bin
-r-xr--r-- 1 root    root   7963316 Feb 13 15:38 bnconfig
drwxr-xr-x 4 bitnami root      4096 May 14 03:54 conf
drwxrwxr-x 5 bitnami daemon    4096 May 14 04:28 htdocs
drwxr-xr-x 2 root    root      4096 Feb 13 16:05 licenses
-rw-r--r-- 1 root    root        19 Feb 13 16:09 properties.ini
drwxrwxr-x 2 bitnami daemon    4096 May 10 21:49 tmp

bitnami@ip-172-31-21-198:/opt/bitnami/apps/wordpress$ $ sudo bnconfig --machine_hostname kimbholmes.org
$: command not found

bitnami@ip-172-31-21-198:/opt/bitnami/apps/wordpress$ $ sudo ./bnconfig --machine_hostname kimbholmes.org
$: command not found

bitnami@ip-172-31-21-198:/opt/bitnami/apps/wordpress$

Thanks,
Tim

ridruejo 2018-05-18 20:05:06 UTC #10

You are pasting an extra leading "$"

kaczocht 2018-05-18 22:19:41 UTC #11

Arghhh! I went through my history on trying to invoke the bnconfig and I did stupidly have the $ in my paste buffer. Having a painful sinus infection for a month that turned into the flu scrambled my brains. I thank you all so much and apologize for my stupidity. The site is working fine now. Thank you Thank you Thank you!

ridruejo 2018-05-18 22:33:05 UTC #12

We have all been there Glad you got it working and have a great weekend!

kaczocht 2018-05-23 01:44:47 UTC #13

I am getting mixed content security error and apache log has "server certificate does NOT include an ID which matches the server name".

I followed instructions for using AWS Certificate Manager per https://docs.bitnami.com/aws/how-to/configure-elb-ssl-aws/#step-4-modify-the-web-server-configuration-on-the-bitnami-application-instance2 but nowhere in there does it have instructions to remove the Bitnami certificate. Is that the problem? Thanks!

marcos 2018-05-23 11:49:13 UTC #14

Hi @kaczocht,

Regarding the Apache warning you mentioned above ("server certificate does NOT include an ID which matches the server name"), it is caused by an Apache server name mismatch.
We will update our documentation and include a case for fixing the warning you mention, but for now, please open "/opt/bitnami/apache2/conf/httpd.conf" and change the following line:

ServerName localhost:80

By this (where "mydomainname.com" is your new URL, e.g., "kimbholmes.org"):

ServerName mydomainname.com

Next, regarding the mixed content error, that happens when you have both HTTP and HTTPS resources getting loaded in a single site.
For instance, if your site is accessed through HTTPS and you're loading CSS stylesheets via HTTP, you will get that warning.
In order to fix that error, you will need to manually update your site address in WordPress Admin panel (wp-admin).
In addition to that, it is recommended to force HTTPS on all sites, you can see how to do it here: https://docs.bitnami.com/virtual-machine/components/apache/#how-to-force-https-redirection-for-an-application-with-apache

Please let us know if you have any question.

Best regards,
Marcos

How to fix "server certificate does NOT include an ID which matches the server name"

Bitnami Wordpress Multisite GCP: self-signed certificates - where to start

My amazon ec2 instance with bitnami wordpress get those errors

kaczocht 2018-05-24 16:49:44 UTC #15

Hi Marcos,

I had the httpd.conf changed to my domain for many weeks. I even tried to change it with and without the "www." and the error_log reflects the domain I have it there (either with or without the www when I change and restart):

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
ServerName www.kimbholmes.org:80

#

[Thu May 24 16:43:14.560848 2018] [mpm_event:notice] [pid 21040:tid 139705179522816] AH00491: caught SIGTERM, shutting down
[Thu May 24 16:43:18.703339 2018] [ssl:warn] [pid 29339:tid 140323064895232] AH01909: www.kimbholmes.org:443:0 server certificate does NOT include an ID which matches the server name
[Thu May 24 16:43:18.745521 2018] [ssl:warn] [pid 29340:tid 140323064895232] AH01909: www.kimbholmes.org:443:0 server certificate does NOT include an ID which matches the server name
[Thu May 24 16:43:18.765905 2018] [mpm_event:notice] [pid 29340:tid 140323064895232] AH00489: Apache/2.4.29 (Unix) OpenSSL/1.0.2n configured -- resuming normal operations
[Thu May 24 16:43:18.765938 2018] [core:notice] [pid 29340:tid 140323064895232] AH00094: Command line: '/opt/bitnami/apache2/bin/httpd.bin -f /opt/bitnami/apache2/conf/httpd.conf -D DISABLE_BANNER'

I already followed the instructions to force SSL redirection and the mixed case issue surfaced after that. I was able to fix the mixed content by using the plugin: WP Offload S3 and forcing https for all content.

Regarding the apache error_log, I'm not sure what next to do since everything appears to be configured correctly and I'm not seeing any adverse effects other than the errors in the log.

Thanks!

marcos 2018-05-25 10:10:05 UTC #16

Hi @kaczocht,

It seems you are not properly configuring the "ServerName" property.

Please run the following commands:

$ openssl x509 -in /opt/bitnami/apache2/conf/server.crt -noout -text | grep CN= 
$ openssl x509 -in /opt/bitnami/apache2/conf/server.crt -noout -text | grep DNS:

You should see something like this:

        Issuer: O=Bitnami, OU=Certificate generated at boot time, CN=www.example.com
        Subject: O=Bitnami, OU=Certificate generated at boot time, CN=www.example.com

Supposing that what comes after "CN=" is "www.example.com", you will have to put exactly that in the ServerName (the port can also be added), e.g.:

ServerName www.example.com

That is, if the "www." does not exist in the CN/DNS field in your SSL certificate, you should avoid it.

Check a Let's Encrypt certificate example below:

        Issuer: C=US, O=Let's Encrypt, CN=Let's Encrypt Authority X3
        Subject: CN=www.mydomain.com
                DNS:mydomain.com, DNS:www.myotherdomain.com, DNS:myotherdomain.com

In this case, you should preferably chose "www.mydomain.com".

Let us know if you have any questions.

My amazon ec2 instance with bitnami wordpress get those errors

kaczocht 2018-05-30 01:52:22 UTC #17

Hi Marcos - Thank you for the reply. I am using AWS Amazon issued SSL certificate and I followed those instructions. No where did they have state to update the /opt/bitnami/apache2/conf/server.crt. It seems as if apache is still using the Bitnami default cert. This is the result:

openssl x509 -in /opt/bitnami/apache2/conf/server.crt -noout -text | grep CN=

Issuer: O=Bitnami, OU=Certificate generated at boot time, CN=example.com

Subject: O=Bitnami, OU=Certificate generated at boot time, CN=example.com

Are there instructions that are missing to replace the /opt/bitnami/apache2/conf/server.crt with the AWS issued cert? Thanks,

Tim

“Before we work on artificial intelligence why don’t we do something about natural stupidity?” —Steve Polyak

Sent: Friday, May 25, 2018 at 5:20 AM

From: marcos <answers@bitnami.com>

To: kaczocht@mail.com

Subject: [Bitnami Community] [WordPress] Www.kimbholmes.org redirected you too many times. Try clearing your cookies. ERR_TOO_MANY_REDIRECTS marcos

May 25

Hi @kaczocht,

It seems you are not properly configuring the "ServerName" property.

Please run the following commands:

$ openssl x509 -in /opt/bitnami/apache2/conf/server.crt -noout -text | grep CN= 
$ openssl x509 -in /opt/bitnami/apache2/conf/server.crt -noout -text | grep DNS:

You should see something like this:

        Issuer: O=Bitnami, OU=Certificate generated at boot time, CN=www.example.com
Supposing that what comes after "CN=" is "www.example.com", you will have to put exactly that in the ServerName (the port can also be added), e.g.:

ServerName www.example.com
That is, if the "www." does not exist in the CN/DNS field in your SSL certificate, you should avoid it.


Check a Let's Encrypt certificate example below:


 

        Issuer: C=US, O=Let's Encrypt, CN=Let's Encrypt Authority X3
                DNS:mydomain.com, DNS:www.myotherdomain.com, DNS:myotherdomain.com

In this case, you should preferably chose "www.mydomain.com".
Let us know if you have any questions.





Visit Topic or reply to this email to respond.





In Reply To




kaczocht

May 24Hi Marcos, I had the httpd.conf changed to my domain for many weeks. I even tried to change it with and without the "www." and the error_log reflects the domain I have it there (either with or without the www when I change and restart): # # ServerName gives the name and port that the server u…


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

marcos 2018-05-30 11:32:42 UTC #18

Hi @kaczocht,

As per your comment above, it seems you did not replace the certificate properly.

You need to download your certificate files to your instance, and place them inside the following directory:

/opt/bitnami/apache2/conf/

The SSL private key must be named "server.key", and the SSL certificate public key or certificate must be named "server.crt", just like the current files. It is documented here: https://docs.bitnami.com/aws/components/apache/#how-to-enable-https-support-with-ssl-certificates

Once you have replaced your certificate, you must restart your Apache server:

sudo /opt/bitnami/ctlscript.sh restart apache

Once that is done, the command below should give you a new output, different than the previous:

openssl x509 -in /opt/bitnami/apache2/conf/server.crt -noout -text | grep CN=

kaczocht 2018-05-31 18:54:39 UTC #19

Hi Marcos, I followed this Bitnami documentation which does not mention updating the certificate per the document you provided: https://docs.bitnami.com/aws/how-to/configure-elb-ssl-aws/#step-4-modify-the-web-server-configuration-on-the-bitnami-application-instance I don't see anywhere in those instructions on downloading the AWS certificate. I will spelunk around for that.

Thanks,

Tim

“Before we work on artificial intelligence why don’t we do something about natural stupidity?” —Steve Polyak

Sent: Wednesday, May 30, 2018 at 1:42 PM

From: marcos <answers@bitnami.com>

To: kaczocht@mail.com

Subject: [Bitnami Community] [WordPress] Www.kimbholmes.org redirected you too many times. Try clearing your cookies. ERR_TOO_MANY_REDIRECTS marcos

May 30

Hi @kaczocht,

As per your comment above, it seems you did not replace the certificate properly.

You need to download your certificate files to your instance, and place them inside the following directory:

/opt/bitnami/apache2/conf/

Once you have replaced your certificate, you must restart your Apache server:

sudo /opt/bitnami/ctlscript.sh restart apache

Once that is done, the command below should give you a new output, different than the previous:

openssl x509 -in /opt/bitnami/apache2/conf/server.crt -noout -text | grep CN=

Visit Topic or reply to this email to respond.

In Reply To

kaczocht

May 30Hi Marcos - Thank you for the reply. I am using AWS Amazon issued SSL certificate and I followed those instructions. No where did they have state to update the /opt/bitnami/apache2/conf/server.crt. It seems as if apache is still using the Bitnami default cert. This is the result: openssl x509 …

Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

kaczocht 2018-05-31 19:14:20 UTC #20

Hi Marcos,

I give up! I do not see how to download the certificate in AWS Certificate Manager. It is a AWS certificate. How do I get that AWS private certificate so I can load it into the server.key?

Thanks!

abjimenez 2018-06-06 10:11:44 UTC #21

Hi @kaczocht,

As far as I know, you can't download certificates from AWS Certificate Manager. It only works with specific services such as Elastic Load Balancing, Amazon CloudFront...

Could you follow the indications that @marcos said in his previous post?

Best regards,
Andrés Bono.

Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now!