I cannot reach my own plex server on 127.0.0.1:32400. It pops up a message that says “Plex is Not Reachable”. When I try to log in at Plex.TV it says “there was a problem logging in”. I’ve had this problem before when there was a double NAT situation, but I’ve disconnected everything and connected the server through USB tethering on my phone and I still can’t reach plex.tv. I’ve cleared cookies, I’ve cleared ARP tables, I’ve flushed dns, I’ve restarted. I’ve reinstalled PMS. I can reach plex.tv on any other device on the same network and login fine, though my server is no longer reachable. I had the server set up to allow connections without authentication on my local IP range and on 127.0.0.1.
Same result. That just goes out to the internet to come back and find localhost. The issue appears to be related to plex authorization, which I can’t reach at all. Although local host was set up as allowed without authorization and that worked during internet outages, so there is something slightly more to it I think.
Alright, you asked me to reply over here so I will.
I looked at your logs.
This error shows up over and over again:
[HttpClient] HTTP error requesting GET Sign In | Plex (60, SSL peer certificate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name ‘plex.tv’)
So this is the first link I found that seems to be relevant:
I know you mentioned your firewall was off.
What are you using for router/cable modem/firewall hardware appliance?
I’m using an AT&T router with no additional firewalls. There is another router for my local network which can be annoying, but to rule that out I have the computer attached directly to the router with on a different subnet. No proxy and no VPN. Other computers on the network do not have that SSL problem and can log in just fine.
The issue was that I couldn’t reach the authentication service for plex.tv, which I knew and was clear from the logs. The cause was a windows service called VPNbypass that was designed to route Plex around a VPN so remote access would still work. It was manually routing plex.tv and a few other plex related things so they wouldn’t go through a VPN. The routing it was using for plex.tv was no longer valid, so it routed those requests to a dead end. I haven’t used a VPN in years, but this was a windows service so I had forgotten it was even there. Removing the windows service and deleting the manual routs from the network host file solved the issue.
If you are unable to sign in or unable to authenticate on Windows, check you network host file to see if it is doing any funky routing. And also remove VPNbypass. It worked but it was a brute force solution and this is a great example of why I hate those.
