Support for External + Internal jellyfin access

My setup and probably many others have setup external access to Jellyfin. I have configured infuse to use the internal/local IP because using the external means I constantly have to upload and download on my network.
So to watch my library when I am away from home, I have to re-add my library using the external URL.

So my feature suggestion is: Support for both Internal and External, so when I add my Jellyfin library in infuse, I can add the URL for both internal and external.

I don’t know how this would be implemented:

  • ping the local IP first, if no connection; use external ? and maybe give a small toast notification on which it is using
Internal: 192.x.x.x.x.x

I feel like this should be handled by the user for example via a split horizon dns or even NAT hairpinning. A more secure option would be something like a site-to-site VPN.

1 Like

For ease of use, I would still prefer my proposed suggestion.