Posts made by spiffyweasel 0

@MrMazda Thanks for the thorough job!

Would it be possible to take action against this trolling uploader? They don't seem to have stopped. Within the last month, they have created 20+ new torrents with the obscure "big white boy" moniker.

@MrMazda This hasn't been my experience. I just forced the use of IPv4 with my VPN and yet the client is having trouble getting the tracker to respond to its requests in a timely manner. Perhaps the number of torrents you are using on your IPv4-only setup is too low for the issues to manifest. For reference, the tracker seems to work fine for my setup for roughly the first 50-100 torrent announce requests and then starts timing out for subsequent requests.

@DirtyNick same here, nothing has been resolved yet. Since you reset your passkey, you'll need to redownload every torrent to start seeding again.

It is good that the issue has been acknowledged finally.

Besides the immediate fix, it would be very useful if the admins could come up with one or more steps to more conclusively determine that the server/tracker is at fault in the future. Anything that avoids the unnecessary tug-of-war that transpired over the last 2 weeks as we tried to convince folks that there is a problem with the tracker and not with individual user clients.

Regrettably, some users ended up resetting their passkeys in the false hopes of a quick fix - another thing that could have been avoided by a quicker acknowledgement of the issue than the 10 days it took here.

@MrMazda Have server-side changes been looked at so far (the entire stack from the DDoS protection to the actual tracker service)? To my mind, there has been sufficient evidence to indicate that none of the affected users have changed anything in their client.

I'm down to seeding barely 100 torrents down from approximately 16,000, and I'm seeing a steady uptick in the number of reseed requests since the start of the outage. If a fix is not found soon, I plan to stop seeding entirely for the time being.

@Gayfox996 For posterity: https://www.reddit.com/r/SuddenlyGay/comments/164tdhx/fit_check/

@spiffyweasel-0 Also, nothing has changed in my client+VPN setup for the last ~3 months so it's unlikely to be an issue we (the users) can fix.

@MrMazda I'm on qBitTorrent 4.6.3 and experiencing the issues.

@Douseikekkon More recent reports of connection issues: https://community.gaytorrent.ru/topic/64831/most-of-my-files-are-red/

@raphjd Agreed, but it seems like it was part of a longer recording. Can't tell for sure though.

@MrMazda Sorry, fixed link now, should be good for 90 days.

@vashkevron From what I can tell, it appears to be overeager DoS protection. For instance, if I switch between different VPN servers, things suddenly start working again for the first few minutes before dying back down.

@spiffyweasel-0 Previous reports of similar issues (in the last 3-4 days): https://community.gaytorrent.ru/topic/64819/a-connection-attempt-failed-in-download

@turlough I've been experiencing similar issues since the last 3-4 days. I'm using qBittorrent via VPN so it's unlikely that your setup is at fault. It's more likely that there has been a configuration change in the DoS protection for the tracker preventing so many of us from connecting. It's hard to imagine an actual DoS attack lasting so long (although I don't know this for sure).

https://streamable.com/3te4zr

Alternatively, does anyone recognize the people in the snippet?

@zullu Yes, the tracker seems to be non-responsive for me too.

If an admin is seeing this message, it may be worthwhile putting up a banner message on the site to prevent a torrent (pun unintended) of similar support requests until the SSL issue is fixed.

Is there any particular person on the team who I can contact about volunteering opportunities to improve the site? I'm a software developer with some web dev experience.