Your server is signed in to Plex, but is not reachable from outside your network

Plex Media Server Remote Access
21

IPv4…
I’ve got IPv6 turned off in the router settings

22

One last thing we can try before i suggest a large :hammer:

  1. Turn off Remote Access
  2. Restart PMS
  3. Let it do its thing and be stable (about 5 minutes of whatever)
  4. Turn on Remote Access
  5. Let it go green.
  6. It may flash back to red but still should be open.
  7. Download the logs about 1 minute after Remote Access enabled.
23

as requested…
and thanks for all the help @ChuckPa

24

Thank you. I found it.

It’s throttled from all the attempts.

Jan 26, 2021 22:10:18.439 [0x7f92edfc5700] DEBUG - MyPlex: Published Mapping State response was 422

Let it sit there, as is, and see what it looks like in the morning.

25

I can do that… thanks again

26

Still not working this AM or this afternoon.

Verified by two devices outside my network that I share my server with… both going remote indirect.

27

I know there is a ton of consternation on the Plex forums currently regarding Remote Access suddenly breaking and flipping between connected and not connected. I ran into the same issue on my server.

After many many hours troubleshooting and rebuilding: the issue actually stemmed from the Denial of Service protection on my Asus AX-11000 (if you have that model it is a checkbox under the Firewall setting). The second I disabled that specific option, canyouseeme started reporting it could connect and Plex/Emby has had zero connection issues.

Important Note: that setting has been on since I purchased the router around a year ago. Plex only stopped working with remote access within the last 30 days. I have no idea what changed but thought id share the solution that worked for me.

Server OS:
Windows 10 Pro for Workstations
Plex Server Build:
1.21.2.3939
Router:
Asus GT-AX11000

28

Can either of the remote devices connect directly to your server?

Either by adding your public IP address into the client (SmartTV, mobile, etc) or pointing a browser at https://public_ip_address:32400/web/index.html.

29

Thanks… I actually have the firewall in the ASUS turned off monetarily to try and get this to work, so the DOS option isn’t available. But before the firewall was turned off I had played with setting DOS off and it didn’t help…

I’ve never had a problem with canyouseeme showing the port as closed… it’s always showed the port as open weither I set it up as Upnp or port fwd rules.

30

I’m trying to access https://public_ip_address:32400/web/index.html. on my cell and it’s not working.

First I got a certificate warning from safari but I can choose to accept it.
Then the plex logo comes up but it never connects to my server. .
It eventually just times out.

31

BTW… I have no problem accessing my Routers GUI from outside my network when I select the applicable settings and it setups the port forwarding for that port.

32

Still getting nowhere with this.

I tried giving the NAS a new manual IP address and made all the applicable changes regarding port forwarding… no dice.

Also tried to just set the router to allow DMZ for the NAS but again… no dice.

My neighbor has a pretty similar setup (NAS running plex, same ISP but different modem/router). We compared NAS settings and everything looks good.
Next plan is to bring my NAS over to their place and see if we cant get it working on there network. Maybe rule that out.

Getting a little frustrated here…

33

I’m not sure what else to try. It is like all the pieces work, but not the whole. Probably missing something simple, but danged if I know what it is.

Report back how it goes at the neighbor’s place.

34

Update… finally got it working.
After spending the morning trying out different things, it became obvious the problem was with my network. I did a factory reset of my main router and reset the modem and poof…It started working as UPNP… did a manual port FWD and it’s still kicking.
After the reset my ISP did assign me a new WAN IP… not sure if that did the trick.

I’ve slowly started adding items to my network afraid that one of them is going to bring the house down again. Only thing left is my attic router than runs in Asus’s AImesh (wired) but I think I need to reset it and just don’t feel like climbing to the attic.

Hopefully my success continues.

I did have an issue Friday with Plex deleting a tons of my TV shows from my NAS for whatever reason after I removed plex in an attempt to reinstall it. No rhyme or reason to it… some shows it didn’t touch, some shows it only deleted a season or two… some shows it deleted all the seasons. It only deleted the actual files but didn’t touch any folders. Lesson learned… don’t give Plex write access.

35

For anyone following alone… I added the Asus AImesh node (router) and the remote access is still up and running.

Not sure what caused the issues in the main router but whatever it was… seems to be fixed now.

Thanks for the help.

36

Plex port check 32400 with Dream Machine Pro “Not available outside your network”

I recently got a Dream Machine Pro early 2021 and upgraded to the latest firmware. I had Plex working with an Asus router before getting the new router. After setting the port forwarding rule for Plex on the Dream Machine I could not get the Plex port checker to say my Plex server was accessible on the internet, but it was working - I could use my Plex outside my network.
After seeing several posts on Ubiquiti and Plex forums, I thought I would share what fixed this for me.

My hardware:
Ubiquiti Dream Machine Pro running the latest firmware
Plex running on Windows 10 Pro.
Random 1GB switch between the Dream Machine and the Plex computer.

I tried the following (not in any particular order), which did NOT fix the issue:

  1. Rebooted the Dream machine after making the port forwarding rule.
  2. Added firewall rules to Dream Machine to allow Plex to talk to the internet (these were later removed completely).
  3. Downloaded the Plex server installer and did a “repair” of my software.
  4. Rebooted my Plex server.
  5. Made sure my Plex IP was static, and that was matching my port forwarding rule.
  6. Deleted any old “authorized devices” showing on my Plex account (I had 2 old Plex server versions still hanging on).
  7. I did NOT have a double NAT issue with my network.
  8. Disabled all Dream Machine network intrusion protection.
  9. PPnP is disabled on the Dream Machine by default, I did enable it and tried the port checker, then disabled PPnP.

Here is what DID fix this:

  1. Set the IP of Plex server to a static IP.
  2. Added the port forwarding rule to the Dream Machine, I used 32400.
  3. there are plenty of other articles about HOW to do that exactly.
  4. On my actual Plex server, I pulled up the web interface, then went to the Settings > General.
  5. you will see a section labeled “Server signed in as” and your account info.
  6. next to this, you will see “SIGN OUT”
  7. click the “SIGN OUT”
  8. that will then change to “Claim this server”, click that and let it finish
  9. Now you can go down to Settings > Remote Access
  10. Tick the box to “manually specify public port”
  11. Enter 32400 in the box, or whatever port you choose to use, matching your port forwarding rule.
  12. Plex should then check the internet and port connection, and should work.
  13. After several hours my Remote access still says “Fully Accessible outside your network”

Hope this article helps someone else with the same issues, and if my FIX section doesn’t resolve your issue feel free to check the other items I mentioned.

37

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