Cannot access local server after allowing remote access

Plex Media Server
,
1

I use a Windows 10 PC, and have recently purchased a Synology NAS DS218+, and I cannot access PMS locally after allowing remote access.

So, the problem appears like this. I have installed PMS 1.19.1.2701 on the NAS, i have set it up for movies, tv shows and home videos. All this while i am logged in to the PMS using Google Chrome going through the local ip adress and port 32400. I have, at this point, not enabled remote access (i unticked the little box during setup). However, when i do allow remote access, a port forwarding rule is automatically created:

Plex Media Server

Protocol: TCP

External Host -

Internal Host: 192.168.0.xxx

External Port: 15813

Internal Port: 32400

Options: UPnP Rule

After this, I can no longer access PMS through internalip:32400/web. I also cannot change the port forwarding rule without factory resetting my router (a Sagemcom F@ST 3890V3).

All that happens is that the error message ERR_CONNECTION_TIMED_OUT shows up on screen, together with a recommendation to check my connection, my proxy and my firewall. The connection and the firewall are both working OK, so it must be the proxy? Or is it something else?

Do I have to fake a local connection to the NAS via a SSH tunnel? That doesn’t seem like the way to go. I suspect the port forwarding rule is the problem, but I am no expert. I don’t know how to fix this, your help would be appreciated.

Server Version#: PMS 1.19.1.2701
Player Version#: web interface, DS218+

3

OK, I followed your instructions, and i got no access. Couldn’t even log in. Error connection timed out… I have attached my log.zip.
Logs (1).zip (552.1 KB)

Edit: I might add that now i cannot access PMS using remote either…

5

No such files exist in that folder…

7

It is 192.168.0.122:32400/web

9

Of course, here you are
Logs (2).zip (567.3 KB)

11

Re 4, when you say Open Plex, do you mean i type myprivateip:32400/web and hit enter?
Re 5, this is if step 4 leads to a sign in prompt, right?

Well, i did the above, and got the err_connection_timed_out again…

I have also checked the physical connections to the NAS, and switched cable, it doesn’t seem to have any effect.

13

I can access my DSM via nasip:5000 no problem at all. I have not used EZ-Internet at all. Should I?

15

I can sign in for sure, but i don’t see the server. Well, I see it, but am not granted access to it. The wheels just keep spinning.

17

OK, I will do that. All I know is that the problem occurs the very moment remote access is enabled, and an automatic port forwarding rule is created in my router. It works just fine if i don’t enable it. It may be the router and/or my ISP, but i’m guessing.

Thanks very much for the help, now i await the big gun i guess…

19

I was just about to reset it actually. I’m also thinking about disabling UPnP IGD, so it won’t auto-forward all of a sudden. Is that a good idea?

21

Right, i’ll disable it then. And Chrome, Firefox and MS Edge have all given the same results. I’ll post the result here.

22

OK, upnp igd is now disabled in the router, so at least nothing will happen without my express actions. I tried to forward the port manually to get remote access that way, but everytime with the same result, total loss of local access to the server. Even if the port forwarding should have no relevance to this particular problem, it is quite an interesting connection i think.

I will run Plex without remote access for the time being.

24

Yes, while on the same local network. No vpn. No access from outside my LAN.

26

Here’s a screenshot from a popular app - let me know if you need more information.

28

That’s my mobile phone.

30

Yes, i’ll talk to my ISP. I have considered bridging the router, since i have an old TP Link Archer C7 that’s just lying in a drawer. I’ll let you know how it goes.

31

Hello, here’s an update regarding my problems with the Sagemcom F@ST 3890V3 router. I had a two hour phone conversation with my ISP tech support, which started with attempts to solve the port forwarding problem, and ended with me bridging the router to my trusty old TP Link Archer C7. There is definitely something wrong with the firmware to the Sagemcom, as it seems to block the very ports it is supposed to forward, thus making all access to the router impossible. The bridging wasn’t easy either. Several attempts failed (both by me and the support guy). However, after having factory reset both the Sagemcom and the TP Link routers, and by manually shutting down the wifi function on the Sagemcom, i managed to bridge the router. I then had to disconnect all my wifi devices, and wait several hours, before a new wan ip was distributed to me. Then everything worked just fine.

Thanks for your help and guidance trumpy81!

TLDR: Flawed Sagemcom router couldn’t forward ports, and couldn’t be bridged without taking several extra undocumented actions (unknown to my ISP tech support guy, but discovered through trial and error). Eventually it worked and my Archer C7 is now taken out of retirement, to serve once again.

33

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