WordPress wp-admin https重定向循环

您已经添加了$_SERVER['HTTPS'] = 'on';到您的wp-config.php ?

您还应该使用 WP迁移数据库插件从http://yoursite.com到https://yoursite.com

You've added $_SERVER['HTTPS'] = 'on'; to your wp-config.php?

You should also use the WP Migrate DB plugin to migrate from http://yoursite.com to https://yoursite.com

我遇到了类似的问题,只是将以下代码段添加到了我的wp-config.php中:

 /** SSL */  
define('FORCE_SSL_ADMIN', true);  
// in some setups HTTP_X_FORWARDED_PROTO might contain  
// a comma-separated list e.g. http,https  
// so check for https existence  
if (strpos($_SERVER['HTTP_X_FORWARDED_PROTO'], 'https') !== false)  
    $_SERVER['HTTPS']='on';
 

根据中的建议.仅在您的负载平衡器(或防火墙)设置中启用了SSL直通的情况下才需要这样做.这意味着尽管您可以在TLS/SSL中通过HTTP访问该站点,但是服务器接收的通信仅是HTTP.为了解决这个问题,需要上面的标头,以便WordPress可以将HTTPS设置为on配置数组中的$_SERVER.

I had a similar problem and just added the following snippet to my wp-config.php:

/** SSL */  
define('FORCE_SSL_ADMIN', true);  
// in some setups HTTP_X_FORWARDED_PROTO might contain  
// a comma-separated list e.g. http,https  
// so check for https existence  
if (strpos($_SERVER['HTTP_X_FORWARDED_PROTO'], 'https') !== false)  
    $_SERVER['HTTPS']='on';

as suggested in the Codex. This will only be needed in case there's SSL passthrough enabled in your load balancer (or firewall) setup. Meaning that while you can access the site via HTTP within TLS/SSL, the communication that your server receives is HTTP only. To account for that, above header is needed so WordPress can "set" HTTPS to on in the $_SERVER config array.

由于我还没有发表评论的权限,因此我将发布此附加内容作为另一个答案:

Elias提出的将以下内容添加到wp-config.php的解决方案对我有用:

 /** SSL */  
define('FORCE_SSL_ADMIN', true);  
// in some setups HTTP_X_FORWARDED_PROTO might contain  
// a comma-separated list e.g. http,https  
// so check for https existence  
if (strpos($_SERVER['HTTP_X_FORWARDED_PROTO'], 'https') !== false)  
    $_SERVER['HTTPS']='on';
 

但是,只有当我将该文件中的先于其他内容使用时,它才对我有用！

As I do not have the comment privilege yet, I will post this addition as another answer:

The solution proposed by Elias, to add the following to wp-config.php, did the trick for me:

/** SSL */  
define('FORCE_SSL_ADMIN', true);  
// in some setups HTTP_X_FORWARDED_PROTO might contain  
// a comma-separated list e.g. http,https  
// so check for https existence  
if (strpos($_SERVER['HTTP_X_FORWARDED_PROTO'], 'https') !== false)  
    $_SERVER['HTTPS']='on';

However, it only worked for me when I put it before everything else in this file!

这本书的另一个版本,只需将其添加到wp-config.php顶部

原因是可能存在负载平衡器或某些未传递正确的https值的东西,因此您必须从其他地方获取它并将其伪造为wordpress.

 if ( (isset($_SERVER['HTTP_X_FORWARDED_PORT'] ) && ( '443' == $_SERVER['HTTP_X_FORWARDED_PORT'] ))
    || (isset($_SERVER['HTTP_CF_VISITOR']) && $_SERVER['HTTP_CF_VISITOR'] == '{"scheme":"https"}')) {
    $_SERVER['HTTPS'] = 'on';
}
 

Another version for the books, just add this to the top of wp-config.php

Reason is that there could be load balancers or something that does not pass along the proper https value, so you have to grab it from elsewhere and fake it for wordpress.

if ( (isset($_SERVER['HTTP_X_FORWARDED_PORT'] ) && ( '443' == $_SERVER['HTTP_X_FORWARDED_PORT'] ))
    || (isset($_SERVER['HTTP_CF_VISITOR']) && $_SERVER['HTTP_CF_VISITOR'] == '{"scheme":"https"}')) {
    $_SERVER['HTTPS'] = 'on';
}

实际上...我遇到了这个问题,解决起来非常容易且令人尴尬.不知何故,在webhost上我的wp-admin文件夹被删除,因此没有wp-admin出现此相同的错误消息.

经过数小时的测试,我看到了许多不同的方式,然后再次下载并上传后,一切正常.

检查一下,就这么简单.

Actually... I had this issue and the solving was quite easy and embarassing. Somehow on the webhost my wp-admin folder was deleted and therefore no wp-admin with this same error message.

After hours of testing so many different ways I just saw this and when downloaded and uploaded again it all worked as normal.

Check it guys, it can be that simple.

5岁的问题...

好的,安装了SSL证书并使用找到的http链接更改为https后,出现了此错误. " https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar" rel="nofollownoreferrer">此处.

我尝试了各种配置,除非我进行了以下设置,否则似乎都无法解决此问题:

 define('FORCE_SSL_ADMIN', true); 
define('FORCE_SSL_LOGIN', true);
 

对此:

 define('FORCE_SSL_ADMIN', false);
define('FORCE_SSL_LOGIN', false);
 

它允许我访问登录页面,但随后无法实际登录.我尝试回答了两个,但不幸的是,它还是没有帮助,直到我做了以下更改:

 /** SSL */   
define('FORCE_SSL_ADMIN', true);
// in some setups HTTP_X_FORWARDED_PROTO might contain
// a comma-separated list e.g. http,https   
// so check for https existence   
if (strpos($_SERVER['HTTP_X_FORWARDED_PROTO'], 'https') !== true)  
     $_SERVER['HTTPS']='on';
 

由于某种原因,我不知道为什么-我不得不更改

！== 错误

到

！== 是

我将nginx作为主机运行,并反向代理到nginx单元... 如果有人知道为什么这样做,请告诉我

5 year old Question...

Okay, I had this error, after installing my SSL Certificate and changing all links that were http to https using the wp-cli.phar found here.

I tried various configurations and none seemed to resolve this, unless I set this:

define('FORCE_SSL_ADMIN', true); 
define('FORCE_SSL_LOGIN', true);

to this:

define('FORCE_SSL_ADMIN', false);
define('FORCE_SSL_LOGIN', false);

It allowed me to hit the log-in page, but then was unable to actually log-in. I tried answer two but that unfortunately didn't help either, Untill I did the following change:

/** SSL */   
define('FORCE_SSL_ADMIN', true);
// in some setups HTTP_X_FORWARDED_PROTO might contain
// a comma-separated list e.g. http,https   
// so check for https existence   
if (strpos($_SERVER['HTTP_X_FORWARDED_PROTO'], 'https') !== true)  
     $_SERVER['HTTPS']='on';

For some reason, I do not know why - I had to change the

!== false

to

!== true

I'm running nginx as host and reverse proxy to nginx unit... If anyone has any idea why that worked, Please let me know

将网站托管在Azure webapp服务Linux上时,我遇到了同样的问题.

尝试使用此插件.激活时请多加注意. https://wordpress.org/plugins/jsm-force-ssl/

此插件使用本地WordPress过滤器,而不是PHP的输出 缓冲区,以实现最大的可靠性,性能和缓存兼容性 (此插件不会影响缓存性能),以及301 永久重定向以获得最佳SEO(301重定向被认为是最佳 从HTTP转换为HTTPS时,用于SEO).

大型主机的荣誉代理/负载平衡变量 环境:

HTTP_X_FORWARDED_PROTO HTTP_X_FORWARDED_SSL要求:

您的Web服务器必须配置有SSL证书,并且能够 处理HTTPS请求.

只需激活插件即可完成

没有插件设置可调整,也没有更改 您的WordPress配置-只需激活或停用 用于启用/禁用过滤器和动态重定向的插件.

I had the same issue when I hosted my site on Azure webapp service Linux.

Try this plugin. take care when it active it works. https://wordpress.org/plugins/jsm-force-ssl/

This plugin uses native WordPress filters, instead of PHP’s output buffer, for maximum reliability, performance and caching compatibility (this plugin does not affect caching performance), along with 301 permanent redirects for best SEO (301 redirects are considered best for SEO when moving from HTTP to HTTPS).

Honors proxy / load-balancing variables for large hosting environments:

HTTP_X_FORWARDED_PROTO HTTP_X_FORWARDED_SSL Requirements:

Your web server must be configured with an SSL certificate and able to handle HTTPS request.

Simply activate the plugin and you’re done:

There are no plugin settings to adjust, and no changes are made to your WordPress configuration — simply activate or deactivate the plugin to enable / disable the filters and dynamic redirects.