Remote Access continues to report "Not available outside your network"

Plex Media Server Remote Access
1

Server Version#: 1.19.5.3112
Player Version#: 4.34.3

Hi All,

I feel that I have exhausted my options (existing posts and google-fu) and still have a lingering issue around remote access for my setup. There are a couple posts that have similar issues as mine but I didn’t want to simply highjack their threads with a “Me Too” comment in the event that I am somehow missing something in my setup.

Details:

I am running Plex via Docker that is then setup to be accessed via Traefik over 80/443 at https://plex.example.duckdns.org. My proxy is setup correctly as I have zero issues accessing Plex directly from a browser and can successfully authenticate and consume media remotely. The issue comes in when attempting to access the server via the Plex iOS app remotely.

Configuration/Settings:

  • Traefik accepts traffic on 443 and passes it to Plex on 32400

  • Traefik only accepts TLS 1.2 and 1.3

  • Enabled “Remote Access” and manually set external port to 443

  • Secure connections are set to “Preferred”

  • Disabled weak TLS versions

  • Disabled Relay

  • Custom server access URL’s set to https://plex.example.duckdns.org:443,https://192.168.4.46:32400

Troubleshooting:

  1. I can manually use the “Retry” button under “Remote Access” and it will show as Green for a few seconds and then go away again.

  2. If make 32400 public and bypass Traefik, it works fine.

  3. If I make 32400 public through Traefik, it works fine.

  4. I checked my servers in the Plex.tv xml and the URL’s look good and resolve to the correct IP’s via nslookup.

  5. Logs indicate that the connection is not getting published if I am reading them correctly.

Aug 18, 2020 15:10:47.430 [0x7fb4637fe700] DEBUG - MyPlex: async reachability check - current mapped state: 'Mapped - Publishing'.

Aug 18, 2020 15:10:47.431 [0x7fb4d679e700] DEBUG - Completed: [192.168.4.27:51561] 200 PUT /myplex/refreshReachability (7 live) TLS GZIP 0ms 274 bytes (pipelined: 52)

Aug 18, 2020 15:10:47.924 [0x7fb4477fe700] DEBUG - HTTP 200 response from PUT https://plex.tv/devices/b6d7dc82983ae8d4d0f952c8ac44957d710277eb?Connection[][uri]=https://plex.example.duckdns.org:443&Connection[][uri]=https://192.168.4.46:32400&Connection[][uri]=http://172.18.0.5:32400&httpsEnabled=1&httpsRequired=0&dnsRebindingProtection=0&natLoopbackSupported=0&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx

Aug 18, 2020 15:10:47.931 [0x7fb4d6f9f700] DEBUG - EventSource: Got event [data] '<Message address="71.71.228.213" port="443" asyncIdentifier="323c1c5a-ff3c-4d23-ab8e-50974a058a11" connectivity="0" command="notifyConnectivity"/>'

Aug 18, 2020 15:10:47.931 [0x7fb4d6f9f700] DEBUG - PubSub: Got notified of reachability for async identifier 323c1c5a-ff3c-4d23-ab8e-50974a058a11: 0 for 71.71.228.213:443 (responded in 508 ms)

Aug 18, 2020 15:10:47.931 [0x7fb4d6f9f700] DEBUG - MyPlex: reachability check - current mapping state: 'Mapped - Publishing'.

Aug 18, 2020 15:10:47.931 [0x7fb4d6f9f700] DEBUG - MyPlex: mapping state set to 'Mapped - Not Published (Not Reachable)'.

With all that said, have I missed something in my setup or is there an issue with remote access that is affecting what seems like a large number of people.

Thanks in advance,

2

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