You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like jellyfin to check all known servers before showing the login dialog with the serverlist.
Additional context
Currently, when a server cant be reached, the user is redirected to the login-ui where a new ip can be entered or a known one choosen.
However, i think it would be a better user experience, when the app would try to reach any other known server when the primary cant be reached. When one known server is reached, that one will be selected and loaded, so that the experience is seamless.
My reasoning is that most users have a very short list of jellyfin instances they connect to, and only one per network. With my suggestion, the user would always be connected to a working instance (if one is reachable). Only users that have two or more instances reachable at the same time might be connected to the wrong server, if the previously selected server is unavailable.
The text was updated successfully, but these errors were encountered:
Concur. I'm using it from home 98% of the time. The 2% of the time I'm not on my home lan, I would appreciate not having to manually enter my server's public address. It doesn't seem to be remembered, perhaps because I'm on port 12322 through a reverse proxy.
I don't ever want it to default to my public address, because that would needlessly consume bandwidth on my router's external interface. But I would really like to not have to type in a url and port number every time I'm out of the house.
Describe the feature you'd like
I would like jellyfin to check all known servers before showing the login dialog with the serverlist.
Additional context
Currently, when a server cant be reached, the user is redirected to the login-ui where a new ip can be entered or a known one choosen.
However, i think it would be a better user experience, when the app would try to reach any other known server when the primary cant be reached. When one known server is reached, that one will be selected and loaded, so that the experience is seamless.
My reasoning is that most users have a very short list of jellyfin instances they connect to, and only one per network. With my suggestion, the user would always be connected to a working instance (if one is reachable). Only users that have two or more instances reachable at the same time might be connected to the wrong server, if the previously selected server is unavailable.
The text was updated successfully, but these errors were encountered: