@SimonSaid:

@MrMazda
I've been getting the following error in rtorrent since a few days:

  Tracker: [Peer certificate cannot be authenticated with given CA certificates]

Do you know what's going on?

Hi @SimonSaid

Also been having this issue, I managed to track down a solution that was suggested a few years ago in a different scenario with rtorrent, and it seems to be working again. I have posted it here: https://forum.gaytorrent.ru/index.php?topic=66678.msg342248#msg342248

It does seem to fix the problem in rtorrent/rutorrent. Hope it helps.

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/10

The 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=0

While 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.

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/10

The 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=0

While 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.

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.

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)

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