SOLVED: Windows client won't connect to https server

[serlmercant]

Up till now I have been using Jellyfin remotely through http and port forwarding (which I know is a bad idea) but I am trying to get it set up the proper way. Using Zoraxy as a reverse proxy app within TrueNas Scale, I was able to setup an SSL certificate for my domain and point it towards my server's IP and port (I am still using the default http port 8096 which should be fine since external traffic is passed through the proxy). Https works fine when accessing the web client in my browser (the lock icon reports "connection secure") but I lose the ability to connect via the Windows desktop client unless I allow http connections in Zoraxy, defeating the purpose. Typing in my domain (with or without a port specified) always defaults to http and fails to connect, even if I add the https:// prefix. Strangely, if I open the client when my server is in https mode, it shows an unresponsive version of the add server page (the url is there and editable but the "connect" button is greyed out).

Anyone have an idea what might be causing the issue and how to fix it?

I am using the latest versions for both the server (10.11.2) and client (1.12).

[alleycat]

Up till now I have been using Jellyfin remotely through http and port forwarding (which I know is a bad idea) but I am trying to get it set up the proper way. Using Zoraxy as a reverse proxy app within TrueNas Scale, I was able to setup an SSL certificate for my domain and point it towards my server's IP and port (I am still using the default http port 8096 which should be fine since external traffic is passed through the proxy). Https works fine when accessing the web client in my browser (the lock icon reports "connection secure") but I lose the ability to connect via the Windows desktop client unless I allow http connections in Zoraxy, defeating the purpose. Typing in my domain (with or without a port specified) always defaults to http and fails to connect, even if I add the https:// prefix. Strangely, if I open the client when my server is in https mode, it shows an unresponsive version of the add server page (the url is there and editable but the "connect" button is greyed out).

Anyone have an idea what might be causing the issue and how to fix it?

I am using the latest versions for both the server (10.11.2) and client (1.12).

This is simply how it should work not knowing your full setup, (I'm unfamiliar with Zoraxy, but most reverse proxies work the same). Open up port 443 in your router. (This is for the reverse proxy). If you have port forward 8096 in your router, remove it). In the reverse proxy backend, point it to the local IP (not the FQDN) and port 8096. The FQDN should be in the proxy frontend.

[serlmercant]

Done, done, and done. Since https works in the browser client, I think there must be some way that the desktop client connects differently.

[alleycat]

Done, done, and done. Since https works in the browser client, I think there must be some way that the desktop client connects differently.

I'm using Jellyfin Media Player at a remote client. Just use the FQND in the client like https /your-domain-name.com without any port number, the proxy will handle that.

[serlmercant]

I tried pretty much every iteration of the address (with/without http/https; with/without a port) to no avail.

[serlmercant]

Ok I think I found the fix: I needed to completely disable http requests in the Zoraxy status page rather than auto-redirect them to https. Something about the auto-redirect must have confused the client app.