HTTPS issues connecting to tracker about docker-transmission HOT 5 CLOSED

Or need to add env to not verify SSL cert.

Sorry to reply on this already closed ticket. I've encountered the same issue because the tracker I'm trying to download to uses a self-signed certificate. As of Transmission 3.00 SSL verification is enabled by default.
A workaround that I tried and worked consists on set the TR_CURL_SSL_NO_VERIFY env variable to 1

from docker-transmission.

I am unable to reproduce this on a debian or ubuntu host. This issue could be specific to synology

from docker-transmission.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from docker-transmission.

I have the same issue with latest 3.0.0 build.
I believe this is due to alpine image and libcurl not able to verify SSL certificates. ca-certificates is not included in this transmission image. Or need to add env to not verify SSL cert.

from docker-transmission.

I have the same issue with latest 3.0.0 build.
I believe this is due to alpine image and libcurl not able to verify SSL certificates. ca-certificates is not included in this transmission image. Or need to add env to not verify SSL cert.

I use the latest build with ssl trackers fine. (as do MANY of our users) I'm going to close this and if you have an issue, you can open a new issue and provide logs/compose etc, but i can definitively tell you, "https" works fine

also libcurl is working fine...

root@c8c5aecdd54e:/# curl --insecure -v https://www.google.com 2>&1 | awk 'BEGIN { cert=0 } /^\* Server certificate:/ { cert=1 } /^\*/ { if (cert) print }'
* Server certificate:
*  subject: C=US; ST=California; L=Mountain View; O=Google LLC; CN=www.google.com
*  start date: Jul  7 08:10:21 2020 GMT
*  expire date: Sep 29 08:10:21 2020 GMT
*  issuer: C=US; O=Google Trust Services; CN=GTS CA 1O1
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55af47ee53a0)
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
* Connection #0 to host www.google.com left intact

and ca-certificates is included

from docker-transmission.