dude, you fixed it!
everything is working as it should. thank you so very much for your help, i never would have solved this by myself.
dude, you fixed it!
You’re welcome, glad it’s working for you!

Hello tom80H, thank you again for your support!
Took me some time to go through the troubleshooting options and sadly did not identify anything I would have done wrong…
Made this schema of my setup. VPN and Firewalls are deactivated, and one interesting thing to mention is that there is a connection test in the remote access of the Synology, and that one shows “fail” for all ports that are supposed to be open.
Do not know where to look anymore…
Ignore that but test it from outside your home network (e.g. using a service like canyouseeme.org).
Your schema looks conclusive but the pic resolution doesn’t really allow reading any of the technical details in the screenshots (port forwarding, connection test [although probably neglectable], Plex status)
Woooo boy, Viasat.
I’ll be surprised if they don’t try to block Plex, at least the default port :32400.
I’m a little bit confused about the Port range forwarding screenshot. It’s blurry but appears to have a different IP address in it.
(Only TCP needs to be forwarded.)
By the way, on the Modem, there are 3 different options for ports management:
“Single port forwarding” - “Port range forwarding” - “Port range triggering”
I use “Port range forwarding”. Guess it is ok?
The worst thing in all this is that, besides watching a film from time to time from a hotel room somewhere, what I really want to do is use the Plex module in the Sonos app.
For whatever reason, while Sonos itself will need the local wifi only, the Plex add-in seems to require internet to give me access to the music stored locally on my NAS.
The list of media will appear only after requesting multiple times, then the playback will be interrupted very often, which looks very much as if the Relay function was being used.
Had it working properly and enjoyed the much better interface of Plex over the native Sonos one when I was living in an area with a decent internet.
Hi Volts, thank you for joining the conversation
Viasat
well, yes… Living in Austria (not Australia) for now and I am now experimenting with satellite internet after unsuccesful attempts in all the other alternatives. For this part of the world the company behind is SkyDSL Europe but they seem to do all the bad things I read about Viasat on other forums. Most annoying one is that they indeed seem to be using a lot of filtering on my “unlimited” access. Sometimes, a simple search in Google waits forever while the same on Duckduckgo gives an acceptable response time (and the simultaneous Google request on my fallback lousy LTE connection is then the fastest)…
If anyone reading this is contemplating Viasat right now : stay away.
But thanks for the tip. Will try to enable a few random ports and see if it brings me any further…
I got something similar setup like Gabske.
WAN- ISP Router(fiber “modem”) connect to my ye olde netgear Router that is hooked up to my switch acting as the “router” for all my LAN connections.
ISP modem is on 10. IP range , everything on the LAN router is on 192.168. IP range.
(i prefer to not change any of that, one reason is my ISP moden can not be configured or even connected to locally, it must be via ISP’s “home page”)
I added a portforward on ISP modem with IP of PMS on default port, and Plex actually think this is fine.
(as you can see on screenshot)
BUT i cant connect and “canyouseeme” cant see me.
As i understood from comments further up i need to Port Forwad on my LAN router aswell? And this is where i am stuck.
(blank part is WAN IP)
The modem’s “WAN IP address” is a private network. That means your ISP isn’t assigning a publicly routable IP4v address but placed you in a “CGNAT”. That means Plex has no means to connect to your server from outside your home network.
As the ISP is assigning the WAN IP address to your router, configuring a port forward on the router won’t be enough. Your best shot is asking your ISP if they can assign you a publicly routable IPv4 address. Some ISPs will consider this. Most of those will try to sell you a static IP address – usually for a steep price. You don’t need a static IP address! Although with some ISPs that’s the only option to get a publicly routable IPv4 address… so that’ll be up to you…
The Plex server is in a double-NAT situation. Both the ISP router and your Netgear router are performing network address translation.
One solution is to eliminate one of the NAT processes. You could ask your ISP to place their router in “modem mode.” It will provide one public address to the Netgear router, which then provided 192.168.x.x address to all devices. Alternately, you can run the Netgear in Access Point mode, disabling its NAT processes. Everything on your network will then have a 10.x.x.x address (which you said you do not want to do).
A second solution is a double port forward.
The Netgear router will need a fixed 10.x.x.x address, either statically configured on the Netgear itself or assigned by the ISP router.
The Plex server will need a fixed 192.168.x.x address, either statically configured on the server or assigned by the Netgear router.
Im pretty sure there is no CGAT going on here. My IP changes from time to, though not as frequent as it used a few years ago. (Also a tracert on my WAN ip show the two expected hop. 1: the LAN router, 2: ISP (the WAN IP)
Ok, that makes sense.
I really don’t not want to rely on my ISP modem for anything LAN, since its impossible to use it when internet is down. (Idiotic to say it mildly)
Edit: Canyousee can now see me.
Edit2: Ok, tested away from wifi and everything seems to be working as intended. Thanks @FordGuy61
I found the “indirect” only appears when I assign a static IP address. Once I go back to DHCP, “indirect” goes away.
I have the same issue and tries all suggested fixes by plex, and cannot get it to work. Worked fine for years and now does not work.
Any changes on your ISPs side?
To what outcome have you troubleshot your issue? – users won’t be able to help based on “it’s not working and I tried everything”
Hi Tom80H…
I talked to ISP a couple months ago about any changes they ay have made to affect this, and they said no changes that would affect me regarding being to access PLEX outside my network were made.
.
Since then I have tried many suggestions about changing things in the router (ASUS RT AC68U) put forward by others in this thread, and still cannot get remote access connection to last more than a couple of minutes before turning red again.
tried changing the external port to several different ones in the 40,000 range (40530, 42350,( as well as 10689 and none worked.
I tried GRC.com “shields up” to check those ports and they are all in stealth mode.
I would think that I should be able to open specific ports but I cannot find out how to do that.
I tried several ports on canyouseeme.org and none of them worked either as they just timed out.
As I mentioned, this worked for years and suddenly stopped several months ago.
I am running the most recent PLEX media server on Synology DS415+ and all media files are on the same NAS. NAS goes to switch —> router—>Modem (ISP supplied). Speed is 300Mbs and only one user (me) signs onto plex remotely currently.
if anyone has any other suggestions or has been able to get the remote access to work, would sure appreciate knowing how you did it.
Doesn’t anyone from PLEX development or support monitor these forums? Would be nice if they could chime in on this issue.
thanks for you response. Much appreciated
Garry
Your port forward being not visible from outside your home network strongly implies there’s an issue somewhere between “the internet” (incl. your ISP) and (including) your router configuration. Could be your ISP blocking certain ports, could be a bad port forward. If you cannot see a port forward from outside your home network, this means at this stage it’s no issue anywhere within Plex.
Have you checked the simple things from the troubleshooting guide?
As you mention your network setup… can you verify your ISP modem is in bridge mode OR your port forward is actually configured on that modem, so “the outside” has a chance to even see it?
" * does your router actually have a routable public IPv4 address (no private IP address ranges, no IPv6-only setup, no GCNAT…)?"
not sure I understand what you are asking here. This is what i see in my router config :virtual Server /Port Forwarding Tab (note that the 123 in the internal IP address here was changed for this screen shot only…it is not 123 in reality but is a fixed number.
Dont know what you mean with the IPV4, IPV6 and GCNAT
- do the public IP address visible on your router and the one identified by Plex match?
I assume you mean the external Port? and yes it matches… see screen shot following
the specified external port 42350 matches what’s in PLEX:
- can you get a port forward to be seen if you’re using a super-standard port (e.g. 80, 8080 and the likes)?
Seen? where?
on canyouseeme.org, if I put in port 80 I get:

using 8080 there connection timed out.
does this help?
thanks for your assistance. Most appreciated.
Is 70.68.224.122 the IP address you see as WAN IP address on your router and as public IP on the Plex remote access settings page?
in plex… yes…

s
70.68.224.122the IP address you see as WAN IP address on your router…
I don’t see this address anywhere in the WAN on the router;
Note that in the WAN internet Connection tab there is a WAN Connection type which is set to Automatic but there is a drop down that shows that there is a place to put a static IP. Is this where it could be set to the 70.68.224.122 if this is needed?
I checked through all other tabs and there is no other place that this IP address or any other is
Network Map. Internet Status & WAN IP listed at top.