[Feature] Allow server endpoint to be changed in Android app #2335
Replies: 9 comments 5 replies
-
In that case (that the endpoint server address or port was changed on your backend already but you had still been logged in to the mobile app with the original endpoint) you won't be able to logout of the mobile app (Android only running 1.54.0 build.77 as far as my testing) and you will be required to delete the mobile app data to then have the ability to change the server endpoint on the login dialog. It is not ideal. |
Beta Was this translation helpful? Give feedback.
-
I've run into this myself. I am a software developer, but I do almost exclusively backend services. Haven't played with android in about a decade and I've never played with flutter. That said, if somebody has the time to point me in the right direction I can probably implement this feature. In my mind it would just be adding another item in the settings that holds the server url, but whatever you all think is best I'm up for. |
Beta Was this translation helpful? Give feedback.
-
I think for the mobile app, since the server is always self-hosted, and since many users have or are playing with different ways of either using opened ports on their router, or tunneling with a VPN, or using an external service such as Tailscale or Cloudflare Tunnels to ultimately get to their Immich server endpoint, that it would also be nice to have a way to have a settings area in the mobile app UI, and perhaps also in the admin user's UI as well (although for the later I don't know if that is necessary to have), to be able to configure multiple endpoint URL addresses, like perhaps up to 4 or so. Since the server application is self-hosted always this makes sense, as without it then the user of the mobile app, which may be a family member or someone not so familiar things, has to attempt the endpoint connection with mobile app, then if they can't make the connection, possibly because the admin has changed the way the endpoint could even be able to connect, always must be told to logout or clear app data, then be told what the new / current endpoint method is. If the server Explanation: I want the mobile app to utilize local IP address on the primary / first attempt to make a connection to the endpoint URL, perhaps that primary URL would be the internal IP address. If it cannot reach that address in a specified (by the mobile app) or just go with a default timeout value that is hard coded, then it falls over to the secondary / second endpoint URL that the admin already had preconfigured in his UI. If it can't reach that endpoint in a timely manner it attempts at the third endpoint URL, and it if times out getting there it simply cycles back to the primary / first endpoint URL, and then just goes in that loop until it makes a connection or until the user exists the mobile app. This could make the difference if the admin normally prefers to connect via mobile app while at home on the internal IP address using http on default port 2283, but when he leaves home he wants the mobile app to utilize Tailscale DNS address on https, on a different port, perhaps that is behind nginx proxy. Basically it would be good so that the mobile app doesn't just have a single endpoint URL entry to support self-hoster's that utilize or have implemented or are just playing around with multiple different methods of tunneling or otherwise opening ports for forwarding to be able to, without dealing with always having to change the endpoint setting in the mobile app, since it currently only attempts a single endpoint address entry, the priority of the order in the endpoint # 1, endpoint # 2, endpoint # 3 configurable setting in the mobile app per user of the app would determine the order in which it always attempts to make that connection to the one Immich server. I don't know if you follow me on why this would be good to have but if you need further clarification let me know! I can create a feature request for it. |
Beta Was this translation helpful? Give feedback.
-
Having a similar issue where my request was deleted as a duplicate of this thread. Even simpler than how you’re connected and how it needs to route, I wish there was a way to have multiple servers to switch between. I run a test and a production server and want a quick way to jump between the two without having to remember an IP/URL. It would be fine if you still had to sign out but the login screen had “stored” connections and log in credentials. |
Beta Was this translation helpful? Give feedback.
-
It would be great to have both remote and local address options |
Beta Was this translation helpful? Give feedback.
-
I understand it may have security implications, but I would really like immich app to allow following 301/307/308 redirects. Even if new/changed redirects would pop up a confirmation/security warning that would reduce most concerns I think. edit: seems like I had some unrelated certificate errors. 301 seems to do something, but fails at login. |
Beta Was this translation helpful? Give feedback.
-
Would love this feature also. I recently setup homelab wide SSL certs and therefore my immich endpoint address has changed, same server and files, just a different address. Would be great to be able to just soft update these details Would also appreciate the dual option as others have mentioned! |
Beta Was this translation helpful? Give feedback.
-
Just a heads up on this, since I found myself in the same situation. The quickest way is currently to just log out of the old server and log again in the new one. It is pretty transparent. |
Beta Was this translation helpful? Give feedback.
-
I think the same way slack allows multiple workspaces or pager duty allows account switching would be great. Especially when you find yourself becoming the admin for multiple families :) |
Beta Was this translation helpful? Give feedback.
-
The feature
I changed the server endpoint in my internal network, and after much searching Settings and Backup menus, as well as throughout the interface, I could not find any way to delete / update / add the server endpoint in the app short of deleting app data.
That method is serviceable but probably scary or confusing for non-technical users. It would be much better if there were a button within the app to change the endpoint. Maybe it functionally does the same thing as deleting all application data with a warning, but doing it "within the app" is a more comfortable UX.
Better than that would be if you could maintain all other settings, changing only the endpoint:
Platform
Beta Was this translation helpful? Give feedback.
All reactions