Selfhosted

40347 readers

363 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

domains on internal network (feddit.dk)

submitted 5 months ago by EvilCartyen@feddit.dk to c/selfhosted@lemmy.world

21 comments fedilink hide all child comments

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....

you are viewing a single comment's thread
view the rest of the comments

[–] CameronDev@programming.dev 17 points 5 months ago* (last edited 5 months ago) (3 children)

I can't remember exactly what its called, but something like ~~router~~ NAT 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.

Found it: https://community.tp-link.com/en/home/stories/detail/1726

[–] EvilCartyen@feddit.dk 14 points 5 months ago* (last edited 5 months ago) (1 children)

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 :)

[–] danielquinn@lemmy.ca 8 points 5 months ago

Thanks for posting this! I have the same router.

[–] Creat@discuss.tchncs.de 11 points 5 months ago

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

[–] poVoq@slrpnk.net 4 points 5 months ago (1 children)

I think the term often used is "NAT reflection".

[–] CameronDev@programming.dev 3 points 5 months 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 :/