I’m running a WordPress 4.4.2-based membership site on Ubuntu 12.04 LTS
with
PHP 5.6.20.
After upgrading to 1.9.14 (compiling from source with no errors or
warnings), I could no longer log in to my site, using Firefox/Chrome/IE.
Trying to login didn’t timeout. Instead, fairly quickly, I would get an
error message like this in Firefox:
Secure Connection Failed
The connection to jobmob.co.il was interrupted while the page was
loading.
The page you are trying to view cannot be shown because the
authenticity
of the received data could not be verified.
Please contact the website owners to inform them of this problem.
Learn more…
Tailing the error logs, nothing at all appears when I try to log in.
My WordPress install is Multisite, which means I can have multiple
websites
running off a single install, and I do. However, only the main website
has
this login issue with 1.9.14. I could still log in without a problem in
each of the other sites.
How to troubleshoot this? 1.9.14 has relatively few changes, so I was
surprised by this. I’ve since rolled back to 1.9.13
On Wed, Apr 06, 2016 at 03:38:31PM -0400, jshare wrote:
My WordPress install is Multisite, which means I can have multiple websites
running off a single install, and I do. However, only the main website has
this login issue with 1.9.14. I could still log in without a problem in
each of the other sites.
How to troubleshoot this? 1.9.14 has relatively few changes, so I was
surprised by this. I’ve since rolled back to 1.9.13
There are various changes related to request body handling when
using HTTP/2 in 1.9.14. If you are using HTTP/2, consider
disabling it to see if it helps.
In either case debug log should help to further diagnose the
problem, see A debugging log.
My WordPress install is Multisite, which means I can have multiple websites
running off a single install, and I do. However, only the main website has
this login issue with 1.9.14. I could still log in without a problem in
each of the other sites.
How to troubleshoot this? 1.9.14 has relatively few changes, so I was
surprised by this. I’ve since rolled back to 1.9.13
Could you try without 3rd-party modules and patches?
I enabled the debug.log to compare the output with http/2 enabled and
disabled, but when I compare the two side by side, nothing jumps out at
me.
Aside from the time and a few numbers, the two log sections are
identical.
What should I be looking for?
For example, here’s the tailed log section that appears when I can’t
login
because http/2 is enabled:
On Sun, Apr 10, 2016 at 04:18:05AM -0400, jshare wrote:
If I disable http/2, I can login - good call!
I enabled the debug.log to compare the output with http/2 enabled and
disabled, but when I compare the two side by side, nothing jumps out at me.
Aside from the time and a few numbers, the two log sections are identical.
What should I be looking for?
For example, here’s the tailed log section that appears when I can’t login
because http/2 is enabled:
[…]
2016/04/10 10:53:23 [debug] 11339#0: *32 http process request line
2016/04/10 10:53:23 [debug] 11339#0: *32 http request line: “GET /readme.html
HTTP/1.1”
This log doesn’t looks like a request with HTTP/2 enabled.
Rather, it looks like a plain HTTP/1.1 redirect to SSL. You
probably have another server{} section to handle SSL, and this
section doesn’t have debugging log configured.