Selfhosted

59999 readers

799 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.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Hairpin dns issue (lemmy.world)

submitted 2 months ago by mortalic@lemmy.world to c/selfhosted@lemmy.world

29 comments fedilink hide all child comments

I've got Immich working great on Unraid, but if I'm on my network I can't really use it. Just fails to resolve the dns. I looked it up and it's that my router doesn't support hairpin or something. It's a Aginet hb810. I found a workaround in the Immich client where you can add a second entry that's network specific, but it doesn't seem to work very reliably.

What are my options?

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

[–] tko@tkohhh.social 1 points 2 months ago* (last edited 2 months ago) (1 children)

The challenge here is that the host is Unraid, which publishes its own interface on 80/443. My reverse proxy is of course handling all requests for my sites, but that is ALSO running on a container, and must be listening on something other than 80/443 when using host or bridge networking.

So, if I'm following along correctly, I would need to put my reverse proxy on a different host (bare metal or VM) in order for it to listen on 80/443.

[–] cecilkorik@lemmy.ca 2 points 2 months ago* (last edited 2 months ago) (2 children)

I'm not too familiar with unraid but from a little research I just did it seems like you're right. That does seem like a really unfortunate design decision on their part, although it seems like the unraid fans defend it. Obviously, I guess I cannot be an unraid fan, and I probably can't help you in that case. If it were me, I would try to move unraid to its own port (like all the other services) and install a proxy I control onto port 443 in its place, and treat it like any other service. But I have no idea if that is possible or practical in unraid. I do make opinionated choices and my opinion is that unraid is wrong here. Oh well.

[–] tko@tkohhh.social 1 points 2 months ago (1 children)

As I dug into this, I found that it is in fact trivial to change the Unraid UI ports. There's a setting for it. I can only assume that since Unraid attracts a LOT of novices, bad advice gets passed around and taken as gospel. So, I changed Unraid's ports, set my reverse proxy to listen on 80/443, updated the NAT on my router, and added the relevant host overrides to the DNS Resolver. Hairpin eliminated. Thanks again!

[–] cecilkorik@lemmy.ca 2 points 2 months ago

Great news! Also thanks for providing the follow-up, hopefully it helps people who use Unraid in the future.

[–] tko@tkohhh.social 1 points 2 months ago (1 children)

Totally fair... I appreciate you engaging with me, your perspective is appreciated! I won't defend Unraid's choice when it comes to the UI ports, but I will simply say that there are things that are really nice about Unraid from a usability standpoint.

Thanks again for your thoughts!

[–] cecilkorik@lemmy.ca 2 points 2 months ago

Convenience is great until it becomes inconvenient. But that's a journey we all make :)