https url port not match to 8920

[JimmyLaurant]

Jellyfin ver.10.8.13
Recently remote visit my NAS, find out Jellyfin desktop shortcut opens like:
https://[privatezone]:8096
SSL errorxxxxxx
Before, it opens like:
http://[privatezone]:8096, no error;
Of course, I found out HSTS is enable, but when url protocol change to https, why JF cannot auto match to https port??
That is, why url not opens like:
https://[privatezone]:8920??

P.S.: default port setting, ssl cetificate is right set.
Need Help.

[TheDreadPirate]

Jellyfin does not offer https on port 8096 and while 8920 is the correct https port for jellyfin, it isn't enabled by default.

If you are using a reverse proxy with Jellyfin, you don't need to specify the http/https port unless they are not default.

[JimmyLaurant]

Jellyfin does not offer https on port 8096 and while 8920 is the correct https port for jellyfin, it isn't enabled by default.

If you are using a reverse proxy with Jellyfin, you don't need to specify the http/https port unless they are not default.

JF https is enable, but not enforced;
Reverse proxy is ok, but use a desktop shortcut is also convenient, right?

[mcarlton00]

This sounds like your browser is forcing https even when it's not available. Several browsers have this feature and I believe it's enabled by default. If you want to use a desktop shortcut, best course of action is probably to just change it's target to port 8920

[JimmyLaurant]

Well, forced https is disable on my browser (firefox).
It's not a windows desktop shortcut, it's on NAS dsm desktop.
My JF is packed by a third-party source, created as an app and is not in docker.
Checked file in /@appstore/Jellyfin/ui, tried to manually change the port from 8096 to 8920, and protocol to https, but no luck, when JF restarts, it forces back to port 8096, and protocol remains https.

This sounds like your browser is forcing https even when it's not available.  Several browsers have this feature and I believe it's enabled by default.  If you want to use a desktop shortcut, best course of action is probably to just change it's target to port 8920

[TheDreadPirate]

[Client] https 443 <--> 443 [Reverse proxy] 8096 <--> 8096 http [jellyfin server]

Is this how you have things setup?

[mcarlton00]

If it's not something packaged or placed by us, then we have no idea how it's been configured or how it's set up. It doesn't sound like it's a Jellyfin problem and more a packager problem

[JimmyLaurant]

[Client] https 443 <--> 443 [Reverse proxy] 8096 <--> 8096 http [jellyfin server]

Is this how you have things setup?

Well, it seems that way, but I didn't particularly set a reverse proxy;
When remote accessing my NAS, I just click on JF shortcut on dsm desktop and the browser opens the JF url.