The address in your web browser’s URI bar is no indication about whether the traffic between your plex server and the plex app running in the web browser is encrypted.
It is merely indicating, if the web app as such was loaded through an encrypted connection or not.
After the web app has been loaded into the browser, things can change.
That’s why there are icons beside the server name(s). A green padlock indicates encrypted communication.
All Plex traffic is using one single TCP port. Encrypted or not.
All necessary domain names and encryption certificates are provided by Plex, btw. by default. You don’t need to supply your own.
Hi,
thanks a lot for the quick reply.
I was searching for a dedicated HTTPS port which I did not find.
But when checking your information I see that the port 32400 will handle both HTTP and HTTPS.
So https://localhost:32400 is working as well. Then I get an certificate error (which is expected and OK) and connection is TLS 1.2 encrypted.
This has only indirectly to do with secure connections.
The connection to this server cannot be made directly.
If it is a local server, it is probably because your DNS resolver (router) or your ISPs DNS server don’t play ball.
try to use Google’s DNS servers instead (8.8.8.8)
try and find if there is a setting in your router related to ‘DNS rebinding protection’.
If there is, tell it to make an exemption for the domain plex.direct
Thanks,
the connection above was from a company Network. So maybe there are some restrictions.
Now from Home Network (via plex.tv) it looks OK:
I have a no-ip.com DNS entry for my external IP, so maybe this is something blocked here.