Server Version#: v1.41.9.9961-46083195d
Player Version#: 4.149.0 (web)
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
Hello,
On August 10th, I logged into my PLEX and the TV app displayed “network unavailable.”
My server is a PMS on Windows 10 and I’m using “Veeam backup agent”. So, I ran a full restore to July 29th.
The restore was successful, but it still didn’t work. So I removed my PMS from the list of authorized devices to claim it again, but it didn’t work.
Now I’ve looked at the articles on the PLEX forum and read my PMS logs. The PMS seems to be unable to contact the “PubsubServerManager.”
Can you help me please ?
Plex Media Server.1.log (7.5 MB)
Most likely it is your ISP sabotaging Plex access by not resolving plex domains.
Set the “DNS Server” in your router settings to 8.8.8.8 and 8.8.4.4
then reboot the router,
then reboot your server,
then reboot all other client devices in the local network
If you are contacting your ISP, please ask them why they are blocking Plex.
It works with DNS 8.8.8.8. Thanks for the troubleshooting.
What should I ask my carrier to unblock PLEX ?
Show them the same error messages that you quoted above.
It is clear that this is a DNS issue. And before you changed them in your router, you used the DNS server of your ISP – which failed to resolve the necessary plex domain(s).
Perfect, thank you for your explanations and especially for your exemplary responsiveness, you are the best ! 
Hello,
To resolve the problem, my provider requires the following information :
- Protocol type
- External port
- Internal port
In the PLEX logs indicates:
[CERT] Subject name is /CN=*.d7cd2d2e946d4a31a3a5348a52d32e28.plex.direct
Aug 22, 2025 19:43:57.922 [12636] DEBUG - [CERT] Installed certificate with fingerprint 11:59:01:72:c3:72:fe:fa:46:64:c2:c3:77:d8:e7:1a:b7:b9:f6:06.
Aug 22, 2025 19:43:57.922 [12636] DEBUG - [CERT/OCSP] no URL available
Aug 22, 2025 19:43:57.922 [12636] WARN - [CERT/OCSP] getCertInfo failed; skipping stapling
My ISP confirms that the ports are open and there is no filtering.
I updated PMS v.1.42.1.10060-4e8b05daf
The problem is still present.
New log.log (2.0 MB)
