Setting up Nginx on CentOS 7 as a reverse proxy
-
@JaredBusch I setup a reverse proxy with nginx for ScreenConnect, but the relay port isn't working. Can you provide your setup for how your relay is setup? Does it require two different IPs?
-
@zenbu said in Setting up Nginx on CentOS 7 as a reverse proxy:
@JaredBusch I setup a reverse proxy with nginx for ScreenConnect, but the relay port isn't working. Can you provide your setup for how your relay is setup? Does it require two different IPs?
That's not HTTP traffic. You would have to set Nginx up for TCP/UDP load balancing
-
@zenbu said in Setting up Nginx on CentOS 7 as a reverse proxy:
@JaredBusch I setup a reverse proxy with nginx for ScreenConnect, but the relay port isn't working. Can you provide your setup for how your relay is setup? Does it require two different IPs?
First, do you need a revere proxy for that? It's not web traffic. If you do, I'd recommend HA-Proxy.
Second, don't use CentOS 7 today. This guide is very old.
-
@scottalanmiller said in Setting up Nginx on CentOS 7 as a reverse proxy:
@zenbu said in Setting up Nginx on CentOS 7 as a reverse proxy:
@JaredBusch I setup a reverse proxy with nginx for ScreenConnect, but the relay port isn't working. Can you provide your setup for how your relay is setup? Does it require two different IPs?
First, do you need a revere proxy for that? It's not web traffic. If you do, I'd recommend HA-Proxy.
Right, you port forward the relay traffic. It is encrypted by the clients on each end. You SSL certificates do not apply to it anyway.
-
@scottalanmiller said in Setting up Nginx on CentOS 7 as a reverse proxy:
Second, don't use CentOS 7 today. This guide is very old.
Well the new guide is old already too. But at least it is still the same on Fedora 31 as it was on Fedora 27...
https://www.mangolassi.it/topic/16651/install-nginx-as-a-reverse-proxy-on-fedora-27
-
@flaxking Good point, I found out about that and have been reading up on it. Using ngx_stream_ssl_preread_module seems like it may be the solution. It will let you differentiate between HTTP SSL traffics and non HTTP ssl traffic. That way I'm hoping to use port 443 for both the web portal and the ScreenConnect relay.
-
@zenbu said in Setting up Nginx on CentOS 7 as a reverse proxy:
That way I'm hoping to use port 443 for both the web portal and the ScreenConnect relay.
I don't believe that there is any possible way to do that. Because you'd need a host header or something to differentiate and SC doesn't work that way.
The traffic is designed to be on different ports. They can be any ports that you want, but not the same one.
-
You have two issues... the first is what we call "being weird." This is a bizarre thing to be trying to do. It's not wrong, it's just "weird"... that kind of thing that hard to describe but it's clearly strange and trying to invent a wheel that already works really well.
The second issue is your goal: what goal are you trying to accomplish by doing this? There's not normally any reason to have the proxy of the SC control port traffic. What problem are you trying to solve by doing this?
-
@scottalanmiller said in Setting up Nginx on CentOS 7 as a reverse proxy:
What problem are you trying to solve by doing this?
If I had to guess, outbound traffic controls blocking port 8041 (the default relay port).
I run in to this sometimes.
-
If the above is your problem, then you should look at a different solution. @scottalanmiller's current favorite is MeshCentral.
It is not as good as ConnectWise Control yet, IMO, but close.
