Security behind plex API on port 32400

Server Version#: 1.41.6.9685
Player Version#:

I hope this is the best/correct spot to post this.

Background: I have a Plex server running on a Linux box. I have port 32400 open and running on an external static IP. Remote play via mobile device and web browser works great.

I have created a set of tools to manage my Plex server (and they’re really cool! I keep wondering if I should release this suite of tools to open source, but anyway.). The tools hits the Plex API via the 32400 port. That route is not secured. All of my development work has always been in my home on my home network,

Last week I was at a friend’s home and working on my tools and was SHOCKED the code I wrote could still invoke the Plex API! Sure, to invoke anything on the API, I have to provide the Plex API token. The issue is that the route is not using SSL. I want to fix that by securing it with a certificate and forcing traffic to that port by way of port 443 (using ngnix)

My concern is, if I do that, will remote media access stop working in any way? I’m not 100% sure how remote media viewing works. I think it’s proxied by the Plex cloud server that hits some other API?

Help? Please and thank you!

You can set the “Secure connections” setting to Required, there is more info here as well as in the description of the setting itself.

1 Like

Thank you for the help!