Excellent news, at least I know where to start now. I wanna play with all the network things and learn, but I also wanna just have it sorted in 5 minutes of hacking
Excellent news, at least I know where to start now. I wanna play with all the network things and learn, but I also wanna just have it sorted in 5 minutes of hacking
rambos@lemm.ee 10 months ago
Its that simple to use different IPs just with DNS server:
DNS server
But dont you have your services on the same IP and different ports? If thats the case you will also need reverse proxy like nginx. So DNS server will point your domain name (you can just make a name for local use) to your server IP. Then reverse proxy can point each name to a specific IP and port.
Reverse proxy
Lifebandit666@feddit.uk 10 months ago
I don’t know why you were downvoted for this, you’re right and I figured this out for myself last night when I decided to try figure it out at 1.30am after 3 beers.
I managed to get all my port 80 stuff sorted but my Arr stack for example needs something more, probably the dreaded nginx…
I’m having a look at Caddy now because I’ve never used it before, Nginx I didn’t like when I used it and I’ve recently heard the original developer has left the project and started a new one.
Rehwyn@lemmy.world 10 months ago
Nginx is a lot less painful if you use Nginx Proxy Manager. You get a nice GUI and can easily get SSL certificates with Let’s Encrypt.
7Sea_Sailor@lemmy.dbzer0.com 10 months ago
If you dont fear using a little bit of terminal, caddy imo is the better choice. It makes SSL even more brainless (since its 100% automatic), is very easy to configure yet very powerful if you need it, doesnt require a 200 MB mysql database and does not have issues with path filtering due to UI abstractions. There are many more advantages to caddy over NPM. I have not looked back since I switched.