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…

  • CameronDev@programming.devEnglish
    0·
    10 days ago

    I can’t remember exactly what its called, but something like router loopback is what you want. I’ll have a look around. But if you set it right, things should work properly. It might be a router setting.

    • EvilCartyen@feddit.dk
      OPEnglish
      0·
      10 days ago

      Thanks - I have an icotera i4850 router which claims to support NAT loopback, but I can’t figure out where to do it and it seems like the manual is gone from the internet :) Might have to ask my internet provider if they have a PDF somewhere.

      Edit: D’oh, it’s a checkbox in the port forwarding interface! Thanks a bunch, didn’t know what to look for before your reply :)

      • CameronDev@programming.devEnglish
        0·
        9 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 :/

    • Creat@discuss.tchncs.deEnglish
      0·
      9 days ago

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