Jump to content

IP problems since upgrade to - Synology VPN - Shield TV

Recommended Posts


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 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?






Many thanks. 

Edited by Xeuz
Link to post
Share on other sites

Hi there, does the server dashboard display the correct remote address?

HI thanks for the reply, please see the attached images in the original post, when the (synoogy) VPS is turned on the IP for the emby server changes to the IP of the VPS, resulting in no connetion from the shield TV, other methods, phone, PC, Mac interestingly still work with the changed VPS IP. 

The default should be the local network DHCP address and no the VPS.


The emby server should not be changing to use the VPS allocated local IP but retain the DHCP allocated IP when the VPS is connected, much like it did before update.


The exception and issue connecting is only relevant to the Shield TV objecting to the new IP allocated by the VPS and used by the Emby server, the code must simply look for the machine IP and not be able to differentiate the VPN against the DHCP allocated real local network IP.


Hope this makes it more clear, thanks in advance. 



Edited by Xeuz
Link to post
Share on other sites
  • 2 weeks later...



Apply latest Synology build, open emby server settings, go to advanced, set the server (Synology NAS) default local IP.

Shield TV now works as designed. 

VPS in Synology network can now be reconnected without IP change by emby to the live VPS.


I thank Luke for his responce, and hope this assets someone in the future. 

Edited by Xeuz
  • Like 1
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...