Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2024 Poal.co

1.0K
• (edited ) (+3/-0)
Answered New Host > Major problems on Tor

I have used Tor throughout my time on poal - now it's almost impossible to even visit the site.

I asked you earlier (@AOU) about some issues on previous host with regards to login problems, which were seldom and could be fixed by connecting to a new node.

-Not anymore.

It took me 23 days to figure out poal.co was already online all this time...

And after my first login today, posting once, then browsing and realizing problems were about (site "unavailable" > only on Tor: works fine on other IPs), it took me 30 re-connects through other nodes to even write this post.

So @AOU: this post may be my last: I can't even get into the site anymore, and if that means me choosing not to use Tor, that means goodbye poal. (Not that I've contributed anything that carry that much weight, but still, I won't relieve myself of the yardsticks at my disposal just yet.)

Edit:

After walkthrough by @AOU:

There's an algorithm in place that blocks IPs that fuck up poal. Most IPs are Tor nodes these days, which makes poal near inaccessible through Tor for regular users.

Problem ["solved"]:

-Problems will linger for Tor users for the duration of the attacks.

I have used Tor throughout my time on poal - now it's almost impossible to even visit the site. I asked you earlier (@AOU) about some issues on previous host with regards to login problems, which were seldom and could be fixed by connecting to a new node. -Not anymore. It took me 23 days to figure out poal.co was already online all this time... And after my first login today, posting once, then browsing and realizing problems were about (site "unavailable" > only on Tor: works fine on other IPs), it took me 30 re-connects through other nodes to even write this post. So @AOU: this post may be my last: I can't even get into the site anymore, and if that means me choosing not to use Tor, that means goodbye poal. (Not that I've contributed anything that carry that much weight, but still, I won't relieve myself of the yardsticks at my disposal just yet.) *** Edit: After walkthrough by @AOU: There's an algorithm in place that blocks IPs that fuck up poal. Most IPs are Tor nodes these days, which makes poal near inaccessible through Tor for regular users. * https://poal.co/s/Announcements/501763 Problem ["solved"]: -Problems will linger for Tor users for the duration of the attacks.

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (34).
[–] • 0 pt

Agreed, but it (Tor) is what is affected. (From my POV).

And that it works: Yes: it just happens to block Tor users (atm.). Hence my frustration.

Accidental floods: Extremely unlikely. (and not my point(-er)).

But if you're having problems on your end, it does come through Tor it would seem.

If this is what "they" use these days, there's little to (do about) it - and thus: little to do but stave out the storm.

Lest they sit there manually pressing buttons like an idiot... (like I do), which is unlikely.

Aka: smells like DDOS fuck-twat something or other.

End Note:

I'll be checking in from time to time, but on the grander picture of things, it's just a wittle wolf blowing at the hut yet again - and should calm down after a while.

But fuck me: it really took me 23 days from the site coming back online to I realized it was actually back online.

Only today, I bothered to log in.

I checked the site almost every day, but never came through, thus thinking poal was still down due to transition.

Fuckin' Tor, eh?

[–] • 0 pt

But fuck me: it really took me 23 days from the site coming back online to I realized it was actually back online.

Only today, I bothered to log in.

I checked the site almost every day, but never came through, thus thinking poal was still down due to transition.

Fuckin' Tor, eh?

The protection existed before I migrated from the previous host and installed it back on the new host only a few days later. So it probably was related to the DNS taking longer to propagate over specific networks/nodes.

[–] • 0 pt

I remember. But, it's never been this bad before. Because now it's really not good.

Don't quite know when the site went back up, but we're probably into a month straight of fuckery.

Which means your filters for one: works great.

Surprised at the number of affected nodes though. It's either relentless ("A.I.") or long time-outs on your end.

Don't "quote" me on that - I get where you're at: do what it takes.

Maybe put up a bulletin/sticky? (Perhaps you've done so already: I've been living under a rock lately)

[–] • 0 pt

I already posted about it 10 days ago. It’s the current right sidebar sticky

https://poal.co/s/Announcements/501763