Feedback Technical Grievances

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
Nool,

Since yesterday I've been unable to access the site using Firefox based browsers. Waterfox and TOR Browser (also Firefox based) are both giving a similar, generic "timeout" or "unable to connect" style messages. This is on both TOR and standard domains. Brave works fine for both types of domains. I've tried it on multiple computers with the same results, including multiple different VPN services. I honestly can't tell if it's on my end or what. I thought it was DDOS related at first, but the behavior is consistent depending on the browser.
 
i frequently get these errors

when trying to connect to the .onion:
error2.png

when trying to connect to the .net:
error.png

sometimes i can log in just fine and the errors start later (when trying to open a thread for example)
other times i can't connect to the site at all

spam restarting tor browser or switching tor circuits fixes it eventually, but sometimes it takes a lot of restarts until i get a working connection, and even then it usually doesn't last long until it goes back to errors
 
  • Agree
  • Like
Reactions: Manat, Stolos, std::string and 1 other person
Pee Cola said:
Maybe it's just me, but over the last 3 days (including today) the Farms has become unreachable at the same time every day (around 22:00 UTC; convert it to your local time yourselves). Sometimes it's just for a few minutes like today; though the last couple of days were more like 30-60 minute interruptions.

If I didn't know any better, I'd say that the troons are running their DDoS attacks to a schedule rather than just willy-nilly. Maybe they're running out of steam (for now)?

tbh I wouldn't be surprised if the 22:00 UTC attacks stop as of tomorrow; at least one of them would be reading this thread. Will be interesting to see what time they reschedule their regularly scheduled daily DDoS to
Click to expand...
They've started early today (21:45 UTC). Whether it's because of impatience or because one of them saw this post, who knows.

Either way, I'll probably go touch grass for an hour until they run out of coins to put in the DDoS meter for today.
 
  • Agree
  • Like
Reactions: Manat and notafederalagent
Null said:
DNS related, pretty sure. You're getting different results only because of DNS caching. Try CTRL+F5.
Click to expand...
I tried this and messed around with a bunch of other DNS related stuff with no success, but today it seems to have fixed itself for no apparent reason.

So... yeah. That's fine then.
 
  • Like
Reactions: Manat
Lord of the Large Pants said:
I tried this and messed around with a bunch of other DNS related stuff with no success, but today it seems to have fixed itself for no apparent reason.

So... yeah. That's fine then.
Click to expand...
Possibly the cache expired. I had something like this where it didn't work the first time, but eventually whatever was breaking it was fixed and the next time it did work. So just because it didn't work the first time doesn't mean it won't eventually. Always do that (just in general not just here) for persistent problems like that. Otherwise they'll persist even if the actual original problem has gone away.
 
  • Like
Reactions: Manat
AnOminous said:
Possibly the cache expired. I had something like this where it didn't work the first time, but eventually whatever was breaking it was fixed and the next time it did work. So just because it didn't work the first time doesn't mean it won't eventually. Always do that (just in general not just here) for persistent problems like that. Otherwise they'll persist even if the actual original problem has gone away.
Click to expand...
Man, I don't know. I tried EVERYTHING. Clear the OS DNS cache, cleared the browser DNS cache, did a Ctrl-Shift-Del and cleared everything, tried a different browser, tried a fresh browser on a completely different computer, tried both Cloudflare and Quad9 DNS... honestly no idea.

It doesn't sound like anybody else was having problems, so I assume it must have been a client side issue SOMEHOW, but it sure didn't act like one.
 
Last edited:
  • Feels
Reactions: AnOminous
Lord of the Large Pants said:
Man, I don't know. I tried EVERYTHING. Clear the OS DNS cache, cleared the browser DNS cache, did a Ctrl-Shift-Del and cleared everything, tried a different browser, tried a fresh browser on a completely different computer, tried both Cloudflare and Quad9 DNS... honestly no idea.
Click to expand...
Not sure if my issue was a similar issue. I had an issue today where one computer firefox would load and another it wouldn't. The issue was it was for some reason not sending me through the bot check, rebooting and opening up a thread that wasn't the front page finally got it to bot check and let me in.
 
You must log in or register to reply here.
Back