Could not connect to tracker after moving to https

Ask for help and report issues not specific to either the Mac OS X or GTK+ versions of Transmission
Post Reply
ardagast
Posts: 1
Joined: Tue Jan 24, 2012 10:03 pm

Could not connect to tracker after moving to https

Post by ardagast »

Hi,
I want to test SSL support on private tracker. Everything was working great on http torrents, but when I add https torrent i get:

Code: Select all

Announcing to tracker (announcer.c:1484)
Could not connect to tracker (announcer.c:982)
Retrying announce in 334 seconds. (announcer.c:991)
I`m on ubuntu server 11.10 x86, up-to-date packages.

Tracker address, port number in torrent file are valid. I would really appreciate your help, because I have no idea whats wrong...
NisseDILLIGAF
Posts: 7
Joined: Wed Sep 21, 2011 9:34 am

Re: Could not connect to tracker after moving to https

Post by NisseDILLIGAF »

Any news on this??

I upgraded my ubuntu to 12.04 ... and now I can't download from https trackers...!!??
if I try a http tracker it works....

any help please..?

/Nisse
rb07
Posts: 1400
Joined: Sun Aug 24, 2008 3:14 am

Re: Could not connect to tracker after moving to https

Post by rb07 »

NisseDILLIGAF:

If it was working before you upgraded, then the problem is that you forgot to install the "CA cert bundle" that SSL (and therefore curl, which is used by Transmission) needs to verify the server.

The other case is when the server doesn't have a valid certificate, you could ignore the invalid/false/whatever certificate (at your own risk) with some parameter in an environment variable which I don't remember right now.
rb07
Posts: 1400
Joined: Sun Aug 24, 2008 3:14 am

Re: Could not connect to tracker after moving to https

Post by rb07 »

Correction: By default Transmission doesn't verify the server. The environment variables are user to enable that verification.

TR_CURL_SSL_VERIFY
CURL_CA_BUNDLE

Those are the environment variables.

Perhaps the upgrade has enabled that option... in other words, the person(s) who made that upgrade modified the source code or set the first variable in the start-up script. Either that or libcurl made the change (perhaps a bug since Transmission sets the option not to verify).
opticmoose
Posts: 1
Joined: Mon May 07, 2012 6:57 am

Re: Could not connect to tracker after moving to https

Post by opticmoose »

What are the values for the environment variables. I tried setting them but to no avail. I'm having the exact issue above as well, with Ubuntu and the newer versions. :(
Edit:

https://bugs.launchpad.net/ubuntu/+sour ... bug/937537
Apparently there is a workaround. I haven't tried it yet.
NisseDILLIGAF
Posts: 7
Joined: Wed Sep 21, 2011 9:34 am

Re: Could not connect to tracker after moving to https

Post by NisseDILLIGAF »

Thanx!!

Got it working now :)
Downloaded libgnutls26_2.12.18-1_amd64.deb and installed it with 'sudo dpkg -i libgnutls26_2.12.18-1_amd64.deb'
mk4umha
Posts: 1
Joined: Sun Aug 05, 2012 9:59 pm

Re: Could not connect to tracker after moving to https

Post by mk4umha »

I installed http://packages.debian.org/wheezy/amd64 ... 6/download and it still won't connect to any of my SSL Trackers. I had LAMP installed, do i need to uninstall any packages first?

update
I uninstalled LAMP and removed everything, then re-installed transmission daemon and the deb package and still no go. Any Ideas on how to fix this? I'm on Ubuntu 12.04.
Post Reply