thank you.
Summary
What service do you have? Coax (cable), Fiber ?, Telco?
DSL connection from a local telco
How many modem/routers do you have chained together?
I tried with the combined modem/router from the ISP (draytek vigor thing)
and I tried with a DSL bridge that is connected directly into a LAN port of my QNAP. PFsense runs there, doing PPPoE with the ISP. Both don’t play nice.
Here is a pfsense Firewall / NAT / Port Forward rule
I tried with 32400 and 32407, both look good. Also seen in logs. (it arrives at the server)
firewall session/state:
I do see this after a while.. IP .254 is the pfsense. relevant? or just session cleanup?
Sep 28, 2025 07:47:51.763 [139737185823544] Verbose — We didn't receive any data from 192.168.42.254:45760 in time, dropping connection.
Sep 28, 2025 07:47:52.179 [139737185823544] Verbose — We didn't receive any data from 192.168.42.254:42526 in time, dropping connection.
Sep 28, 2025 07:47:52.182 [139737185823544] Verbose — Didn't receive a request from 192.168.42.254:42526: End of file
Sep 28, 2025 07:47:52.191 [139737185823544] Verbose — We didn't receive any data from 192.168.42.254:22382 in time, dropping connection.
Sep 28, 2025 07:47:52.194 [139737185823544] Verbose — Didn't receive a request from 192.168.42.254:22382: End of file
Sep 28, 2025 07:47:53.057 [139737185823544] Verbose — WebSocket: processed 1 frame(s)
Sep 28, 2025 07:47:54.764 [139737187932984] Verbose — Didn't receive a request from 192.168.42.254:45760: stream truncated
Sep 28, 2025 07:47:57.093 [139737187932984] Verbose — We didn't receive any data from 192.168.42.38:41584 in time, dropping connection.
Sep 28, 2025 07:47:57.128 [139737187932984] Verbose — Didn't receive a request from 192.168.42.38:41584: End of file
talking to plex.tv
works.
a******@echobase:~$ curl plex.tv
<html>
<head><title>308 Permanent Redirect</title></head>
<body>
<center><h1>308 Permanent Redirect</h1></center>
<hr><center>nginx</center>
</body>
</html>
so.. either the server is borken or my ISP is doing black magic stuff that is evil. I am running a pi-hole with OpenDNS as upstream. Also I force all other LAN clients there, if they try to bypass it. (via the pfsense).. and I disallow things like quic or DoH towards any of the big DNS servers… does plex need to talk to them directly?
DNS record [plex.direct].plex.direct looks good and resolves to my public IP.
andreas@echobase:~$ nslookup 77-161-[REDACTED].f97889[REDACTED]219192.plex.direct
Server: 192.168.42.204
Address: 192.168.42.204#53
Non-authoritative answer:
Name: 77-161-[REDACTED]f97889e[REDACTED]19192.plex.direct
Address: 77.161.[REDACTED]
I will try one more thing, using the ISP’s DNS servers. But then I am out of options.
EDIT: no joy. Everything is now “default” as the ISP wishes it.
the thing that keeps popping up is this IP: 178.79.145.139 (linode/akamai) - sure that is not one of yours? then it’s maybe a web firewall / honeypot of my ISP?
Sep 28, 2025 08:32:21.591 [139737187932984] Debug — [EventSourceClient/pubsub/178.79.145.139:443] MyPlex: reachability check - current mapping state: 'Mapped - Publishing'.
Sep 28, 2025 08:32:21.591 [139737187932984] Debug — [EventSourceClient/pubsub/178.79.145.139:443] MyPlex: mapping state set to 'Mapped - Not Published (Not Reachable)'.
The NAS was updated on the 23rd. but my kid tells me it stopped working on 20 sept already (when he wanted to watch something) - (I did reboot the box, no joy) - there was, however, a plex update… can this be related?
I am in the log directory of the QNAP but I can’t find anything useful there.. any pointers what to look for?
can I downgrade plex to test? is that an option?
or should I just blame my ISP? or plex? 
I mean:
[Req#cdac] MyPlex: Sending Server Info to myPlex (user=[REDACTED], ip=77.161.[REDACTED], port=32407)
[Req#cdac] MyPlex: Got response for 630137[REDACTED]174f4c03 ~ registered 77.161.[REDACTED]:32407
EDIT2: the server seems to be a DNS server. name: pubsub09.pop.lhr.plex.bz
ndreas@echobase:~$ nmap 178.79.145.139
Starting Nmap 7.97 ( https://nmap.org ) at 2025-09-28 08:38 +0200
Nmap scan report for pubsub09.pop.lhr.plex.bz (178.79.145.139)
Host is up (0.016s latency).
Not shown: 997 filtered tcp ports (no-response)
PORT STATE SERVICE
53/tcp open domain
80/tcp open http
443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 5.40 seconds
andreas@echobase:~$ nslookup
> server 178.79.145.139
Default server: 178.79.145.139
Address: 178.79.145.139#53
> plex.tv
Server: 178.79.145.139
Address: 178.79.145.139#53
Non-authoritative answer:
Name: plex.tv
Address: 34.254.54.72
Name: plex.tv
Address: 34.254.245.199
Name: plex.tv
Address: 54.76.243.238
Name: plex.tv
Address: 3.248.163.211
> 77-161-[REDACTED]19192.plex.direct
Server: 178.79.145.139
Address: 178.79.145.139#53
Non-authoritative answer:
Name: 77-161-[REDACTED]5219192.plex.direct
Address: 77.161.[REDACTED]
>
EDIT 3: I give up
all the other services on my NAS work.. I even re-built the firewall and NAT rules, including PnP
yet.. after a minute >> unreachable. 
Sep 28, 2025 15:03:25.983 [139737185823544] Debug — [EventSourceClient/pubsub/139.162.215.242:443] EventSource: Got event [data] '<Message address="77.161.[REDACTED]" port="32407" asyncIdentifier="a920628d-a17a-40d2-aa1c-0fe7f400520c" connectivity="0" command="notifyConnectivity"/>'
Sep 28, 2025 15:03:25.983 [139737185823544] Debug — [EventSourceClient/pubsub/139.162.215.242:443] PubSub: Got notified of reachability for async identifier a920628d-a17a-40d2-aa1c-0fe7f400520c: 0 for 77.161.[REDACTED]:32407 (responded in 5024 ms)
Sep 28, 2025 15:03:25.983 [139737185823544] Debug — [EventSourceClient/pubsub/139.162.215.242:443] MyPlex: reachability check - current mapping state: 'Mapped - Publishing'.
Sep 28, 2025 15:03:25.983 [139737185823544] Debug — [EventSourceClient/pubsub/139.162.215.242:443] MyPlex: mapping state set to 'Mapped - Not Published (Not Reachable)'.
