Using Feralhosting and I can no longer connect using rutorrent/rtorrent
-
Hi guys,
so i know that with the DDOS changes etc, that some errors with ip might have been popping up.
So having used feralhosting for many years, it seems that rutorrent will no longer connect to any of your trackers (existing ones that were seeding, and new ones i just added).I just get the following error: Tracker: [Peer certificate cannot be authenticated with given CA certificates]
So i checked in Deluge and Transmission (which i have installed on the same server, but never use as I prefer rutorrent), and both work perfectly without issue.
I got in touch with feral, and they have said i need to get in touch with you guys.
I have checked and other sources (both public and private trackers) are working in rutorrent, so its localised to the gaytorrent.ru torrents i am attempting to download.Any ideas what the issue could be? and how can we resolve it?
Thanks
-
I'm having exactly the same issue with rutorrent that just started today.
-
Around here with the same problem since this morning using seedbox
-
Just since around Noon today (May 30) Eastern Daylight Time, I am having an issue connecting to the Tracker. My current IP through my VPN is 64.62.244.51.
Is this IP now being blocked by the DDOS protection? It is one of the servers used by Netshade, which is a widely-used Macintosh VPN.
They have several servers but this particular one seems to normally work best for me. I have tried one of their others (with a similar IP, only the last node changed). But I am still having the same issue: Transmission 3.00 (f4489c982e) reports:
Announce error: Could not connect to tracker - Today at 6:48 PMI've used NetShade for several years now. And since I have already paid for a full year's subscription, it would be very inconvenient to switch VPN providers.
I'd appreciate any help or suggestions. Thanks!!
-
A little more information:
1. To see if the issue was IP-specific, I tried a NetShade server in the UK. No change in the issue. (And that's a completely different IP!)
2. Other torrent trackers are working fine and have no new issues; so I don't think it's a problem with the Transmission update.
3. .torrent files previously downloaded (before today) appear to be functioning okay. I see data being up- and down-loaded, even though Transmission reports it cannot connect to the Tracker. This applies to both seeding and leeching torrents.Any help is appreciated!!
-
I started receiving the "Peer certificate cannot be authenticated with given CA certificates" in ruTorrent on a Pulsed Media seedbox yesterday as well. Torrents from other sites are working fine through this seedbox server and I can download torrents directly from this site to my PC using uTorrent OK, so it seems to be a ruTorrent(possibly pulsedmedia.com)/GAYtorrent.ru related issue.
Anyone got any ideas on how to fix this?
-
It is not just Feral Hosting. I am not with them, but same problem. No connection (just on this tracker) for 36 hours or so, now.
Hopefully staff are looking into a work-around.
To be told that we just need to change VPN or IP is not so realistic, seedboxes don't usually use a VPN (a lot of VPNs have trouble dealing with that amount of traffic) - in short, the IP comes with the seedbox.
-
Just to add another one: NordVPN doesn't seem to work anymore as well. No issues with pretty much all other sites I'm using, so it's likely the new protection here that's disrupting service.
That's a pretty big VPN provider and asking everyone using them to just go elsewhere or change surely isn't the way to go with this?
-
SomeĀ additional updates:
1. Previously-downloaded .torrent files are no longer working. I believe they were only working before because the same members were in the swarm as when the last successful announce occurred. Simplified - the previous IPs are now gone and I can't connect to the Tracker to find out the new ones.
2. I have raised this issue with the site Helpdesk and also pointed them to this thread. I am hopeful that the Admins will provide some answers.
3. Can anyone tell me what VPNs are still working as of now? While I'm not thrilled with the idea, I might consider using a different VPN on another computer. Though I realize that is not an option for most people. (Didn't gt.ru have a VPN of their own at some point? I cannot seem to find anything about it now.)Any and all help isĀ appreciated!!
-
We are trying to gather info so we can find the problem.Ā Ā We need people to provide as much info as possible to track down the issue.
It was one of the other sites that had their own VPN.
-
Two things to noteā¦. For users who are having issues with the CA Certificate for our SSL tracker, you can manually change the beginning of the announce URL in your torrent client. Change the beginning from:
https://tracker.gaytorrent.ru/
to
http://tracker.gaytorrent.tw:2710/
If you want to make this change permanent on all torrents moving forward, click the "Profile" tab at the top of the page, then disable the SSL tracker, and save the changes at the bottom of the page.
For users who are using NordVPN, it has come to my attention that it will only work consistently if you enable the Custom DNS setting and use the servers 8.8.8.8 and 8.8.4.4These solutions should get you around most issues. If you are not using a VPN and the tracker change does not work, you may need to use a VPN to bypass the issue routing through to our tracker. I use PrivateVPN, as do a number of other staff, and it works GREAT with our system.
-
Two things to noteā¦. For users who are having issues with the CA Certificate for our SSL tracker, you can manually change the beginning of the announce URL in your torrent client. Change the beginning from:
https://tracker.gaytorrent.ru/
to
http://tracker.gaytorrent.tw:2710/
If you want to make this change permanent on all torrents moving forward, click the "Profile" tab at the top of the page, then disable the SSL tracker, and save the changes at the bottom of the page.
For users who are using NordVPN, it has come to my attention that it will only work consistently if you enable the Custom DNS setting and use the servers 8.8.8.8 and 8.8.4.4These solutions should get you around most issues. If you are not using a VPN and the tracker change does not work, you may need to use a VPN to bypass the issue routing through to our tracker. I use PrivateVPN, as do a number of other staff, and it works GREAT with our system.
Thanks for the possible workaround MrMazda, however personally I don't like the idea of switching to a non-secure (http) link - that may be my paranoia kicking in, but I try and keep as secure, safe and anonymous as possible when I'm online!
-
Two things to noteā¦. For users who are having issues with the CA Certificate ... <snip>For users who are using NordVPN, it has come to my attention that it will only work consistently if you enable the Custom DNS setting and use the servers 8.8.8.8 and 8.8.4.4
These solutions should get you around most issues. If you are not using a VPN and the tracker change does not work, you may need to use a VPN to bypass the issue routing through to our tracker. I use PrivateVPN, as do a number of other staff, and it works GREAT with our system.</snip>
Thanks MrMazda, I appreciate your help!
While I use NetShade, and not NordVPN, I will try those specific DNS values to see if they help.
Since Transmission hasn't specifically given any errors about the CA Certificate and I agree with @pjh1122 about staying as secure as possible, I'll try that first. I will inform of my results up here.
-
It should also be noted that users who are using Transmission 3.0 have experienced no end of trouble trying to reach the tracker, and rolling back to version 2.94 seems to resolve the issue.
-
I posted this in my support discussion about this, but thought it would be good to share here as well.
After doing some digging, I managed to come across this discussion about the same error being seen in rtorrent/rutorrent.
https://github.com/binhex/arch-rtorrentvpn/issues/10The one post in it refers to this post: https://bbs.archlinux.org/viewtopic.php?pid=981832#p981832
which talks to changing a setting in rtorrent: network.http.ssl_verify_peer.set=0While this still has some potential security concerns, it would appear that this is the only fix that I could find for this issue on the web.
This is of course simpler than going through hundreds of seeding torrents on your server to change to the non ssl tracker url, it doesn't seem to represent a less secure option than that one is.I have tested this and it does seem to be working. Not sure this is a long term solution to this issue, but wanted to share.
-
UPDATE: Apparently, there was an underlying issue with the SSL certificate for which we were not aware, which has been fixed. This should mean that Transmission 3.0 among a number of other clients should now work again.
-
Can confirm it's all now working my end - thanks Mr MazdaĀ :cheers:
-
Very good. I hope you can hear my loud purringā¦Ā :love:
