Can't connect over HTTPS / nginx

[ElDavoo]

Hello, I can connect to my transmission locally with an ip address (not using http) but I can't manage to connect using its domain name. I can connect using the same settings with transmission-remote-gui . Transmission is exposed on my LAN at 192.168.1.4:9093/transmission/rpc, without https. Nginx takes care of doing the reverse proxy and https job, so I have https://mydomain:443/transmission/rpc . How can I debug the problem? Thank you very much, David

[equeim]

You can run tremotesf from command line and see what error does it print. How did you setup TLS with nginx, does it use self signed-certificate? Can curl perform request to https://mydomain:443/transmission/rpc from command line?

[ElDavoo]

Hello, nginx is using a "standard" TLS configuration, HTTPS only setup for websites. curl gives back as expected: <h1>401: Unauthorized</h1><p>Unauthorized User. 1 unsuccessful login attempts.</p> The official Windows build gives back "connection error". It doesn't stay attached to the terminal so I can't see the error. However, I tried compiling and running tremotesf on Linux and it works! So it's either something fixed in last commits or something Windows-specific.