I have self hosted immich on Debian on my homelab. I have also setup tailscale to be able to access it outside my home.

Sometime ago, I was able to purchase a domain of my choice from GoDaddy. While I am used to hosting stuff on Linux, I’ve never exposed it for access publicly. I want to do that now.

Is it something I can do within tailscale or do I need to setup something like cloudflare? What should I be searching for to learn and implement? What precautions to take? I would like to keep the tailscale thing too.

PS: I would like to host immich as a subdomain like photos.mydomain.com.

Thanks!

  • helenslunch@feddit.nl
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    4 months ago

    You use a reverse proxy. Configure your DNS (GoDaddy in this case) to forward requests to your domain to your WAN IP. Set up port forwarding on your router to send HTTPS requests to your server, then the reverse proxy processes the request and directs it to the proper container.

    This is honestly the most confusing and complicated part of self-hosting.

    It’s also all made very simple using Yunohost.

    Also please move away from GoDaddy as soon as possible. Popular alternatives would be NameCheap or Porkbun.

    • walden@sub.wetshaving.social
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      4 months ago

      This is honestly the most confusing and complicated part of self-hosting.

      I agree! It took me years to finally decide to buckle down and wrap my head around what a “reverse proxy” is. Once I figured it out things became so much more usable and fun.

      Combined with DNS redirects in my LAN (to get around NAT loopback), things are very easy to use.

      • Ænima@lemm.ee
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 months ago

        You sound like me with Docker. Still unsure how to use that shit but haven’t sat down to really try again, either.

        I agree, reverse proxy was also a little mind numbing before I really buckled down and read/watched a bunch of info on it. I learn best by examples and try-fail, but that’s hard to do with live services.

        • LifeBandit666@feddit.uk
          link
          fedilink
          English
          arrow-up
          2
          ·
          4 months ago

          I found a lot of the problems I had with Docker were with Docker. Once I moved to using Portainer for Docker it became much more accessible.

            • LifeBandit666@feddit.uk
              link
              fedilink
              English
              arrow-up
              2
              ·
              edit-2
              4 months ago

              You need to pick a machine (if you only have 1 you don’t lol) to be your web portal, bang a block of code in via ssh or command line (I copy pasted) then you can access Portainer via the web portal.

              From there “Stacks” is Docker Compose and you can fiddle with your containers, networking settings and all the other stuff via a UI instead of having to SSH in all the time to look at your compose files.

              Then if you wanna use docker on more machines you just bang a block of code into that machine via ssh and it will appear in your Portainer

              Far easier imho

              • Ænima@lemm.ee
                link
                fedilink
                English
                arrow-up
                1
                ·
                4 months ago

                I have saved this reply for the near future when I rebuild my server box to run Linux! Thanks again for your knowledge and information!