This has to be a joke, i’m getting real tired of getting the server up and running just to be hit in the face come the next update… I have the same issue that most seem to be having right now, the server is “Not available outside your network”, and not one single thread have had the solution for me. And honestly i’m about done with this… Call me lazy or whatever, but i really don’t want to get a degree in IT(whatever) just to be able to stream stuff on my home network.
With that said, anyone have any tips for a simple NAS solution to streaming movies/series on a home network. Been looking around but i thought you guys probably have some ideas. Synology DS218play is the one i’m leaning towards atm.
I’m done with plex, I’m done having to spend more time on this piece of ----- “server” then i do setting up and maintaining game servers.
Same thing here, everything was working fine until latest update, Remote Access pemanently shows " Not available outside your network".
I’m done with Plex.
Is there an ETA on 1.14.0.5468? I’m also running into some very strange/inconsistent remote access issues, where it will work for awhile, then randomly drop and not work again, and I honestly don’t know if it’s Plex, my network, or what… I’m leaning toward it being a Plex issue seeing as I had a solid/fast direct connection working remotely for 2 hours yesterday, and haven’t gotten it to work since…
id like to “third” this as well for inconsistent remote issues. usually 3 or 4 reboots will fix the issue… im running server 2012 r2 on a dell t610 with an Asus ac88u
I don’t know how you expect me to investigate from just making a statement.
If you feel there is still reliability issue after upgrading to beta 1.14.0.5468 which only came out yesterday, please provide logs and information as to what the issue was and when.
Have you needed 3 or 4 reboots after upgrading to 1.14.0.5468 ?
It could be soon. I have no information as to when it becomes public. You could provide logs of your issue and can check then if it would be fixed by the 2nd item on my list of fixes in 1.14.0.5468
As you have identified, you have a Double NAT due to there being a router servicing your apartment block
With double nat where you have no control of the two routers, it would be impossible to get to work
This shows the 2 different WAN IPs detected
Nov 22, 2018 17:05:13.965 [9148] DEBUG - PublicAddressManager: Obtaining public IP.
Nov 22, 2018 17:05:14.183 [9148] DEBUG - PublicAddressManager: Got public IP from http://plex.tv: 66.xxx.xxx.xxx
Nov 22, 2018 17:05:17.490 [9148] DEBUG - NAT: UPnP, public address is 10.105.101.221
Nov 22, 2018 17:05:17.491 [9148] DEBUG - PublicAddressManager: got WAN IP 10.105.101.221 from router
Nov 22, 2018 17:05:17.491 [9148] WARN - PublicAddressManager: WAN IP is a private IP address
Nov 22, 2018 17:05:18.625 [9140] ERROR - MyPlex: mapping failed due to potential double NAT configuration
So your external WAN IP is 66.xx.xx.xx but your router sees it as 10.105.101.221 which must be the IP allocated by the building router, The 10.105.101.221 is a Private Network IP
With double nat you may be able to cascade a port forward through but you would need control of both routers or cooperation from the other router manager
For example, say you decide to have public port 32501 as the port for Plex Media Server externally. Yyou would get Apartment Block Router manager to make sure the allocated IP 10.105.101.221 gets fixed (eg DHCP Reserved for your router Mac Address) and does not change and in that apartment block router they would forward public port 32501 to your router on 10.105.101.221 as port 32501, Then in your router you forward public wan port 32501 to local private 32400 and pass it to the Local IP of the server. Again this would need to fixed = by DHCP Reservation. You specify 32501 as the public port in the server settings
