It makes little sense why it works on an offsite WiFi, but not mobile data.
I’d agree with unbuckled above, it’s a DNS issue. If your mobile device is capable, use nslookup or dig to see what responses you are getting in different scenarios. It’s possible that your VPN software is leaking DNS queries out to the mobile data provider’s DNS servers while you are on mobile data and only using the correct DNS settings when you are on wifi. Possibly look for split tunnel settings in the VPN software, as this can create this type of situation.
You can also confirm this from the pihole side. Connect to the VPN via mobile data and browse to some website you don’t use often, but is not your own internal stuff. Then open the query log on your pihole and see if that domain shows up. I’d put money on that query not showing in the pihole query log.
I turned on query logging for my PiHole. I chose a random site I don’t typically browse, and confirmed I saw it logged in my PiHole. Though, I am thinking it’s likely DNS that’s causing issues.
I even tried turning off split tunneling, and it does the same thing.
I checked automatic DNS setting on my phone.
I don’t know if it will make a difference but the DNS records for my local services are CNAME records, so I am going to change it to an A/AAAA record on PiHole.
I don’t have a lot of networking skill here, but could it be your WiFi connections (anywhere) are IPv4 and on mobile it forces IPv6, thus why you can connect via IP:port?
Typically your wireguard host machine has IP forwarding/masquarading setup so you can reach your home LAN. Could this be an issue through the router / proxy?
Hellmo_Luciferrari@lemm.ee 1 week ago
I have DNS handled by my PiHole (using unbound as-can upstream DNS)
On my PiHole, I have an A record for the docker box, and then CNAME records pointing to the A name record.
It makes little sense why it works on an offsite WiFi, but not mobile data.
sylver_dragon@lemmy.world 1 week ago
I’d agree with unbuckled above, it’s a DNS issue. If your mobile device is capable, use nslookup or dig to see what responses you are getting in different scenarios. It’s possible that your VPN software is leaking DNS queries out to the mobile data provider’s DNS servers while you are on mobile data and only using the correct DNS settings when you are on wifi. Possibly look for split tunnel settings in the VPN software, as this can create this type of situation.
You can also confirm this from the pihole side. Connect to the VPN via mobile data and browse to some website you don’t use often, but is not your own internal stuff. Then open the query log on your pihole and see if that domain shows up. I’d put money on that query not showing in the pihole query log.
Hellmo_Luciferrari@lemm.ee 1 week ago
I turned on query logging for my PiHole. I chose a random site I don’t typically browse, and confirmed I saw it logged in my PiHole. Though, I am thinking it’s likely DNS that’s causing issues.
I even tried turning off split tunneling, and it does the same thing.
I checked automatic DNS setting on my phone.
I don’t know if it will make a difference but the DNS records for my local services are CNAME records, so I am going to change it to an A/AAAA record on PiHole.
I have these set in PiHole and not my Unbound.
Strit@lemmy.linuxuserspace.show 1 week ago
In that case, are you sure the VPN is actually on, when on cellular?
Hellmo_Luciferrari@lemm.ee 1 week ago
Absolutely, I can connect to the services via IP:Port
BCsven@lemmy.ca 1 week ago
I don’t have a lot of networking skill here, but could it be your WiFi connections (anywhere) are IPv4 and on mobile it forces IPv6, thus why you can connect via IP:port? Typically your wireguard host machine has IP forwarding/masquarading setup so you can reach your home LAN. Could this be an issue through the router / proxy?
Strit@lemmy.linuxuserspace.show 1 week ago
Beats me then. Network wise an external Wifi should follow the same rules as an external cellular connection.