58
How to reach different services on the same machine via name instead of ip+port? (lemmy.world)
submitted 8 months ago by to c/selfhosted@lemmy.world
31 comments fedilink hide all child comments
 

On my Lan I have 192.168.1.111 hosting a bunch of various services not containerized. All connections are done either from my internal lan or from wireguard going through 192.168.1.111 so no external traffic bar wireguard.

I've set the host name of 111 in the hosts file inside the router and 111 and it works for all devices expect the ones connecting via wireguard.

But I dont want to have to use hostname+port for every service, I'd like each service to have its own name. I'd also like certs.

Can someone point me in the right direction for what I need to do? I'm thinking maybe this requires a local DNS server which im hesitant to run because im happy using 8.8.8.8.

For certs do I create a single cert on the 192.168.1.111 and then point all the applications to it?

you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 8 months ago (4 children)

Certificates can have multiple usages and you didn't specify the purpose in your case. A certificate is not necessarily tied to an IP or even a server. However, if you want to authenticate the server with a certificate, you will need the IP address to be resolved by a DNS. So, you should clarify what you actually want to accomplish. Do you expect your certificates to be self-signed or signed by a certification authority? A certification authority cannot validate a private IP address.

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 3 points 8 months ago* (3 children)

    Sorry, a cert for https because im sick of the annoying browser warning. Self signed is fine and I can use certbot for that I believe.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 9 points 8 months ago (1 child)

    self-signed won't get rid of any warnings, it will just replace "warning this site is insecure" with "warning this site uses a certificate that can't be validated", no real improvement. What you need is a cert signed by an actual certificate authority. Two routes for that:

    1. Create your own CA. This is free, but a PITA since it means you have to add this CA to every single device you want to be able to access your services. Phones, laptops, desktops, etc.

    2. Buy a real domain, and then use it to generate real certs. You have to pay for this option ($10-20/year, so not a lot), but it gets you proper certs that will work on any device. Then you need to set up a reverse proxy (nginx proxy manager was mentioned in another post, that will work), configure it to generate a wildcard cert for your domain using DNS-01 challenge, and then apply that cert to all of your subdomains. Here's a pretty decent video that walks you through the process: https://m.youtube.com/watch?v=TBGOJA27m_0

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •