HTTPS Trackers Cannot Connect

kman · Post by **kman** » Tue Jan 08, 2019 9:18 pm

Hello - recently a private tracker I use had its certificate updated and now I am getting "Could not connect to tracker" error.

Code: Select all

Jan  8 14:10:28 transmission-daemon[22386]: web will verify tracker certs using envvar CURL_CA_BUNDLE: none (web.c:400)
Jan  8 14:10:28 transmission-daemon[22386]: web NB: this only works if you built against libcurl with openssl or gnutls, NOT nss (web.c:401)
Jan  8 14:10:28 transmission-daemon[22386]: web NB: invalid certs will show up as 'Could not connect to tracker' like many other errors (web.c:402)

I am using Transmission 2.94 on ASUSWRT. How can i force Transmission to ignore the SSL verification?

Any help will be appreciated.