Hello, all. I'll start this post off with - this is a test. :P I have the same topic posted at /r/... seeing if I get any l<3ve over here!!! I hope so!!! LemmyNet for the WiN!
I have two domains that I pay for... lets call them domain1.com and domain2.com.
I'm running a Bitwarden docker container that uses nginx to serve the website... its address is bitwarden.domain1.com .
I'm running a HUGO website with Apache2... its address is domain2.com .
I have one local IP address; currently, I forward ports 80 & 443 to the local IP of the Bitwarden VM.
So... thats my issue; I don't understand how to forward these two different services to the domains that I want them on... I've read about Apache2's vhosts - but the websites are on different VMs, and the Bitwarden docker container uses nginx.
I've thought about condensing and putting both services in one VM; but theres still the apache2/nginx issue. I've heard someone mention I should use a third VM to route the traffic to the correct local IPs - but I don't know what software I'd use.
I've thought about using a Cloudflare tunnel for one of those services; but I don't really want to pay, and aren't sure how fast a free Cloudflare tunnel would be - this might be a solution for the Bitwarden service, as I'm the only one accessing it...
Does anyone have any suggestions? I'm sure I'm just novice enough that I don't see the obvious solution - and I'd love to get both sites up and running. Thanks for any input or help!!!
pAULIE42o
. . . . . . . . . . .
/s
Alright, I wanted to come back now that my setup is complete... special thanks to those of you who suggested nginx-proxy-manager - its very nicely put together and really makes reverse proxies a breeze...
Long story short, I just created a brand new VM... started with the proxy manager and built on top of that. Next up was my static Hugo website; it was too easy to point change Apache2's ports.conf to 8097 instead of 80, and use nginx-proxy-manager for the SSL certs... that one was basically plug and play.
The Bitwarden bit was a bit more involved, but not too bad... at first I just redirected traffic to the original (other machine) Bitwarden VM - but no one wants an extra VM to backup and support... so I went with a fork Docker of bitwarden_rs/vaultmaster - it comes w/ e-mail setup in the container, so one less thing to worry about... I had to swap around some docker-compose.yml ports and just point nginx-proxy-manager at it... this time, tho, I used the SSL certs from the docker; I didn't wanna dig in and remove what they already had running.
In the middle I was still fighting with myself and not taking ya'lls good suggestions - I tried to go the Cloudflared route; which is a cool service... but you can't tunnel root domains unless you're a paid user. Cloudflared tunnels would be great for exposing the Plex, TrueNAS, etc's of the world... but I didn't NEED/want subnets.
Thanks to the Beehaw community... TechHeart.life is up and running. :P (Don't worry, the Bitwarden is on a private domain. Phhhbbbbtttt.)