Why does wp-admin login page failed after changing to https because of looping redirection and how to solve it?

-
After changing my Wordpress from http to https, the wp-admin login page failed because of too many redirections.

I finally solved this problem by adding the following line to wp-config.php:
$_SERVER['HTTPS'] = 'on';

评论

发表评论

此博客中的热门博文

Openwrt路由器上配置shadowsocks透明代理+gfwlist(PAC)

-
Shadowsocks 服务推荐： Just My Socks 推荐理由：价格便宜，支持月付，安全灵活。 本文配置的前提是已经有shadowsocks服务。你可以通过购买或者自行搭建的方式获得。以下是链接： 直接购买网上的服务，此处推荐 Just My Socks 快速Just My Socks配置Shadowsocks，请点 这里 。 自行搭建，请参考 KVM VPS上配置V2Ray(Shadowsocks mode) + 加速:普通BBR/魔改BBR(测试于Ubuntu 16.04) 本文所使用的环境，仅作参考： OpenWrt 18.06.1/LuCI openwrt-18.06 整体思路： DNS部分： if 访问地址在gfwlist中     DNS请求转发到127.0.0.1:5353的dns-forwarder的监听端口     dns-forwarder转发到8.8.8.8进行解析     8.8.8.8在gfwlist中，通过匹配iptables规则转发到1080端口     ss-redir监听1080端口，通过shadowsocks代理服务器转发请求 else     正常使用公共DNS或者ISP提供的DNS服务器 其他数据： if 访问地址在gfwlist中     通过匹配iptables规则转发到1080端口     ss-redir监听1080端口，通过shadowsocks代理服务器转发请求 else     正常访问 步骤1:依赖包安装（ 非常重要 ） 本文所有的操作都基于SSH和Web管理界面操作。 首先通过SSH添加GPG Key，这样之后添加的源才能通过签名验证： wget http://openwrt-dist.sourceforge.net/packages/openwrt-dist.pub -O /tmp/openwrt-dist.pub opkg-key add /tmp/openwrt-dist.pub 然后在OpenWRT Web管理界面，“系统”>“软件包”>“配置”中，“自定义feeds”最后添加两行源： src/gz openwrt_dist http://openwrt-
阅读全文

Configure shadowsocks transparent proxy + gfwlist(PAC) on OpenWRT Router

-
You must have Shadowsocks services which can be gained in the following way before actually starting to configure. Purchase Shadowsocks Service directly online. Recommendation:  Just My Socks Quick Shadowsocks configuration using Just My Socks, please click here . Build the service yourself. Please refer to  Configure V2Ray(Shadowsocks mode) + 加速:普通BBR/魔改BBR on KVM VPS (Tested on Ubuntu 16.04) . The environment this article used, FYI： OpenWrt 18.06.1/LuCI openwrt-18.06 The Overall Idea: DNS part: if the requested address is in gfwlist     forward DNS request to 127.0.0.1:5353 which is listened by dns-forwarder     dns-forwarder forwards the request to 8.8.8.8 for translating     8.8.8.8 is in gfwlist, so match iptables rules and is fowared to 1080     ss-redir listen on port 1080, foward request to shadowsocks server else     use public DNS servers or the DNS servers provided by the ISP other data: if the requested address is in gfwlist     match ipt
阅读全文

Using Haproxy + shadowsocks (ha + ss) to setup multi ss backend and load balance

-
*Install haproxy > sudo apt-get install haproxy *Configure haproxy >vim /etc/haproxy/haproxy.cfg global     ulimit-n 51200     log /dev/log local0     log /dev/log local1 notice     chroot /var/lib/haproxy     pidfile /var/run/haproxy.pid     user haproxy     group haproxy     daemon defaults     log global     mode tcp     option dontlognull     timeout connect 5000       timeout client 50000     timeout server 50000 frontend ss-in     mode tcp       bind $Your_IP:8002     default_backend shadowsocks backend shadowsocks     mode tcp       balance roundrobin         server ss1 $Your_SS_IP1:$Your_SS_PORT1 maxconn 20480         server ss2 $Your_SS_IP2:$Your_SS_PORT2 maxconn 20480 --The haproxy only allows the remote ss servers with the same password. As here haproxy is only providing the function like a load balancing switch. It's like a multi channel valve which does NOT provide any shadowsocks protocol level function
阅读全文