Hello friends,
I am using Plex on a dedicated server with dedicated IP. I’ve been searching for ways to get remote access through port 80 for days, but without success. So I would like your help. I already released the firewall, but I can’t get remote access on port 80.
I tested Emby on this same server and with it I can access normally on port 80.
Do you know what it can be? I’m running Plex on Windows Server 2016.
Is this machine connected directly to the internet?
Or is there a router?
In the latter case it’s just a matter of creating the right port forwarding rule in the router’s settings. Then tell Plex that it shall announce port 80 for remote connections, under Settings - Server - Remote Access
It is a dedicated server and is directly connected to the internet, if I had a router in the middle I know how to do the routing, but as it is not at my house, I cannot do it.
I hire the dedicated server just to not depend on my local network.
I know there is a way to redirect a port number on Windows (totally with Windows’ own tools). But I don’t have it comitted to memory.
Google may know more.
I tried something like: https://www.oceanoinfo.com/windows-redirecionamento-de-portas-via-netsh/
But without success.
Perhaps it has to do with permissions ? On Linux for example, an application cannot just allocate ports < 1024 (priviliged) this requires a certain level of permissions.
Perhaps on the Windows installation, the “plex” user that runs the service/server is not authorized enough to run on the lower ports ? Hence the standard 32400 will work fine.
To that respect, “Emby” might be running with a much higher privilege (like ad “admin” account) so it can bind to TCP/80 ?
Don’t know, I never used Plex on Windows …
Did you actually shut down and disable the IIS service, before trying the netsh command?
Because otherwise you won’t be able to occupy port 80, since it is the default port for a web server.
This server is not running IIS, otherwise I would have a problem with Emby too.
Thanks for the answer. The two I run as an administrator.
And you are not running Emby concurrently on port 80? 
(Sorry, had to ask.)
No, I wouldn’t make that kind of mistake. 
What happens if you use a web browser on a different machine and point it to
http://ip-address:80/web ?
No Working: http://142.44.158.59:80
Working: http://142.44.158.59:32400
OK, this means that the netsh command didn’t function.
Why does it have to be port 80 anyway?
I would like to use CloudFlare over the top, and it only works on certain ports.
I’m migrating Emby to Plex, in Emby I used it normally on port 80, so I wanted to keep the same standard with Plex.
I don’t understand the use case for cloudflare.
Many, if not most media streams are going to be transcoded/remuxed specifically for each client device. Which means that cloudflare won’t be able to cache much and re-use it for the next plex client.
Some more things to try (in the discussions below):
Thank You.
My idea is not the cache, but to be able to use HTTPS and avoid route problems, since the server is in Canada and I am in Brazil.
