[Issue]: "Open Jellyfin" no longer specifes port - will not open web interface properly.

[rsg73]

Please describe your bug

1. Right click Jellyfin taskbar icon in Windows 10 while Jellyfin server is running.
2. Select "Open Jellyfin"

In the past this would open a browser window to localhost:8096 which would open the Jellyfin web interface. Since v 10.8 this no longer happens. When "Open Jellyfin" is selected, the browser tries to open "localhost/web/index.html" which throws an error as the port is not specified. When the port is added manually it opens normally.

Is this the intended behavior now, or is there a setting that needs to be modified, or did somebody just forget to add the port in to the address? Again, I have never had this problem prior to 10.8.X

Selecting this:

Returns This:

And subsequently this:

Jellyfin Version

10.8.0

if other:

No response

Environment

- OS: Win 10 Pro
- Virtualization: n/a
- Clients: Browser
- Browser: Firefox/Chrome/Edge (i.e. all)
- FFmpeg Version: n/a
- Playback Method: n/a
- Hardware Acceleration: n/a
- Plugins:n/a
- Reverse Proxy: n/a
- Base URL: n/a
- Networking: n/a
- Storage: n/a

Jellyfin logs

No response

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[anthonylavado]

If you go to "C:\ProgramData\Jellyfin\Server\config", do you have a network.xml file?

If so, what's listed under NetworkConfiguration/PublicPort?

[rsg73]

Thanks Anthony, that was indeed the issue.

PublicPort was set to 80. Switching to 8096 did the trick.

However, when I shut down the server, exited Jellyfin and then restarted, PublicPort is now back to 80 in the config file, so I had to repeat the reset of the port in the config. I assume there is a way to make that change permanent?

Cheers

[anthonylavado]

@rsg73 It should be from the UI, the last time I checked.

Dashboard > Advanced > Networking. Set the public port, scroll down and click Save.

[rsg73]

Hi Anthony. I figured out what is going on.

Dashboard>Advanced>Networking>Remote Access Settings

I changed the "Public HTTP Port Number" and restarted the server - and this in turn changed the PublicPort setting in the network.xml file.

I changed this:

And after restarting the server, this was the result in config file.

I just updated to 10.8.5 this morning, so assume its an issue with this build? (I don't believe this was the behavior in previous builds.

Dashboard > Advanced > Networking is still set at 8096, so I don't think that setting is the culprit here.

[anthonylavado]

You know what - I wonder if I'm grabbing the wrong field from the XML. I should be grabbing the local http port, not the public one. D'oh!

Will fix. It wouldn't be generally available unless at least the next release, but I should be able to make a hotfix build for you.

[rsg73]

"...grabbing the wrong field from the XML." That is what I assumed.

Unless other people are suffering, I don't think you need to spend time on a hotfix. It is not causing any problems for me so I can wait until the next build - and I am sure you have more important things to work on.

Cheers :)