psuttles
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Website inaccessible after 6.9 upgradeThis issue has been resolved.
The culprit was an F5 load balancer health check. I don’t have any details of what exactly was going on with the load balancer (we’re at a university and I was working on this issue with our campus NetOps), but whenever the update to WordPress was made from 6.8.3 to 6.9, the F5 load balancer health check failed and prevented access to the site. When I updated WordPress to 6.9 and let NetOps run a new health check, access to the site was restored via browser.
So, moral of the story:
For WordPress installations behind a load balancer…updating to 6.9 may cause failed health checks. Something to check out if you’re having this issue.Forum: Fixing WordPress
In reply to: Website inaccessible after 6.9 upgradeAdditionally, here’s the cURL output from the working WP version 6.8.3 when I request the same URL:
- Host www/mysite.com:443 was resolved.
- IPv6: (none)
- IPv4: xxx.xxx.xxx.xx
- Trying xxx.xxx.xxx.xx:443…
- schannel: disabled automatic use of client certificate
- ALPN: curl offers http/1.1
- ALPN: server did not agree on a protocol. Uses default.
- Established connection to http://www.mysite.com (xxx.xxx.xxx.xx port 443) from xxx.xxx.xxx.xx port 55294
- using HTTP/1.x
GET / HTTP/1.1
Host: http://www.mysite.com
User-Agent: curl/8.16.0
Accept: /- Request completely sent off
< HTTP/1.1 200 OK
< Date: Mon, 05 Jan 2026 19:32:33 GMT
So, in both instances (6.8.3 and 6.9), the SSL connection is established…but the GET / HTTP/1.1 Host request is being denied in WP 6.9 when attempting to connect to the site via browser, whereas is returns a HTTP/1.1 200 OK response when using 6.8.3.
Note: In the output above, none of the URLs are listed as using HTTP; they’re just listed as “www.mysite.com”. I think the support page here is treating them as URLs and adding the HTTP.
Forum: Fixing WordPress
In reply to: Website inaccessible after 6.9 upgradeThanks for the reply and the suggestion.
I’m assuming the options presented in the wp-admin/options.php page are the same as the wp_options table in the database? Either way, I checked both for any instance of the site or home URL using HTTP and everything I found was correctly using HTTPS.Also, this error message is being presented in browsers…even if I manually enter https://ww.mysite.com (“ERR_SSL_PROTOCOL_ERROR” in browsers or a generic “connection reset” when I attempt to access the site after upgrading to 6.9).
It seems to me like the SSL layer is 100 % correct — the certificate is good, the handshake finishes perfectly. Right after the handshake finishes and (in the cURL example) cURL starts sending the actual HTTP request, Apache (or something directly in front of it) actively kills the TCP connection with a RST packet.