Torrents are not connecting on Rtorrent/Rutorrent
-
Hi guys,
so i know that with the DDOS changes etc, that some errors with ip might pop 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? Cheesy
Thanks
(PS: I did post this in the general discussion section, and then realised there was a support section a lot further down the page, but wasn't able to move it here myself. I see there are a few other guys who have had the same issue with rutorrent as well)
-
I'm having the exact same issue/error on my server, which is running rtorrent 0.9.6.
From my home connection everything is working though. At least one difference is that I'm using rtorrent 0.9.8 on the home box.So it seems like it's an issue on my server setup somehow but still feels unexpected.
I've tried to run update-ca-certificates but it didn't help.Any help appreciated
-
I checked and i'm running rtorrent 0.9.8, and still having this issue, so not sure its related to the version. Hope someone gets back to us about this soon.
-
This error message means that your torrent client is choking on the SSL certificate. In order to get around this, you need to disable the SSL tracker in your profile. You may also need to change the announce URL in your torrent client. Specifically, change the beginning from
https://tracker.gaytorrent.ru/
to
-
You may also need to change the announce URL in your torrent client. Specifically, change the beginning from
https://tracker.gaytorrent.ru/
to
http://tracker.gaytorrent.tw:2710/
Posted on: Yesterday at 01:10:55 amPosted by: halcyonboyHave followed those instructions, and this has produced a different error Tracker: [Could not parse bencoded data: ]
Any more steps to follow?
-
This error message means that your torrent client is choking on the SSL certificate. In order to get around this, you need to disable the SSL tracker in your profile. You may also need to change the announce URL in your torrent client. Specifically, change the beginning from
https://tracker.gaytorrent.ru/
to
it worked for me changing it on RuTorrent 3.9
Thanks a lot!!! -
This error message means that your torrent client is choking on the SSL certificate. In order to get around this, you need to disable the SSL tracker in your profile. You may also need to change the announce URL in your torrent client. Specifically, change the beginning from
https://tracker.gaytorrent.ru/
to
Do you know what's the root issue though?
For one I'd rather keep using the SSL tracker. Also I don't really feel like modifying the 150+ torrent files I'm seeding or having to re-download and re-hash them…  :-[ -
I'm running into the same problem. Unfortunately, changing to "http://tracker.gaytorrent.tw:2710/" doesn't seem to work — the torrent is no longer loaded at all.
Update: Now I'm seeing the message
 Tracker: [Could not parse bencoded data: The page you are looking for does not exist, sorry (function(){function d(b){var a=window;if(a.addE] -
This error message means that your torrent client is choking on the SSL certificate. In order to get around this, you need to disable the SSL tracker in your profile. You may also need to change the announce URL in your torrent client. Specifically, change the beginning from
https://tracker.gaytorrent.ru/
to
Do you know what's the root issue though?
For one I'd rather keep using the SSL tracker. Also I don't really feel like modifying the 150+ torrent files I'm seeding or having to re-download and re-hash them… :-[
[/quote]Some torrent clients do not want to play well with our SSL CA certificate issuer for some reason.
If you've changed from the SSL to the non-SSL tracker and are still having issues, you may need to use a VPN to connect to our services.
Also, it should be noted that for some reason, Transmission 3.0 will not work with our tracker any longer for some reason. Instead, if you're using Transmission, roll back to the previous version (2.94) and you should have no issues.
-
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.
-
Thanks halcyonboy, that's helpful.
-
I had this problem too. it is because of an expired intermediate certificate from sectigo, that expired may 30th. you can check then certificate chain here
https://www.sslshopper.com/ssl-checker.html#hostname=https://tracker.gaytorrent.ru/
most modern software handles this expiration by skipping to the next one in the chain, but older software doesn't, so it fails. to fix this, you need to remove or disable the certificate on your local machine. on most linux distros, you can edit /etc/ca-certificates.conf and prefix the certificate with a ! to disable its use. so change
mozilla/AddTrust_External_Root.crt
to
!mozilla/AddTrust_External_Root.crt
save, and run
update-ca-certificates
to update the certificate store. it should return with a notice that one certificate was removed.
on BSD systems, you will have to remove the certificate from your certificate store by hand, on OpenBSD that is /etc/ssl/cert.pem.
hope this helps.
source : I do this stuff for a living
-
We installed a new certificate today. Sorry for that one but from now everything should work as expected again :cheers:
