-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Enhancement]: Use A Different Server Option #1519
Comments
Sounds like connected/duplicate to that: #209 But in general a solution you are looking for is split DNS. |
I'm a little confused by this request. Does the "switch server/user" button in the side menu not work? Both the "Connect to Server" and "Switch User/Server" take you to the page to change how connecting to the server. |
No, the "Switch Server/User" is only there if you are already connected to a server. It is not visible when it is trying to connect to a server that you are no longer connected to. |
You can still switch the server by clicking the top button and then selecting the other server. |
Okay, got it. I must have been doing something wrong or clicking the wrong thing. Thank you for your help. |
Describe the Feature/Enhancement
Upon starting the app, it would be nice to have an option to choose a different server like how it's done with Jellyfin.
Why would this be helpful?
I use Tailscale to connect to my library when I'm away from home, however when I'm at home I connect directly through my home network. If I log in at home and then wish to continue listening to an audiobook when I'm not at home, I cannot switch to the Tailscale IP address as it just tries to log into the home network. Therefore an option to change network would be really nice.
Great app, by the way. I really like it.
Future Implementation (Screenshot)
This could be a "Choose Network" button just under the "Connect" button.
Audiobookshelf App Version
Android App - 0.9.79
Current Implementation (Screenshot)
The screen that appears when you start the app and can't connect to your home network.
The text was updated successfully, but these errors were encountered: