32

with my WordPress-Blog, I switch to https. Therefore, I have add the following code to my .htaccess-File. My Problem now is, that I get the issue "Too many Redirects". Thank you for your tips!

Domain is a Subdomain:

https://en.example.com

# Begin Force SSL RewriteEngine On RewriteCond %{SERVER_PORT} !^443$ RewriteRule (.*) https://%{HTTP_HOST}/$1 [R=301,L] # End Force SSL # 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
Improve this question

8 Answers 8

Reset to default
92

Make sure that you define the WP_SITEURL and WP_HOME at wp-config.php 

define('WP_HOME','https://yourdomain.com'); define('WP_SITEURL','https://yourdomain.com');

And add this condition to check if the https at wp-config.php

 if ( isset( $_SERVER['HTTP_X_FORWARDED_PROTO'] ) && 'https' == $_SERVER['HTTP_X_FORWARDED_PROTO'] ) { $_SERVER['HTTPS'] = 'on'; }
Improve this answer
Sign up to request clarification or add additional context in comments.

5 Comments

this method when use external ssl tunnel like cloadflare
After two days of crying I finally fixed it. Yes, I'm using external SSL tunnel - CloudFlare + VPS
Perfect, solved to me using a nginx reverse proxy with HTTPS.
great its working .its cause by cloudflare
That bit about setting $_SERVER['HTTPS'] = 'on'; did the trick when running on Kubernetes and Nginx Ingress
76

I have soved the issue using the below code inside wp-config.php

define('WP_HOME','https://mywebsite.com'); define('WP_SITEURL','https://mywebsite.com'); $_SERVER['HTTPS'] = 'on';
Improve this answer

7 Comments

With Cloudflare $_SERVER['HTTPS'] = 'on'; was enough for me.
This, in combination with adding the rewrite rules in .htaccess worked for me too! Thanks!
This saved my life. I spent full week to fix TOO MANY REDIRECTS error but did not get success. But these small but important lines saved me.
It woked for me too. Had spent hours trying to figure this out but finally theses three lines solved my problem. Thank you so much for posting this.
With AWS ELB terminating SSL $_SERVER['HTTPS'] = 'on'; was enough for me
|
23

I had same problem nginx and had to do following in .htaccess

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

in wp-config.php

define('FORCE_SSL_ADMIN', true); define('RELOCATE', TRUE); $_SERVER['HTTPS'] = 'on'; define('WP_HOME', 'https://yourdomain.com'); define('WP_SITEURL', 'https://yourdomain.com');

don't use the below with nginx unless you make sure it passes HTTPS is on to fast cgi, otherwise it won't work, 

if ( isset( $_SERVER['HTTP_X_FORWARDED_PROTO'] ) && 'https' == $_SERVER['HTTP_X_FORWARDED_PROTO'] ) { $_SERVER['HTTPS'] = 'on'; }

it might be of benefit log debug level in error log of nginx, this is how you get to see the flow.

Improve this answer

7 Comments

Just saved our day! Is there any problem using RELOCATE?
Thanks. Only this line $_SERVER['HTTPS'] = 'on'; solves the problem for me
this one definitely fixed it
Thanks this fixed. I think WP_HOME shouldn't have www and ending '/'
Helped me! This is answer in most cases
|
8

Make sure that you define the WP_SITEURL and WP_HOME at wp-config.php

define('WP_HOME','https://yourdomain.com'); define('WP_SITEURL','https://yourdomain.com');

And add this condition to check if the https at wp-config.php

if ( isset( $_SERVER['HTTP_X_FORWARDED_PROTO'] ) && 'https' == $_SERVER['HTTP_X_FORWARDED_PROTO'] ) { $_SERVER['HTTPS'] = 'on'; }

This works well

Improve this answer

1 Comment

Nice, this way i can solve the problem without changes in .htaccess, thanks!
8

if use Cloudflare and Nginx:

1- go to the cloud flare and add always use HTTPS in page rules.

2- add the below code into the wp-config.php

define('WP_HOME','https://example.com/blog'); define('WP_SITEURL','https://example.com/blog'); if ( isset( $_SERVER['HTTP_X_FORWARDED_PROTO'] ) && 'https' == $_SERVER['HTTP_X_FORWARDED_PROTO'] ) { $_SERVER['HTTPS'] = 'on'; }

Note: don't change anything in the database and using incognito mode.

Improve this answer

1 Comment

Nice, this way i can solve the problem without changes in .htaccess, thanks!
7

Try changing your first three lines to:

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

I believe, that unless you attempted to go to https://en.example.com/:443 then {SERVER_PORT} will never return 443.

Improve this answer

7 Comments

Is there a publicly-accessible URL to view your site's behavior?
Oh there is still a problem: Currently I´m also able to open the URL with http only.
So, it isn't forwarding you to https?
sorry for the late response. Now it works! I think, it was a server cache issue.
What if I get the ERR_TOO_MANY_REDIRECTS error? How do I fix that?
|
3

Excerpt: Adding the following lines of code at the start of wp-config.php file resolved the redirect conflict.

if (strpos($_SERVER['HTTP_X_FORWARDED_PROTO'], 'https') !== false) $_SERVER['HTTPS']='on';
Improve this answer

Comments

0

Not directly the answer, but something else to note is that some browsers will cache redirects, so you might be changing your htaccess or wp-config without seeing any changes.

Best way to debug this is using incognito mode.

The above answers worked for me, but it took ages to work out that they had actually worked because of the browser redirect caching!

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.