Selfhosted

39980 readers

949 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

[email protected]

A question re. #wireguard (social.graves.cl)

submitted 1 month ago by [email protected] to c/[email protected]

19 comments fedilink hide all child comments

A question re. #wireguard

When I'm away from home I usually connect to my home (US) and my server (Europe). However sometimes (not always) the connection to my home is blocked, I don't know if it is caused by my phone company or my ISP. I blame the latter, because the connection to my european server never fails.

I wonder if there is something I can do in those cases?
I guess I could try to redirect the traffic to use the european server as a proxy, but that would make things slower the 90% of the time this isn't a problem. Also, this would require me to switch wireguard connections manually, which is not ideal, especially if I'm driving.

Another alternative would be tailscale (maybe with headscale), but I'd rather keep my infrstructure as wireguard only.

Any ideas? cc @[email protected] @[email protected]

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

[–] [email protected] 1 points 1 month ago

Could it be that the domain name has both IPv4 and IPv6 and depending on the network you try to reach one or another? Wireguard can work on both protocols, but from my experience it doesn't try both to see which one works (like browsers do). So if at the first try the dns resolves the "wrong" IP version, wireguard cannot connect and doesn't fallback trying the alternative.