Technology

1928 readers

7 users here now

Rumors, happenings, and innovations in the technology sphere. If it's technological news, it probably belongs here.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

2 domains, 2 servers, 2 web servers - 1 public IP (beehaw.org)

submitted 2 years ago by [email protected] to c/[email protected]

38 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 2 years ago

The setup for my home network is:

caddy
tailscale
PiHole

I have several machines running different services.
Tailscale is in each one of them with the MagicDNS setting pointing to the tail IP of the PiHole.

In the PiHole's DNS I have my different addresses pointing to the machine running caddy (for jellyfin, for PiHole itself, for each of the projects I sometimes run)
(this will be replaced by your domains pointing to your public IP where you'll be running caddy).

Now in the CaddyFile you'll have something like this

jellyfin.pe1uca.local {
    reverse_proxy <service_tail_ip>:<port>
} 

pihole.pe1uca.local {
    reverse_proxy <service_tail_ip>:<port>
}

And the rest of your services in the same way.