Server Version#: 1.43.1.10611-1e34174b1
Player Version#: 4.159.0
Hello,
I recently changed my network configuration and now cannot find my server in the Plex hosted version (https://app.plex.tv/desktop/), while it appears and works fine in the bundled version (http://192.168.1.47:32400/web).
What I changed:
Set my ISP modem/router to bridge mode, going into a Ubiquiti EdgeRouter-X, which feeds ethernet to my Netgear Readynas RN-212, with static IP).
What works:
- Plex server & libraries load via local IP (http://192.168.1.47:32400/web)
- Apple TVs and Plex iOS app connected locally
What does not work:
- Plex server not found when accessing via public IP (even from within my LAN)
- Plex server and libraries not found when accessing https://app.plex.tv/desktop/
I have followed all the steps in the Remote Access Troubleshooting guide (https://support.plex.tv/articles/200931138-troubleshooting-remote-access/).
My remote access shows green constantly, with matching public IP to my router IP.
I have manually specified port 32400, forwarded it in Edgerouter, and when using a port checking tool, it is open.
I have also tried enabling dnsmasq in the Edgerouter, and adding “rebind-domain-ok=/plex.direct/” to the DNS forwarding rules.
From my NAS which hosts Plex, if I run nslookup plex.direct, I get back:
Server: 9.9.9.9
Address 1: 9.9.9.9 dns9.quad9.net
Name: plex.direct
Address 1: 0.0.0.0
However, after looking through the most recent Plex Media Server.log, I found these errors:
Apr 20, 2026 11:34:08.830 [2773418864] ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>
<errors>
<error code="1003" message="API rate limit exceeded" status="429"/>
</errors>
Apr 20, 2026 11:34:16.568 [2771309424] WARN - NAT: PMP, got an error: Not Supported by gateway.
Apr 20, 2026 11:34:16.569 [2824573808] WARN - [HttpClient/HCl#62] HTTP error requesting GET https://97-118-xxx-xxx.{masked-data}.plex.direct:32400/identity (7, Couldn't connect to server) (Failed to connect to 97-118-xxx-xxx.{masked-data}.plex.direct port 32400 after 0 ms: Couldn't connect to server)
The first error would suggest that my certificate is expired and cannot be renewed. I checked the PMS Cache folder, it is owned by admin and has 775 permissions. I don’t see any cert-v2.p12 file in Cache.
Could an admin/mod please check on the status of my cert and if needed, renew it? @OttoKerner
As for the 2nd error, I haven’t found much info on it, so any clarification would be appreciated.
And the 3rd error, about failing to connect to plex.direct, would suggest that I am potentially having issues with DNS rebinding protection; But if I am able to ping and nslookup plex.direct, would DNS rebinding actually be at fault?
Also, when I call https://plex.tv/api/resources?, I get back this for my server:
<Device name="PLEX" product="Plex Media Server" productVersion="1.43.1.10611-1e34174b1" platform="Linux" platformVersion="ReadyNAS OS 6.10.9" device="ReadyNAS 212" clientIdentifier="{masked-data}" createdAt="1776380222" lastSeenAt="1776640319" provides="server" owned="1" accessToken="{masked-data}" searchEnabled="true" publicAddress="97.118.xxx.xxx" httpsRequired="0" synced="0" relay="1" dnsRebindingProtection="0" natLoopbackSupported="0" publicAddressMatches="1" presence="1">
<Connection protocol="http" address="192.168.1.47" port="32400" uri="http://192.168.1.47:32400" local="1"/>
<Connection protocol="http" address="97.118.xxx.xxx" port="32400" uri="http://97.118.xxx.xxx:32400" local="0"/>
</Device>
I see that dnsRebindingProtection=“0” (false). So does this, along with my nslookup test indicate that I am having a DNS rebinding issue, or something else?
Any help or suggestions that anyone can provide would be greatly appreciated! Have been troubleshooting this for a few days now…
Thank you,
Scott
