PR4100 - Remote access troubleshooting help - Fiber POE, ASUS Router

Plex Media Server Remote Access
1

Reposting here.

It appears I am one of the many Plex users having remote access issues. I have researched the issues extensively and tried numerous options to no avail. I am now appealing to the community for help.

Here is the setup:

Plex HW Server: WD PR4100

Firmware Up to date: 5.12.108

LAN IP : 192.168.50.70:32400

Plex Media Server: Version 1.22.3.4392

Manual Port Forwarding set for port 32400

Router: ASUS RT-AX58U

WAN IP: (Static) 139.xxx.xxx.xxx (Paid extra $10/month for static IP)

Port Forwarding set for: 192.168.50.70 Port 32400

ISP: 150/150 up/down through fiber POE device.

ISP Gateway IP: 65.207.XX.XX

Problem: Direct remote access not available outside my network (indirect only )

ISP states his gateway (65.207.X.X) is not blocking and that I have a static IP.

Here are relevant sections of my server logs:

May 10, 2021 08:08:26.391 [0x7fcb32598700] DEBUG - NAT: UPnP, public address is 139.xx.xx.xx

May 10, 2021 08:08:26.391 [0x7fcb32598700] DEBUG - PublicAddressManager: got WAN IP 139.xx.xx.xx from router

May 10, 2021 08:08:26.391 [0x7fcb32598700] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv

May 10, 2021 08:08:26.391 [0x7fcb32598700] DEBUG - HTTP requesting GET (WAN IP).plex.direct:32400/identity

May 10, 2021 08:08:26.396 [0x7fcb32598700] ERROR - Error issuing curl_easy_perform(handle): 7

May 10, 2021 08:08:26.396 [0x7fcb32598700] WARN - HTTP error requesting GET (WAN IP.plex.direct:32400/identity (7, Couldn’t connect to server) (Failed to connect to (WAN IP.plex.direct port 32400: Connection refused)

May 10, 2021 08:08:26.396 [0x7fcb32598700] DEBUG - MyPlex: mapping state set to ‘Mapped - Not Published’.

It looks like a Double NAT situation but my ISP is stating he is not blocking. Any help is appreciated.

2

From what I understood you set your external port also to 32400, right?
Plex is still trying to set up your remote access using UPnP because your skipped one step.

Go to Settings → Remote Access → Check Manually specify public port → Type 32400 there and Apply. Disable and Enabled your remote access back.

3

Tried this several times already but no luck.

1 Like
4

I should say it starts saying it’s working (green) but 10 seconds later goes red.

1 Like
5

Two things. Open your router wan status page and double-check if 139. Is there or another ip starting with 100.
Second, set your the DNS server on your nas to 8.8.8.8.

6

Appreciate you help.

WAN IP on Router says: 139.xx.xxx.xxx

Set DNS on NAS to 8.8.8.8

Restart NAS. Disable, Enable Remote access. Same issue - starts green and goes to red in 10 seconds.

7

Look up the IP address stored at plex.tv.

You’ll need your plex token. See Finding an authentication token / X-Plex-Token.

NOTE: Anybody with your Plex Token can gain access to your server. Never post your Plex Token publicly.

Go to: https://plex.tv/api/resources?X-Plex-Token=YOURTOKENHERE

You’ll see a page of XML info regarding your server(s) and client(s). In the section for your server, look for publicAddress.

Does it match your static IP address? According to your log files it does not.

If not, does it match your ISP’s addressing? 65.207.xx.xx, etc.

https://support.plex.tv/articles/206721658-using-plex-tv-resources-information-to-troubleshoot-app-connections/

8

The address stored at plex.tv does NOT match my static IP address 139.xx.xx.xx

It DOES match my ISP’s addressing 65.207.xx.xx

9

What is that?
It might be already a “router” type of device. If you are adding your own router after it, your server is then in a double-NAT situation.

10

So apparently your router is translating your LAN addresses to 139. but then your router gateway is mistakenly making a second translation to its own IP, resulting in double NAT, hence the Indirect Playing (Plex Relay).
Access your NAS using SSH and run this command curl ifconfig.me. If the result is 65. then you should give your ISP a call.

11

The curl ifconfig.me reported 65.X NOT 139.X so it is definitely the ISP gateway. Working with my ISP provider is a challenging ordeal. It is a small Mom & Pop operation in a rural area. When I originally contacted him about the issue and asked if he could do port forwarding from his end he immediately offered to sell me a static IP address that would “fix the issue”. It has not. He has since been unresponsive with any further request for support.

BTW - This is the gizmo my router connects to (ufiber-loco): UFiber loco GPON CPE – Ubiquiti Inc.

12

Do you have access to the CPE?
Is it on Bridge mode?
What mode is your router on? DHCP, PPoE?
What are the first three hops of the command traceroute 8.8.8.8 (you can show just the first octet)

13

Do you have access to the CPE? NO
Is it on Bridge mode? Unknown
What mode is your router on? DHCP, PPoE? DHCP, PPoE is disabled
What are the first three hops of the command traceroute:
1 192.X
2 139.X
3 10.X
4 65.X

Thanks for your help.

14

I should say I’m not sure if I have access to the CPE or not.

15

That IP 10 in between the valid ones :unamused:
Connect your pc directly to the lan of your CPE . Does your pc get an IP? Are you able to navigate on the internet?

16

If the CPE does not provide an IP address to your PC, then try power cycling it. You’ll need to do the same when re-attaching your router.

Some CPE does not recognize when new equipment is attached (many cable modems behave this way). They need to be power cycled to recognize the new MAC address and provide an IP address.

17

Need to pick up a USB Ethernet dongle tomorrow. Will try then and let you know.

Thanks,

18

Also, got this cryptic one sentence email from my ISP:

"There is nothing on the router at 65.xx.xx.xx that would be blocking port number 32400"

19

Yeah, I actually believe them, but the problem is that the internet “see” you as 65., not as 139. like it was supposed to be. They should just announce a route to your IP without translating it.
But let’s wait for your tests of tomorrow.

20

Update:

  • Connect laptop directly to the CPE fiber gizmo . Laptop DOES get an IP and am able to navigate on the internet.

  • Google search of whats my ip = 65.X.X.X

  • traceroute =

1 139.x.x.x
2 10.x.x.x
3 65.x.x.x

Also, the ISP confirmed the CPE fiber gizmo (ufiber-loco) is in “Router” mode.