Reverse Proxy with Nginx/Apache2?

[MartinIAm]

Hello, I am having trouble setting up a reverse proxy. So one of my websites run on NGINX and the other ones run on Apache2. How can I setup a reverse proxy so when a someone types in a web url to the address bar it leads them to the website? Should I set this reverse proxy with Nginx or Apache2? Also, most people tell me to run both websites on one server, but one of them only runs on Nginx and the other one only runs on Apache2, so I'm kinda stuck here. Also for this reverse proxy what should be the specs of it? I currently have a server that I can virtualize to use as a reverse proxy.

[colonel_mortis]

If your websites are already running nginx or Apache, and they are running on different servers that are exposed to the Internet, you don't need a reverse proxy - you just need to point your DNS towards those servers.

 

If you do need a reverse proxy though, I would lean towards nginx, although both will work fine. The nginx beginner guide includes instructions for setting it up as a reverse proxy - you would want to add a server block for each website, and proxy_pass within a location / { ... }  block in each.

 

36 minutes ago, MartinIAm said:

one of them only runs on Nginx and the other one only runs on Apache2, so I'm kinda stuck here

I'm not sure what you mean by this. There are very few things that only one of them can do, so if you have control of the server you should be able to change the server software if you wanted to. There is no need to do that for this though.

[Master Disaster]

You can run both Apache and NGINX on a server at the same time, all you have to do is change the default port for one of them.

[MartinIAm]

57 minutes ago, Master Disaster said:

You can run both Apache and NGINX on a server at the same time, all you have to do is change the default port for one of them.

I want the same default port though.

[MartinIAm]

1 hour ago, colonel_mortis said:

If your websites are already running nginx or Apache, and they are running on different servers that are exposed to the Internet, you don't need a reverse proxy - you just need to point your DNS towards those servers.

 

If you do need a reverse proxy though, I would lean towards nginx, although both will work fine. The nginx beginner guide includes instructions for setting it up as a reverse proxy - you would want to add a server block for each website, and proxy_pass within a location / { ... }  block in each.

 

I'm not sure what you mean by this. There are very few things that only one of them can do, so if you have control of the server you should be able to change the server software if you wanted to. There is no need to do that for this though.

The servers are already on the internal network, not external. I will look at the guide though.