So i’m experiencing a sudden network issue with only Beehaw despite no major changes to my PC or network.
So I can go to beehaw.org, navigate to anywhere on it, but after 1 minute, the connection becomes unresponsive (connection was reset). This error will persist for about 2 hours or until I change my IP address. At that point, I can hit beehaw.org again, unfettered, but only for about 1 minute before the unresponsiveness kicks back in.
Am running windows 7 and brave browser under proton VPN, but it occurs with or without the VPN running. It only seems to occur with beehaw. I’ve not noticed any other site having navigational problems. I flushed the dns and rebooted both the PC (full shut down) and the wifi, but the error still occurs every time. The connection will be reset after 1 minute on a fresh IP.
Anyone smelt this fish before? Started about a month ago.
Hi,
About a month ago we implemented some mitigation related to unrelenting DDoS and scanning attempts. Might be that our security stack is seeing your connections as part of this, regardless of IP/VPN/TOR. I’d need more information from you to determine that, and try to get a fix in for your connections that don’t hinder our availability or security. Can you DM me here, or on Matrix
@penguincoder:hive.beehaw.orgso we can discuss a few pertinent details?Been connected for at least a half of an hour now, closer to an hour. Things seem normal. I’m good with it. Thanks again.
I’m glad! Thank you for following up.
Mullvad browser returns this
Secure Connection Failed
An error occurred during a connection to beehaw.org. PR_CONNECT_RESET_ERROR
Error code: PR_CONNECT_RESET_ERROR
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem.I’ll ping @Penguincoder@beehaw.org to help you with this.
Hey thanks for that. He was able to get me some traction.
You’re welcome and I hope everything got sorted
but apparently TOR browser runs A-ok.
Update: The TOR browser inevitably slid into the same issue. It took a bit longer to manifest. I got at least five minutes.
