@lyse@lyse.isobeef.org Ahh so it’s not just me! 😅

@prologic@twtxt.net @lyse@lyse.isobeef.org I checked my logs and all I see are 304 responses and a couple of delayed requests here and there due to rate limiting, but not that many. I’ll disable it (the rate limiting) for a couple of days, let me know if you still get the ‘forbidden access’ thing 🫣 I may have effed up my configuration trying to deal with some weird stuff.

@aelaraji@aelaraji.com is there anything else in front of your server or is it just direct? 🤔

@prologic@twtxt.net I’m using CF Tunnel on a raspberry pi, can’t do direct at the moment.

@aelaraji@aelaraji.com Luckily, my scrollback buffer was large enough. It actually returned HTTP 530. Yes, this is not a typo, five hundred and thirty, not 503 Service Unavailable. Might be a Clownflare thing: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#Unofficial_codes

@aelaraji@aelaraji.com Ahh it might very well be a Clownflare thing as @lyse@lyse.isobeef.org eluded to 🤣 One of these days I’m going to get off Clownflare myself, when I do I’ll share it with you. My idea is to basically have a cheap VPS like @eldersnake@we.loveprivacy.club has and use Wireguard to tunnel out. The VPS becomes the Reverse Proxy that faces the internet. My home network then has in inbound whatsoever.