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
Thanks so much for the reply; others have mentioned the same, or similar, but your response spelled it out... I knew this was what I needed to do [scenerio 2] but I just didn't have experience with setting up the proxy - I'm technical enough to RTFM and will get this setup today; one thing that was kinda fudging me up was that my Bitwarden machine, where the domain currenty forwards to, runs in a docker container - so I think I'll actually forward the OTHER domain to the 'lemmy' [although its not lemmy, just using your example as the reference..] machine that's just an Ubuntu server running apache2 for serving the website - and I'll probably end up using Apache's Name Based Virtual Host Support instead of your nginx-proxy suggestion - either way, I think its accomplishing the same.
Appreciate your, and all the other, replies - this thread literally performed better than on the /r/ platform! I'm sold on LemmyNet!
Both nginx and apache are webservers and can do what you need.
Apache calls this Name-based Virtual Hosts. (see ServerName/ServerAlias)
Nginx calls this Name-based virtual servers (see server_name in the docs)
Either will listen on ports 80/443 on the IP and proxy the request depending on the hostname used. If you're not really familiar with either, I would recommend nginx. It's very popular, the documentation is good and the syntax is a lot better IMO.
I hear caddy is also a nice alternative with even simpler syntax, but I haven't used it myself.
Good luck!
I can see how you're not yet familiar with all these terms :p Both nginx and apache are http servers and work the exact same in your case.
The server (apache or nginx) listens on the IP on port 80 and 443. Depending on the hostname that is used to connect, the request is proxied to a different location. Apache calls this virtual hosts, nginx call this virtual servers