Apache as Reverse Proxy and Lets Encrypt SSL

wh33t · 02-18-2020, 01:28 PM

Hey LQ,

I was hoping to get some confusion cleared up. I've got a server in my office that is running 2 virtual machines. Both are linux, one is a nextcloud instance, the other is just a traditional LAMP setup. I have them separated for reasons, the main reason being I will likely put those VM's on separate machines at some point in the future and keeping them isolated like this is pretty much industry standard at this point isn't it?

So I'm thinking about setting up Apache as a Reverse Proxy, that will forward cloud.mydomain.com to the nextcloud VM, and www (or any other subdomain really) to the LAMP VM.

1. Is this the right solution to the right problem?
2. When Apache is operating as a reverse proxy, does every bit of data that it is proxying have to go through the proxy itself? Am I correct in thinking it very much operates as a gateway for all proxied devices/services behind it?
3. Do I need to do anything special to use LetsEncrypt Certbot in a setup like this?

I just want to make sure I'm on the right track before I dump anymore time into setting this up. Please and thank you!

Morgo · 02-19-2020, 04:19 AM

Hey,

I would highly recommend that you use nginx as your reverese proxy, and keep apache in front of it.

Otherwise, you seem to be on the right track. You might run into some issues with Certbot and let's encrypt over one such set-up.

I've found myself battling this oddity a few times at a hosting company I shall not name, that I previously worked in, several times over.

https://community.letsencrypt.org/t/...rd-proxy/49484

This post on let's encrypt's community forum might shed some light on the matter, it is a common issue, when setting up any kind of proxy-ing.

Best regards,

Morgo

jdrosales · 02-26-2020, 12:39 PM

Quote:

Originally Posted by wh33t

Hey LQ,

I was hoping to get some confusion cleared up. I've got a server in my office that is running 2 virtual machines. Both are linux, one is a nextcloud instance, the other is just a traditional LAMP setup. I have them separated for reasons, the main reason being I will likely put those VM's on separate machines at some point in the future and keeping them isolated like this is pretty much industry standard at this point isn't it?

So I'm thinking about setting up Apache as a Reverse Proxy, that will forward cloud.mydomain.com to the nextcloud VM, and www (or any other subdomain really) to the LAMP VM.

1. Is this the right solution to the right problem?
2. When Apache is operating as a reverse proxy, does every bit of data that it is proxying have to go through the proxy itself? Am I correct in thinking it very much operates as a gateway for all proxied devices/services behind it?
3. Do I need to do anything special to use LetsEncrypt Certbot in a setup like this?

I just want to make sure I'm on the right track before I dump anymore time into setting this up. Please and thank you!

I agree with the answer of Morgo about setting up nginx as the reverse proxy.
On the ssl certificates from letsencrypt.org I found an article that is up to date and that will guide you step by step on how to do what you want: https://linuxize.com/post/secure-ngi...-ubuntu-18-04/

Regardless of it been written for Ubuntu 18.04 server, it might apply well for what you want.

Good luck!