503 Service Temporarily Unavailable - on Chrome/Chromium restore

#1

Pages with protected content get a 503 on restarting Chromium based browsers.

  • This is not the 503 related to IP addressed or whatsover - just a plain

503 Service Temporarily Unavailable

Nginx

It also often happens on first call of a site. Refresh and page appears.

content of site:

503 Service Temporarily Unavailable

503 Service Temporarily Unavailable

nginx

— Note this only happens to pages that have s2member protected content. Could be because they are not cached? Maybe I have a general problem here? This appeared with recent chrome (based) browsers. Firefox is fine.

#2

Likely a failure with S2Member dealing with the IPv6 Protocol is probably behind this.
If you can monitor the user logins which log the users IP address that will give the best way to work out what the issue is.

#3

I’m not sure about this anymore - but yeah the IPV6 bug of s2member could have been the reason. I’m thinking of switching off IPV6 temporarily until s2member is fixed. But then I fear there are a few users already who have no IPv4 support anymore.