Remote Access stops working after a few hours

Plex Media Server Remote Access
,
1

Server Version#: 1.20.4.3517
Player Version#: 1.22.0.1421-be6a7c42

I’ve been running my plex server on my RasPi4 docker image for a couple months without any issues, but recently the remote access hasn’t been working correctly; it will refuse connections from outside my network and I have to restart the whole system in order for it to work again, and it only works for 4 or 5 hours, however the status in Settings -> Remote Access always marks Fully Accessible.

I do have port forwarding in my modem and UPnP on a separate router, but after playing with the settings I couldn’t find the solution. Any ideas?

2

Also, how can I get your attention?

3

Please never rely on UPnP. Just configure port forwarding manually and disable UPnP. What are your port forwarding rules? Do you have double NAT, a VPN or some other special network configuration? Please also post server logs.

4

Thanks for your suggestion @drmagoo. I have disabled UPnP and restarted the system, so far it looks like it’s working, but I’d like to keep it running for a few hours and see how it is behaving. If the connection breaks again I will attach the logs, if not, I will just let you know how it goes.

5

At some point during the night the remote access stopped working. I am sure that it worked for at least one hour last night.
I have my modem port forwarding to my router, and the router port forwarding to my RasPi, UPnP is disabled.
As promised, I’m uploading the logs.

(File removed)

6

what’s more, last night (when it was working) the remote access status was “not available outside your network”; now that I cannot access it shows “Fully Accessible”

tempsnip
tempsnip1023×444 310 KB

Screenshot_2020-11-15-09-25-30-836_com.plexapp.android
Screenshot_2020-11-15-09-25-30-836_com.plexapp.android500×1000 62.6 KB

7 
Nov 08, 2020 13:10:38.214 [0xb13fe430] ERROR - MyPlex: mapping failed due to potential double NAT configuration
Nov 08, 2020 13:10:39.672 [0xb253d430] WARN - PublicAddressManager: WAN IP is a private IP address

Similar log entries have also been written today. So please tell us more about your network configuration. Do you chain multiple routers behind each other or do you use a VPN software?

Please also disable verbose logging.

8

I have a Technicolor modem/router provided by my ISP, behind that an Asus Router, which is my point of access for all of my devices home. No VPN software is being used whatsoever.

I suspect that the root cause might be the Modem, it was changed by the ISP a couple of weeks ago and that’s when the problems started, before that it had been running for months without an issue with the same configuration as now.

I believe the modem might have a double NAT issue, given that the modem WAN IP address is different than the one I get from whatsmyip.com

9

That’s it. You have two options:

(1) Set your Technicolor modem into bridge mode, if that’s possible. Please ask your ISP.

(2) Also configure port forwarding in your Technicolor router, so that it points to the IP address of your Asus router and the port you have configured there.

10

I’ve had this configuration since the very beginning. What troubles me is that is works for a couple of hours and then stops.

I’ll see what I can do about the bridge mode for the Technicolor modem

11

In theory, you could also just disable NAT on your ASUS router, i.e. connect a LAN port, not the WAN port of your ASUS, to your Technicolor and configure the static IPs and DHCP servers accordingly (e.g. disable the DHCP server on your Technicolor and let the Asus handle most things). I used a similar setup until recently and it was rock stable.

There are really many options to handle your situation, not just the two I have mentioned above. In the end, you have to get rid of the double NAT. Good luck :slightly_smiling_face:

12

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