So maybe I am missing something obvious, but here goes:

I’ve got a small server at home, and I have simply.com pointing various domains to it. Works fine, nginx routs the traffic where it needs to go.

But whenever I am at home and connected to wifi I have to use the internal address and port to reach my server, e.g. 192.168.0.192:8096 for my Jellyfin server. If I use the public URL at home, i hit the login page to my router.

This is annoying when I use apps, as I need to switch between the public URL and the internal address as I come and go from my home…

What are my options for doing something about this? I want to use the public URL at home too…

    • EvilCartyenOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 months ago

      I did go for that 😁 was a simple checkbox in the router settings.

      • aaravchen@lemmy.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 months ago

        FYI, this is called “split horizon” DNS, where the location you get directed is based on the network you adk from. Make sure you have short TTLs set on your DNS records, or devices can have problems moving between networks and still having records cached from the prior network