Feedback Technical Grievances

hey retard, that's been an issue for maybe 8 years now. It was an issue with Cloudflare.

The system is set to cache images. XenForo will render an error page for missing images. This error page gets cached. This shows an avatar. You are not granted access to the account.
Oh. phew i thought i accidently bugged something.
 
hey retard, that's been an issue for maybe 8 years now. It was an issue with Cloudflare.

The system is set to cache images. XenForo will render an error page for missing images. This error page gets cached. This shows an avatar. You are not granted access to the account.
Feel free to call me retarded if this suggestion is stupid, but would it be possible to just add a line of CSS to the error page to hide the user avatar so people will stop thinking they somehow got access to someone else's account?
 
Something happened to the thing that blocked the reply button on the Community Happenings thread. I noticed it because I accidentally replied to something there, noticed what thread it was, and deleted it.

That was pretty helpful in avoiding accidental rulebreaking.
 
  • Like
Reactions: XYZpdq Jr.
Site has suddenly started loading extremely slowly and pfps are barely working now (on this page, only AnOminous' is showing up- to give an idea of the ratio)
Dunno why lol
Have already tried closing and reopening all tabs
Still on Ungoogled Chromium, no VPN, clearnet
 
Only able to connect using either Tor or a VPN through Germany.

Trying to connect through standard clearnet spins for a while then returns a straight up "This site can't be found" where as VPN/Tor loads almost instantly.
 
Been having a great deal of trouble connecting for a couple hours unless I'm on a Netherlands VPN, and even then I had to cycle through a few different Netherlands IP addresses to get it to work.
 
1683230809026.png

Seems another attack is going on. access through tor seems ok but I'm having difficulty over clearnet
 
@Null I'm sure more competent people have already reached out to you, but Timeout during SSL handshake just means that the communication between the server & the load balancer timed out. At least I'm assuming that your connections between the LB/Haproxy and the content servers are SSL encrypted. Generally the timeout is sixty seconds or thereabouts, so assume that whatever the attack is doing it's slowing down the responses enough that the response from the content servers is >$howevermanyseconds. SSL is just the first thing to croak, so you're seeing it in the logs.
 
@Null I'm sure more competent people have already reached out to you, but Timeout during SSL handshake just means that the communication between the server & the load balancer timed out. At least I'm assuming that your connections between the LB/Haproxy and the content servers are SSL encrypted. Generally the timeout is sixty seconds or thereabouts, so assume that whatever the attack is doing it's slowing down the responses enough that the response from the content servers is >$howevermanyseconds. SSL is just the first thing to croak, so you're seeing it in the logs.
SSL is terminated by haproxy, so it's a 60 second load issue affecting haproxy itself.
 
SSL is terminated by haproxy, so it's a 60 second load issue affecting haproxy itself.
In that case yeah, that's a known thing with Haproxy. When it starts to get overloaded, it will also error out like so. Since I'm assuming your haproxy is pretty well tuned, so it's just load.
 
Back up again in the Mountain West. Either Josh got KiwiFlare to mitigate the DDOS or someone ran out of tranny sheckles.
 
Back