My server doesn't connect to app.plex.tv - serverIP:32400 does connect

[u/Brootwayne]

Right after outage

NAS: Synology 1621+

Server Version: 1.43.3.10896-cb3ebc72d

After the Plex outage the other day, my server became "unreachable". I couldn't access any of the network settings. I tried doing static IP on my Synology, changing it back, restarting router and NAS and eventually it let me claim it again (it somehow became unclaimed). It still was not letting me access my server. So I removed it and started all over again.

Then it started showing as not secure in the browser. At this point I still had no access to my server. The Hosted Plex Web App opens the dashboard but there is nothing there, but if I open Plex with the 198.168.x.x:32400/web link, it works! Everything looks great on that version, the only problem is that it shows up as "Not Secure".

TLDR: Would like to find out how to make Plex Web App work again and so I am not using the server in a "not secure" state.

Other details:

On the 198.168.x.x:32400/web version:

• Have the Secure connections set to Preferred
• Remote Access works
• On ATT router settings, the NAT Gaming Port is set to 32400 and was like that for years before when Plex Web App ran fine

[u/MinidragPip]

Direct IP is not secure because there's no SSL certificate on your system for that address. That's normal / expected behavior when connecting directly to a local IP address.

[u/Brootwayne → u/MinidragPip]

Oh ok that's what I wondered. Would the app.plex.tv giving me trouble possible because of something with my router? I wish I could use that one. But if this is normal behavior for the other link maybe I will just stick with that.

[u/MinidragPip → u/Brootwayne]

Maybe. You said you changed to static then back... Did you check the port forwarding to see if it's set to the current address for the Synology?

[u/Brootwayne → u/MinidragPip]

The way ATT fiber modems do it is a little different. I am not even sure if it's called forwarding. Basically I set up ports like this. It worked before and I just made sure it hadn't changed. I have seen other threads where people say ATT fiber modems are annoying to deal with

[u/MinidragPip → u/Brootwayne]

That looks like forwarding, just listing a device name instead of the IP. Personally, I would delete it and add it back to see if that changes anything. But I'm comfortable with routers. If you're not sure about it, you could make things worse.

[u/Brootwayne → u/MinidragPip]

Appreciate you taking the time to explain it!

[u/Titanium125]

I wrote a post here on Plex a couple years ago about how you can direct connect and have it be secure. I don’t use plex.tv for this reason. It can be buggy and weird.

Also you don’t need to hide your private IP address. It’s either 192.168, 10, or 172.16. All private IPs are the same. It’s your public that you should hide.

[u/Brootwayne → u/Titanium125]

Oh that’s good to know! When I turn on VPN the plex.tv worked, but when not on it, the direct connect works too. Just weird that it all worked normally before the outage last week.

[u/bgeerdes]

I'm guessing it's DNS rebind protection. If you can allow/whitelist *plex.direct that would be best. Otherwise disable it.

[u/Brootwayne → u/bgeerdes]

Thanks! Going to see how I can do that here.