2025-04-06, 07:59 AM
Installed Jellyfin from the pdulvp gitup package 10.10.6-02 on my TVS-h874t QuTS 5.2.4. Had it running but uninstalled to clear up some issues with an Emby server. Reinstalled. Now I get
1. Invalid password even though I haven't set up one on the new installation if I go to http://10.0.0.25:8096/web/#/login.html?serverid=4e.....
If I select "admin" for username and forgot password get error "Please try again within your home network to initiate the password reset process". The Mac web browser I am using and the QNAP NAS are on the same home network.
Likely that this server ID is a leftover from a previous installation due to browser history.
2. Get error "we're unable to connect to the server" if I go to IP:8096/web/#/selectserver.html or IP:8086 and select the server. So it sees jellyfin on 8096 as it displays the server selection page but won't connect to it.
So I seem to connect using an outdated URL, but can't connect with the standard address.
Looked to find where the listening port is defined in the config directory but didn't see it in the system.xml file. Log files didn't seem to show the connect failure.
1. Invalid password even though I haven't set up one on the new installation if I go to http://10.0.0.25:8096/web/#/login.html?serverid=4e.....
If I select "admin" for username and forgot password get error "Please try again within your home network to initiate the password reset process". The Mac web browser I am using and the QNAP NAS are on the same home network.
Likely that this server ID is a leftover from a previous installation due to browser history.
2. Get error "we're unable to connect to the server" if I go to IP:8096/web/#/selectserver.html or IP:8086 and select the server. So it sees jellyfin on 8096 as it displays the server selection page but won't connect to it.
So I seem to connect using an outdated URL, but can't connect with the standard address.
Looked to find where the listening port is defined in the config directory but didn't see it in the system.xml file. Log files didn't seem to show the connect failure.