iPad trouble logging in through WireGuard connection

[C.S. 95]

Hi. I put emby on my friend's ipad and it works great with a wireguard connection using a local address direct to my network. Only problem is sometimes after a period of inactivity the wireguard connection gets out of kilter and needs to be reset. If my friend attempts to log in to emby while the WG connection is out of sorts, emby falls back to the remote SSL connection, for which my friend is not authorized. If she toggles WG off and on, then tries to log in again, emby keeps defaulting to the remote address, and she can't get in. Only by closing emby completely or restarting the ipad can she get back in when this happens.

Anyway it's a bit of an inconvenience and I'm wondering if anything can be done. I'm thinking a client-side option to force local / remote would fix it, but if there's a simpler solution, that would be great too.

[Luke 42271]

Hi, does the local address that you want to use match what is displayed on the server dashboard?

[C.S. 95]

Yes for sure. 

[Luke 42271]

Quote

Only by closing emby completely or restarting the ipad can she get back in when this happens.

OK I think another way would be to just click your user icon and go through the server selection process again.

[C.S. 95]

Thanks I'm sure that's also a great workaround.

The thing that sorta vexes me though is the app is trying to connect to an address and port that have never been entered manually. It's just, ya know.. there's a reason I never gave her the remote address -  I just don't want her connecting that way. In this instance, and I know this setup is not standard, but it's not really edge-case either, I feel like there could be more control over how clients connect.

Perhaps a server-side option to instruct clients (after first login) to set either local or remote as the address to always try first. Or my first thought was a place on the login screen to set the connection method to 'Always Local' or 'Always Remote', with the default of course being 'Try both'.

Or some kind of workaround that sticks. But I guess that would be a fix, not a workaround.

[Luke 42271]

Quote

The thing that sorta vexes me though is the app is trying to connect to an address and port that have never been entered manually. It's just, ya know.

It helps most users as they transition from local to remote and also if the server ip address changes.

Maybe an option in the client connection process to never do this.