“Server Error” at [phone]T16:18:05+00:00.

[RokeJulianLockhart]

“Server Error” at [phone]T16:18:05+00:00.

[mouse-reeve]

I'm so sorry about this! I believe the problem is that the redis cache manager on b.s is periodically crashing and restarting, causing it to lose sessions (which is why you are logged out), and then taking a while to reboot, which causes the server errors you're seeing. This is improved by #3245, but we're still working on addressing the reliability issues

[kevin-guertin]

This has been a problem for a while, now. Yesterday, it didn't work at all. Server Error all day and extremely slow to tell you so. It worked briefly today but it was excruciatingly slow. Eventually, it logged me out once again. Trying to login again just gave me the Server Error page. For at least a month or so, I am constantly getting logged out and have to re-login and do 2FA at least once a day, but usually multiple times a day. It is frustrating.

[Hugo-Heagren]

I expect you're only able to connect to http://ip4.me/, like me?

Came here to report this same bug, and can confirm that this describes my situation: I am only able to connect to ip4.me. I'm in the UK and I'm on TalkTalk.

[mouse-reeve]

The pages that still load are ones that aren't reliant on the redis cache; redis is still taking a long time to reboot, which is causing the weirdly long downtime.

[RokeJulianLockhart]

#3271 (comment)

@mouse-reeve, error has appeared again, on the main page.

[gary-host-laptop]

#3271 (comment)

@mouse-reeve, error has appeared again, on the main page.

Same for me yesterday, it works today, and I have a friend from the US who told me he's having the same issue.

[RokeJulianLockhart]

#3271 (comment)

@gary-host-laptop, that's exactly why I asked, actually. However, I should have asked you to instead try to connect to https://ip6only.me/ and http://ip4.me/. That's because I expect the commonality between us is that our ISPs don't provide IPv6 support (although considering it still doesn't work through ProtonVPN or 5G, I'm not confident). I expect you're only able to connect to http://ip4.me/, like me?

[gary-host-laptop]

#3271 (comment)

@gary-host-laptop, that's exactly why I asked, actually. However, I should have asked you to instead try to connect to https://ip6only.me/ and http://ip4.me/. That's because I expect the commonality between us is that our ISPs don't provide IPv6 support (although considering it still doesn't work through ProtonVPN or 5G, I'm not confident). I expect you're only able to connect to http://ip4.me/, like me?

Indeed, I have IPv4 and am behind a double NAT because my ISP uses that to spend even less IP addresses.

I'm so sorry about this! I believe the problem is that the redis cache manager on b.s is periodically crashing and restarting, causing it to lose sessions (which is why you are logged out), and then taking a while to reboot, which causes the server errors you're seeing. This is improved by #3245, but we're still working on addressing the reliability issues

So we won't be able to use the web site until that is resolved? I just want to confirm that I'm understanding correctly.

[mouse-reeve]

Oh I'm sorry, I skimmed this thread and didn't realize that you're seeing continued downtime -- the site has been going down for short periods of time, but should be up currently (it is for me) and only down very infrequently and (now that that fix is live) very briefly. It should be largely usable, so you are experiencing a different issue than what I thought

[gary-host-laptop]

I'm getting this error too and it logs me out pretty constantly which is very annoying.

[RokeJulianLockhart]

#3271 (comment)

@gary-host-laptop, can you provide an approximate location and your ISP?

[gary-host-laptop]

#3271 (comment)

@gary-host-laptop, can you provide an approximate location and your ISP?

I'm from the third world, my ISP is some sh***y no name provider. Anyway, I just checked again, and I was having issues getting logged out constantly before this bug, but right not I can't even log in, it just repeats this error ad nausea.

[RokeJulianLockhart]

#3271 (comment)

It's working for me again, @mouse-reeve.

[kdmcguire]

I've also been seeing fairly regular and long periods of downtime (server errors, not unreachable), and it seems to log me out every time too.

Down for me right now, 18:34 GMT (UTC+0)

[gedankenstuecke]

I also keep getting the same error as reported by @RokeJulianLockhart & @gary-host-laptop over the last 1-2 days, today I encountered this most of the day whenever I tried!🤞

[MattWilcox]

Just chiming in that I'm seeing this issue right now, from my laptop at home. UK based. I'm not logged in.

Also, the About page is timing out. Other pages appear to load, so I assume those are hitting a server cache and About isn't.

[gedankenstuecke]

Thanks for the update @mouse-reeve! Currently it seems to work okay, and all the best in resolving the redis issues!