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…

    • Creat@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      1
      ·
      14 days ago

      Another name, depending on the exact context, is “hairpin NAT”. Should make googling with the specific router OP has easier.

      • CameronDev@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        14 days ago

        Never heard that term, but its a very obscure concept, so wouldn’t surprise me if it had multiple names. Probably vender specific names?

        Seems quite a few people havent heard of it, hence a lot of the split DNS answers :/

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    14 days ago

    You may have to set up split zone DNS so names resolve to private IPs when at home but resolve to public addresses when not home.