"Could not connect to tracker" via HTTPS

Ask for help and report issues with the Windows version of Transmission
Post Reply
MoveData
Posts: 4
Joined: Fri Jan 06, 2017 3:50 pm

"Could not connect to tracker" via HTTPS

Post by MoveData »

Many thanks for offering a Windows version in the main downloads page. Only issue I'm having with it (Windows 10 Pro / v.2.92.14714-x64.msi - early preview) is that with HTTPS announce URL's I'm always getting "Could not connect to tracker". HTTP works fine. Only using the Desktop client, did not install the rest.

Should I try a nightly version or something else might be going on? It's strange though that these torrents are not in Transmission's "Error" category and trackers seem to report that the connection is fine.

Thanks again!
Elroy
Posts: 5
Joined: Fri Mar 03, 2017 6:29 pm

Re: "Could not connect to tracker" via HTTPS

Post by Elroy »

Have the same issue here.

But I'd installed transmission-daemon (service mode) with WebUI.

If I use Qt version, everything works fine. But daemon can't connect to HTTPS.

Already did NAT forward.
MoveData
Posts: 4
Joined: Fri Jan 06, 2017 3:50 pm

Re: "Could not connect to tracker" via HTTPS

Post by MoveData »

Ok, I've installed the last stable nightly build (found here) and this issue is solved/not present.

:)

(seems deleting torrents in the UI doesn't work in either version - will wait for updates)
Elroy
Posts: 5
Joined: Fri Mar 03, 2017 6:29 pm

Re: "Could not connect to tracker" via HTTPS

Post by Elroy »

Thanks for the advice.

Downloaded transmission-2.92+-re4ee96c30d-x64 and now transmission-daemon is working properly with trackers.

I'll check if deleting torrents have the same behaviour here and let you know.
Elroy
Posts: 5
Joined: Fri Mar 03, 2017 6:29 pm

Re: "Could not connect to tracker" via HTTPS

Post by Elroy »

Deleting torrents on Daemon is working properly too.
Post Reply