PMS refuses to connect on Nvidia Shield Pro 2019

Server Version#: 1.18.6.2368 (smb)
Player Version#: 7.28.0.15501

Hello,

I have a major issue with a brand new Nvidia Shield TV Pro 2019 and the Plex Media Server on it. Everything (OS, PMS and apps) is updated to the latest available version. After performing initial setup of the PMS I’m unable to access my new server to add libraries to it or do any additional configuration. The Shield is normally connected via an ethernet cable but I also tried using wifi (router is 2 meters away) but neither makes a difference. I tried the following:

  1. Visit https://plex.tv/web - the Shield server is missing from the list of servers. I can see my other servers (2 windows and 1 linux) and use them as normal.

  2. Visit http://LOCAL_SHIELD_IP:32400/web from a PC on the same network - “No soup for you!” error appears. The Shield server is nowhere to be found.

  3. Visit http://MY_NETWORKS_PUBLIC_IP:32400/web a PC on another network - “No soup for you!” error appears. Behaves in the exact same way as when I use the local IP which makes sense since my router is configured to do a port forward to the Shield so it’s basically the same thing.

  4. Visit http://LOCAL_SHIELD_IP:32400/web from a browser I side-loaded on the Shield - “No soup for you!” error appears. Exact same behavior.

I’ve tried re-installing all Plex related application and did 4 factory resets and re-updates so far to no avail.

The relevant option in Plex Settings says the server is Running and it shows the radio button set to “On” when I click it.

What can be causing this problem? Any assistance on this is greatly appreciated as I bought the Shield with the sole purpose of it serving as a Plex server and it has been failing to perform it’s task since it’s arrival.

Thank you in advance!

1 Like

A follow-up on this for whomever may be having the same issue - the problem was coming from the fact that my internal network was set up with an “abnormal” IP range that wasn’t following the 192.168.*.* pattern. Even though the Shield was getting connected to the internet and various services were running normally the allocated internal IP was messing up the Samba server and it was seeing the internal IP as external making it think it simply just doesn’t have an internal IP at all. That killed the Transfer files over local network functionality with an error message “No ethernet or wifi connection” and it also seemed to affect the PMS itself and made it unreachable/not-claimable through the web app.

Once I changed my router settings so my internal network follows the RFC 1918 standard, factory reset the Shield and re-updated OS and apps the sharing feature started working and the PMS appeared normally.

All this was made possible by the great guys from Nvidia’s support team which spent almost a week debugging with me.

2 Likes

Great job, man!
I had the same issue with nVIDIA Shield TV 2017, and everything was updated to the latest version. Transfer files over local network function can’t be enabled, as long as I did everything I could do. Before I read your comment, I nearly give up installing Plex media server on Shield TV.

Did nVIDIA team have any plan to fix this bug? I have no chance to change my “abnormal” IP range now. If I did this, I had to rebuild my server totally. :fearful:

Unfortunately I strongly doubt they’ll do anything about this as it’s not really a bug. Technically they are following network standards on this (RFC-1918 to be exact) and we aren’t, so we are at fault here. I believe this situation even triggered the creation of a new knowledge base post in their guides/FAQ section so it doesn’t look like they are planning to do something about it.

1 Like

Shield TV team followed RFC-1918, but we followed CIDR ( RFC 1518 | RFC 1519 ), right?
Could you post the link you discussed with Shield TV team? I really want to raise a request for our issue. I want that expensive chip to work rather than sleep in its own shell.

https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/341614/cant-access-storage-over-local-network/

Shield@nVIDIA’s replay

Shield uses the definition I explained for enablement of this feature. If you want to use this feature, your shield needs to be in one of those IP ranges.

What a GREAT team.
Could I translate it to this?
“Change your address, reset system configuration, I have nothing to do with your issue”

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.