I’m using Heimdall to easily access my self hosted stuff ATM. I would like for my family to use them too if they’re so inclined, but there’s no way they will be able to remember the IP addresses, I know I can’t!

Is it a DNS I’m looking for? If so, I’m already hosting a couple of instances of Adguard, can I just set it so that Plex is 192.xxx.x.47 and snapdrop is 192.xxx.x.53 and use that to resolve the request so my 13 year old can just type Plex into his browser and find it?

Or do I need something like Caddy or Nginx or something in between?

Thanks for any advice.

  • LifeBandit666@feddit.ukOP
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    10 months ago

    I WANT to learn how to do all that stuff properly but it hurts my brain. I WILL learn it at some point.

    But I have a domain with Cloudflare and found that far simpler than DuckDNS and Nginx .

    I intend to look into Nginx and caddy and learn them, it annoys me that it makes my eyes cross, but if I can just use Adguard for now then I shall do that, for now.

    I’m at a point where I know that the IT manager at work is a bit shit because the internal addresses at work have no certificate, but also that I’m not better because it makes my eyes cross too. I’ve done it before but I don’t know how I did it, it was a lot of poking.

    • Scrubbles@poptalk.scrubbles.tech
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      10 months ago

      nginx is a beast, I haven’t used Caddy. What I’d say to a newcomer is stick to the plan, just do it step by step. Don’t go looking to build a 30-service massive 1000 line nginx file immediately. Start small.

      • Get the proxy running. Celebrate, have a beer.
      • Proxy a single service through your new proxy. Celebrate, take a break.
      • Proxy a second service through the proxy,.
      • Set up SSL for those services.
      • Set up each service individually.

      Trying to do it all at once will make you go crazy, I made that mistake. Focus on one small thing at a time, slowly adding to your config, that’ll make it easier. Also make backups, or better yet store the conf in a git directory or something so you can easily rollback. If you have one service running but adding a second breaks it and you want to take a break, it’s a lot better rolling it back to a known good state rather than leaving it in a broken state.