this post was submitted on 10 Feb 2025
18 points (90.9% liked)

Selfhosted

42055 readers
506 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

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

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
18
Networking Oddity (lemm.ee)
submitted 1 day ago by Hellmo_Luciferrari@lemm.ee to c/selfhosted@lemmy.world
19 comments fedilink hide all child comments
 

Hello Selfhosted!

So I have an interesting issue. I have a docker host, and that host i have a Caddy container. I have that setup to handle reverse proxying. I have it setup to be local only. I have a pihole and a wireguard server. And can connect to my network successfully.

The part that confuses me is that while on network everything works great. While on VPN I can connect to services by IP:Port. If I use mobile data with VPN, I can't use the site addresses. x.domain.xxx (for privacy sake I'm leaving my domain out of the post.) But when I connect to WiFi, any WiFi, and connect to VPN I can go to the address I have setup for reverse proxying.

I am unsure how to troubleshoot this. Any pointers would be appreciated.

you are viewing a single comment's thread
view the rest of the comments
[–] BCsven@lemmy.ca 2 points 21 hours ago (1 children)

It may not even be the issue, I'm just spitballing, and it maybe DNS issues like others mentioned or cell provider blocking some aspect. As you probably know Wireguard can be set for all traffic to route through the tunnel, or some outside of it. Maybe cell network is not routing DNS through the tunnel, but using its own, or maybe they used a cached Domain name lookup that doesn't have your domain IP. Again, networking/DNS etc is my blind spot. I.e. I have setup openmedia vault on a 256MB RAM arm board to serve my music and SMB shares, but I don't understand reverse proxy LOL.

[–] Hellmo_Luciferrari@lemm.ee 2 points 20 hours ago (2 children)

So, I of course rebooted everything i could, the box hosting my DNS/PiHole, VPN, docker box, etc. However, was remote and couldn't reboot my modem.

I lowered my MTU on my VPN client config after rebooting my modem, and it's working.

I don't fully understand why it worked, but it did.

Maybe something on my ISPs end that wasn't functioning.

[–] BCsven@lemmy.ca 2 points 17 hours ago

Awesome! Interesting with MTU. This was a first hit google search, seems MTU in wireguard setup plays a role also. https://gist.github.com/nitred/f16850ca48c48c79bf422e90ee5b9d95

[–] tychosmoose@lemm.ee 2 points 19 hours ago (1 children)

It's probably still IPv6 related. If you use something like Network Analyzer on your phone while only connected to the mobile network you may find that it only shows an IPv6 address and DNS server, no IPv4 config. That could explain the difference. Particularly if you were using the maximum typically permissible MTU. Your provider might also be doing some 6to4 tunneling somewhere that adds overhead and causes size problems.

[–] Hellmo_Luciferrari@lemm.ee 1 points 3 hours ago

Thank you for the info, I may try that out of curiosity