I run a synology NAS (DS1817+) with an external VPN Network connection set on the unit and local IP which to date of update has worked flawlessly.
Nice update otherwise, thank you .NET core update using less CPU time now.
Until upgrade to the recent synology build the local network which uses 10.0.0.0 ect and still does connected to the Emby server on the NAS and used this range of IP.
After upgrade with the VPN on the Emby server picks up the VPN IP which is wrong and fails to connect.
Manual entry of the correct IP in the emby app for the server does not work.
The only solution in my ignorance is to turn off the VPN connection and then emby will connect from the shield TV
I will add that the issue does not occur when using a mobile app or Mac or PC which strangely defaults to the VPN ip and this issue therefore only occurs when using the Nividea Shield TV, it seems the emby app is now looking at the VPN as default rather than the local IP range set on the network and NAS.
No other related apps have this issue.
It also when the VPN is enabled allows Emby conection as explained and shown in the images via the local Lan using the VPN IP as the server and guess it makes sense other than the shield TV does not now like the setup and refuses connection.
Ideas suggestion and help please as I am now lost and prefer to use the external VPN for other NAS applications if possible but retain use of the shield TV, is this a bug with the shield TV app?
Vpn1.png 19.89KB 3 downloads
VPN.png 19.98KB 2 downloads
Emby 1.png 11.21KB 2 downloads
Edited by Xeuz, 22 April 2019 - 05:01 AM.