Server is up-to-date. Server has been restarted, players have been restarted, router has been restarted; every single piece of technology I have has been restarted. Works on my phone and tablet, does not work on web player on PC or PS5. Always hit with “app.plex.tv is unable to connect to server name securely”. Works on web player if I connect directly using the local IP address of the server.
Edit: Convinced that this is an ongoing DNS issue as these errors are appearing in my Pi-Hole every time I load up Plex in a web browser via app.plex.tv. I’ve verified that it’s not my Pi-Hole is not the issue as I’ve disabled and even unplugged it completely and still getting no connection (and restarting the server multiple times)
Honestly wish there was a dedicated support ticket system, even if I had to wait rather than this lottery of hoping a thread is seen.
Restarted the server and grabbed the logs, not happy just posting them as they include my e-mail. Happy to share via PM.
Still cannot access the server remotely, restarted multiple times. Can only access it locally by putting in the local IP. Has been working without issues until the DNS issues occurred.
Same exact issue. Able to access server on 127.0.0.1:… Can access using Plex app on Firesticks, iphone both local and external. Unable to access via browser, get “app.plex.tv is unable to connect to “xxxx” securely”. Secure connection are set to preferred. Server is on newest (1.23.4.4805). Have restarted multiple times without any changes. Have tried accessing via 2 different PC’s.
Can y’all if possible reboot your modem/router and restart server. and/or try usinng googles DNS instead of whatever your ISP uses. Public DNS | Google Developers
I’m using Pi-Hole as my DNS resolver and haven’t had any issues before the DNS issues Plex suffered. I’ve already attempted removing it, restarting the server and using Google’s DNS (as that’s what I was using before Pi-Hole) and still ran into the same issue. Couldn’t not connect to the server remotely, could not connect on my PS5 but works via the local IP on my desktop and on my tablet/phone through the app.
At this point I’m restarting the server after every little fix I attempt, I sincerely don’t believe that the issue is on my end and with the growing number of people suffering from this issue still I’m inclined to believe it’s on Plex’s end. Everything short of the fridge has been restarted multiple times over the past few days.
Edit: Updated to 1.23.5.4841, restarted everything. Problems persists. I’m still happy to provide logs, just don’t want to post them publicly.
it is on plex’s end. theyre saying its on our end. but i guarantee you. the people having the problem, like myself. i havent touched my dam server in 4-5 days. i leave it fine and it runs smooth. i have servers at home that i run, ive made 0 changes. i play games on my spare time. i have mining rigs setup. 100% this is not on our end, but they are trying every ghetto hotfix they can to say, “hey its working” like, restarting our modem and server, i guarantee you everyone has done that already. this is clearly not on our end. ill provide logs to if thats something you guys need, but at the same time, you guys trying to post solutions we can do on our end, is not gonna be the fix, clearly something did not happen on our end.
Since typing this one minute ago, I will also add the following.
I have 3 4k rokus, my pc, my laptops i have a bunch of machines setup on my Plex server.
Yesterday all my devices could connect. I just went and checked the roku in my living room they are only connected to Wifi, are now having the same issue of everything having the yellow hazard with the “!”
I can confirm that there is still an outstanding issue. I installed the latest server version after being notified today there was an update and still the issue persists. I’ve restarted the server and the “unable to connect securely” error is still there for some at least.
On PC I normally connect to app.plex.tv but just now downloaded the windows Plex app https://www.plex.tv/media-server-downloads/#plex-app and was able to connect. On the same PC through the browser I can’t connect.
Something that may help others who are experiencing this issue is to temporarily change your DNS provider to Google’s servers in your router…or in the client and server computers if that is where your DNS entries are controlled from. See if you can then access your server through app.plex.tv. If you can, then change back your DNS entries (both primary and secondary) to what it was before. Ideally, you should be able to still access the server remotely. Don’t know why this works, but it seems that it is working for other folks having this issue and it has worked for me as well.
May not work for everyone as I’m using a Pi-Hole. I’d tried setting using Google’s DNS whilst disabling the Pi-Hole and that didn’t work. I went into the settings of the Pi-Hole however and switched to Google’s DNS and Plex started working again, switched back to OpenDNS and it’s still working.
plex.direct has address 82.94.168.7
Host plex.direct not found: 2(SERVFAIL)
;; connection timed out; no servers could be reached
This is what I get. Looks like one or more DNS servers on PLEX’s end are not working correctly. Update your NS records on your domain or FIX the issue.
@kegbeach would you mind trying a dig and tell me iff they all return the same. We are not finding an issue (not saying there is not one still on our end)
Server is up to date (Version 1.23.5.4841), nothing changed in the local network, server setup or devices that access the server. Plex server has been restarted, as the actual server that it runs from.
Through the Plex web interface of the server I can see that server is found, in the settings it’s there. But all libraries are reporting: " Something went wrong - There was an error loading your home screen. Please try again in a few minutes."
All devices I use to connect are local in the same network as the server and they all show the same issue.
Why can’t I see my local media, why does Plex even needs internet for me to see local stored media? With a lifetime Plex pass you should have the option to keep working in the event issues like this happen or internet outages.
$ sudo systemd-resolve --flush-caches
$ host plex.direct
plex.direct has address 82.94.168.7
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
$ host ns-plexdirect.plex.tv
ns-plexdirect.plex.tv has address 82.94.168.7
$ host ns-plexdirect.plex.bz
ns-plexdirect.plex.bz has address 184.105.148.70
$ host ns2-plexdirect.plex.tv
ns2-plexdirect.plex.tv has address 184.105.148.71
$ host ns2-plexdirect.plex.bz
ns2-plexdirect.plex.bz has address 82.94.168.8
$ host ns3-plexdirect.plex.tv
ns3-plexdirect.plex.tv has address 82.94.168.9
$ host ns3-plexdirect.plex.bz
ns3-plexdirect.plex.bz has address 184.105.148.72
$ nc -zvw10 82.94.168.7 53
Ncat: Version 7.80 ( Ncat - Netcat for the 21st Century )
Ncat: Connected to 82.94.168.7:53.
Ncat: 0 bytes sent, 0 bytes received in 0.11 seconds.
$ nc -zvw10 82.94.168.8 53
Ncat: Version 7.80 ( Ncat - Netcat for the 21st Century )
Ncat: Connected to 82.94.168.8:53.
Ncat: 0 bytes sent, 0 bytes received in 0.11 seconds.
$ nc -zvw10 82.94.168.9 53
Ncat: Version 7.80 ( Ncat - Netcat for the 21st Century )
Ncat: Connected to 82.94.168.9:53.
Ncat: 0 bytes sent, 0 bytes received in 0.10 seconds.
$ nc -zvw10 184.105.148.71 53
Ncat: Version 7.80 ( Ncat - Netcat for the 21st Century )
Ncat: Connected to 184.105.148.71:53.
Ncat: 0 bytes sent, 0 bytes received in 0.07 seconds.
$ nc -zvw10 184.105.148.72 53
Ncat: Version 7.80 ( Ncat - Netcat for the 21st Century )
Ncat: Connected to 184.105.148.72:53.
Ncat: 0 bytes sent, 0 bytes received in 0.08 seconds.
Something up with ns-plexdirect.plex.bz/184.105.148.70 which is refusing connections but is listed as an authorative DNS.
Since DNS works as a round robin system users will end up hitting the server that refuses connections and their connections may or may not time out before another host is used.
Consultations start at $150/hr with 1 hour minimum. DM me.
host plex.direct
plex.direct has address 82.94.168.7
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
And also in Mac via terminal:
PING plex.direct (82.94.168.7): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
…
— plex.direct ping statistics —
141 packets transmitted, 0 packets received, 100.0% packet loss
