SOLVED: Unable to login/Change password on QNAP

[Caprichoso]

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.

[TheDreadPirate]

Remove all the stuff at the end of the URL. Just http://10.0.0.25:8096 in a private/incognito tab. Since you are probably hitting some emby or jellyfin cached data.

[Caprichoso]

Thanks, that did it! Up and running.

2 other questions.

When you are referring to "cached data" are you referring to my browser cache, or some cache on the server?

In the conf directory system.xml doesn't seem to specify the listening ports. Emby allows them to be changed there. The JellyFin admin panel allows the ports to be changed there. Is there any other way to change them, i.e. if you have a port conflict and need to start the server with different ports?

[theguymadmax]

1. Browser cache
2. network.xml

[TheDreadPirate]

@theguymadmax - Something I learned last night from another user in the Matrix/Discord chat: Network.xml is not generated until you go through the setup wizard. HOWEVER, you can manually create one with just enough content to change ports if needed.

Code:

<?xml version="1.0" encoding="utf-8"?>
<NetworkConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <InternalHttpPort>8096</InternalHttpPort>
</NetworkConfiguration>

The user in chat needed IPv6 enabled in their IPv6 only environment, which is off by default. So they enabled it by manually making network.xml with just the IPv6 line.