can't connect to tracker with HTTPS. http is fine. [solved]

Ask for help and report issues not specific to either the Mac OS X or GTK+ versions of Transmission
Post Reply
c4naan
Posts: 7
Joined: Thu Dec 29, 2016 3:09 am

can't connect to tracker with HTTPS. http is fine. [solved]

Post by c4naan »

I just installed 2.92 (14714) on my Raspberry Pi3. The deamon starts fine and I can download torrents. However trackers that use HTTPS will not connect. If I download a https torrent, but then edit the announce to just be http:// it connects fine.

I get the error:
Tracker: Could not connect to tracker.

any tips?
Last edited by c4naan on Thu Dec 29, 2016 5:00 am, edited 1 time in total.
c4naan
Posts: 7
Joined: Thu Dec 29, 2016 3:09 am

Re: can't connect to tracker with HTTPS. http is fine.

Post by c4naan »

it turns out it was my install/version of Transmission running on LibreElec that was the issue.
I followed this post and was able to get transmission working with https.

essentially I had to download the openelec release, edit the version dependencies as listed here and change the 'openelec' to 'libreelec' in the addon.xml file. then copy the libcrypto 35 file to the appropriate folder and I am up and running :)
maki.ato
Posts: 70
Joined: Fri Apr 15, 2011 10:20 pm

Re: can't connect to tracker with HTTPS. http is fine. [solved]

Post by maki.ato »

At first, I solved this problem as suggested on my forums by adding

Code: Select all

export TR_CURL_SSL_NO_VERIFY=1
to the beginning of /share/CACHEDEV1_DATA/.qpkg/QTransmission3/QTransmission3.sh

But what it does is it enables connecting to https trackers insecurely, same as curl -k, which is not that desireable. Then I decide I can do better than that, so:
1. I Downloaded the cacert.pam file from https://curl.se/docs/caextract.html and placed it in: /share/CACHEDEV1_DATA/.qpkg/QTransmission3/ssl/certs (depending on where you Transmission is installed, you may need to replace CACHEDEV1_DATA).
2. Added

Code: Select all

export CURL_CA_BUNDLE="${QPKG_ROOT}/ssl/certs/cacert.pem"
to QTransmission3.sh instead of that TR_CURL_SSL_NO_VERIFY variable, to point libcurl to the certificate file just added.

Now it's all good.
Don't forget to always make backups of files before making any changes.
Gogetta
Posts: 1
Joined: Mon Nov 29, 2021 7:34 pm

Re: can't connect to tracker with HTTPS. http is fine. [solved]

Post by Gogetta »

maki.ato wrote: Sun Oct 24, 2021 9:25 am At first, I solved this problem as suggested on my forums by adding

Code: Select all

export TR_CURL_SSL_NO_VERIFY=1
to the beginning of /share/CACHEDEV1_DATA/.qpkg/QTransmission3/QTransmission3.sh

But what it does is it enables connecting to https trackers insecurely, same as curl -k, which is not that desireable. Then I decide I can do better than that, so:
1. I Downloaded the cacert.pam file from https://curl.se/docs/caextract.html and placed it in: /share/CACHEDEV1_DATA/.qpkg/QTransmission3/ssl/certs (depending on where you Transmission is installed, you may need to replace CACHEDEV1_DATA).
2. Added

Code: Select all

export CURL_CA_BUNDLE="${QPKG_ROOT}/ssl/certs/cacert.pem"
to QTransmission3.sh instead of that TR_CURL_SSL_NO_VERIFY variable, to point libcurl to the certificate file just added.

Now it's all good.
Don't forget to always make backups of files before making any changes.
Just got this working after some time of trying (not the cleverest person). I thought the code need the $ sign at first but after I removed this it worked a charm. Got the HTTPS error today after years of it working fine. Always used CAcert.qpkg and QPerl.qpkg before which worked fine up until now. This solutions works well though. Thanks maki
Post Reply