Interesting. I have not seen canyouseeme give incorrect results. Especially if the Plex remote access page indicates things are working.
One other way to verify:
Check the Plex Dashboard when someone is streaming remotely (click the button thingy on the right to expand the view).
Is the connection local, remote, or indirect?
If indirect, then it is using Plex Relay, which tunnels the stream through a Plex host.
It indicates remote access is not working correctly.
I’ll give that a shot too - thanks!
So, I’m scratching my head a bit. I followed all the steps we discussed - Static IP address on the Shield, Port forwarding to 32,400 both internal and external. Port forwarding to 32,400 w/in the router. I will maintain green for a few hours but will always revert to red. Frustrating. Any thoughts?
Definitely frustrating. Searched the forum for other posts with people using Orbi routers. Did not see anything similar.
When Plex says remote access is working, can you actually stream remotely? Wondering if you’re getting a false positive. If it does work, make sure it is not using Plex Relay. The Plex Dashboard should show the connection as Remote, not Indirect.
The log files might show something. The next time it fails, pull the log files (Settings → Troubleshooting), and upload them to the thread. They might show something.
The connection is definitely not indirect. I found the connection was indirect when I first inadvertently gave the router vs. the server a static IP address. Once I fixed the router back to DHCP, indirect went away. I seem to be switching between 32400 and 13103 which is the external port that UPnP shows. It will stay green as I rotate these back and forth. I had everything green with the external port set to 32400. I turned of UPnP and it failed immediately. So, I do need to keep the UPnP on.
Here are the logs - not quite sure what I’m looking for/at
com.plexapp.agents.fanarttv.log (14.4 KB)
com.plexapp.agents.htbackdrops.log (9.4 KB)
com.plexapp.agents.imdb.log (8.1 KB)
com.plexapp.agents.lastfm.log (9.8 KB)
com.plexapp.agents.localmedia.log (28.5 KB)
com.plexapp.agents.lyricfind.log (7.1 KB)
com.plexapp.agents.movieposterdb.log (7.0 KB)
com.plexapp.agents.none.log (17.0 KB)
com.plexapp.agents.opensubtitles.log (9.0 KB)
com.plexapp.agents.plexthememusic.log (7.2 KB)
com.plexapp.agents.themoviedb.log (123.5 KB)
com.plexapp.agents.thetvdb.log (8.9 KB)
com.plexapp.system.log (37.4 KB)
org.musicbrainz.agents.music.log (9.4 KB)
Plex Media Scanner Analysis.1.log (98.5 KB)
Plex Media Scanner Analysis.2.log (283.8 KB)
Plex Media Scanner Analysis.3.log (191.1 KB)
Plex Media Scanner Analysis.4.log (168.0 KB)
Plex Media Scanner Analysis.5.log (126.3 KB)
Plex Media Scanner Analysis.log (5.7 KB)
Plex Media Scanner Chapter Thumbnails.1.log (202.9 KB)
Plex Media Scanner Chapter Thumbnails.2.log (7.0 KB)
Plex Media Scanner Chapter Thumbnails.3.log (10.8 KB)
Plex Media Scanner Chapter Thumbnails.4.log (8.9 KB)
Plex Media Scanner Chapter Thumbnails.5.log (13.3 KB)
Plex Media Scanner Chapter Thumbnails.log (4.5 KB)
Plex Media Scanner Deep Analysis.1.log (7.0 KB)
Plex Media Scanner Deep Analysis.2.log (8.7 KB)
Plex Media Scanner Deep Analysis.3.log (8.0 KB)
Plex Media Scanner Deep Analysis.4.log (8.8 KB)
Plex Media Scanner Deep Analysis.5.log (9.6 KB)
Plex Media Scanner Deep Analysis.log (7.3 KB)
Plex Media Scanner Matcher.1.log (3.8 KB)
Plex Media Scanner Matcher.2.log (1.0 KB)
Plex Media Scanner Matcher.3.log (1.1 KB)
Plex Media Scanner Matcher.4.log (3.9 KB)
Plex Media Scanner Matcher.5.log (1.1 KB)
Plex Media Scanner Matcher.log (3.9 KB)
Plex Media Scanner.1.log (34.5 KB)
Plex Media Scanner.2.log (205.2 KB)
Plex Media Scanner.3.log (178.8 KB)
Plex Media Scanner.4.log (156.9 KB)
Plex Media Scanner.5.log (1.6 MB)
Plex Media Scanner.log (50.7 KB)
Plex Media Server.1.log (92.1 KB)
Plex Media Server.2.log (1.8 MB)
Plex Media Server.3.log (4.4 MB)
Plex Media Server.4.log (99.7 KB)
Plex Media Server.5.log (412.7 KB)
Plex Media Server.log (479.9 KB)
Plex Transcoder Statistics.1.log (29.1 KB)
Plex Transcoder Statistics.2.log (8.6 KB)
Plex Transcoder Statistics.3.log (4.4 KB)
Plex Transcoder Statistics.4.log (2.5 MB)
Plex Transcoder Statistics.5.log (92.2 KB)
Plex Transcoder Statistics.log (3.5 KB)
Plex Tuner Service.1.log (1.9 KB)
Plex Tuner Service.2.log (2.7 KB)
Plex Tuner Service.3.log (1.8 KB)
Plex Tuner Service.4.log (2.6 KB)
Plex Tuner Service.5.log (2.6 KB)
Plex Tuner Service.log (1.9 KB)
Thanks for the log files.
FYI, you can upload the entire ZIP file instead of each individual log file.
For remote access, the Plex Media Server.log has the info we’re after.
Plex is seeing a double-NAT, or router behind router, situation.
Jul 13, 2022 06:32:57.018 [11927] DEBUG - [EventSourceClient/pubsub/(redacted):443] MyPlex: reachability check - current mapping state: 'Mapped - Not Published'.
Jul 13, 2022 06:32:57.018 [11927] ERROR - [EventSourceClient/pubsub/(redacted):443] MyPlex: mapping failed due to potential double NAT configuration
Jul 13, 2022 06:32:57.018 [11927] DEBUG - [EventSourceClient/pubsub/(redacted):443] MyPlex: mapping state set to 'Mapped - Not Published (Double NAT)'.
Are you running a VPN on the Shield, the Orbi, or something else between the Shield and the Internet? VPNs and Plex generally don’t play well with each other. A VPN on your personal computer, phone, etc won’t matter as they don’t sit between the Shield and the Internet.
To what is the Orbi connected? Is that device also functioning as a router?
If you are in a double-NAT situation, it can be resolved by placing one of the routers in bridge mode. This disables routing and the NAT function on that device.
On some mesh network devices, disabling routing also hinders or disables the mesh capability. If this is the case with Orbi, then the other device would need to be placed in bridge mode.
If neither device can be placed in bridge mode, then you can use a double-port forward. The first device forwards to the Orbi, when then forwards to the Shield. It requires additional work to configure, but others have used it successfully.
Additional Information:
Hey, thanks for taking a look. I had no clue what I was looking at. I am running the RBR750. Connected to the RBR750 is an ARRIS SURFboard SB6141 DOCSIS 3.0 Cable Modem. I have never run a VPN and have nothing hardware or software between the router and the Shield other than a Gigabit switch. But I can’t imagine the Switch would cause a Double NAT scenario. I could connect the shield directly to the router and circumvent the switch. That’s the only conceivable variable I could foresee. I’ll go do that now.
Here’s what is happening:
Jul 12, 2022 21:57:30.573 [11882] DEBUG - * 6 eth0 (192.168.1.52) (00-00-00-00-00-00) (loopback: 0)
Jul 12, 2022 21:57:34.009 [11943] DEBUG - PublicAddressManager: got WAN IP 192.168.0.3 from router
I’m not sure why this is happening.
Suggestion: A network reboot.
Give the Plex Media Server 2 - 3 minutes to fully boot. Then check remote access status.
If remote access still is not working, pull a new set of Plex log files.
If Plex is logging the same messages, then there is probably an Orbi configuration problem or the cable modem is acting very strange, assigning a private instead of public IP address to the router.
FYI, the cable modem is easy to test. Connect a PC to its Ethernet port, pull up a command window, and issue the ipconfig command, c:\ipconfig. You should see a public IP address, 174.x.x.x. You will most likely need to power cycle the cable modem after connecting it to the PC. You’ll need to power cycle it again after reconnecting it to the router.
I connected the Shield directly to the back of the router. The Internet IP address shows this in the router settings -
Thanks for the update.
That looks like the cable modem is providing a 192.168.0.3 address to the Orbi.
It should provide a public IP address - 174.x.x.x.
Can you connect a PC directly to the cable modem to confirm? You could use the Shield if that’s easier, configure it for a dynamic instead of static address, then look in the Shield settings to see what address is assigned.
If the cable modem is handing out 192.168.0.x addresses, you will need to contact your ISP. Something is probably misconfigured on their end.
Is Charter/Spectrum your ISP (I did a reverse lookup on your public IP)?
I’ve the same ISP. I’m using their cable modem. It provides a public IP to my Asus router (or whatever I attach directly to the cable modem).
If your modem is supplying a private address, then it is either misconfigured (by Charter) or they’ve changed how they handle IP addressing in their network.
I’m using an Arris SBG6400 DOCSIS 3.0 Modem. I also have on hand an Arris SB8200 DOCSIS 3.1 modem I could switch out. I’d just have to register it with Spectrum. I noticed that the internal Netgear was throwing off another domain too, but thought it was something internal. I broke everything down this morning. Pulled the modem up first, then the router while the satellite is unpowered. Still showing the IP address for the router as 192.168.0.3. So, scratching my head. Getting ready to go reconnect my satellite.
Talk with Spectrum. Seems like something off with how they register your cable modem. It should provide a public IP address.
Reconnect the satellite. Does not seem to be a problem.
I switched out the Modem to the Faster Arris SB8200, DOCSIS 3.1 and am now getting these for my IP address for the Router/Gateway- The numbers/addresses now match my Public IP address in the Remote Access settings for plex. Gone are 192.168.0.3 and 192.168.0.1 -
Canyouseeme.org is working now too!!
Nice. Internet connection now working properly.
Plex remote access working as well?
Y-E-S…after all that, it seems as thought the Arris SB6141 modem was the weak link in the chain. I put my better modem, Arris SB8200, DOCSIS 3.1 in it’s place - fixed everything and I picked up another 100 mb/s in D/L speed. THANK YOU for all of your help!!!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
