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

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.

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?

There was an openSUSE suggestion, just a note that default install adds a lot of packages, at the preinstall summary you can click the software title and unchecke patterns you don’t want, or go into further detail and check/uncheck single packages. You can make OpenSUSE as minimal as you like.

I assume being the extreme level coder dev types that program logic all day start seeing life has black and white, and generally humans are not like that.

Yeah, I was going to leave it for the joke, but changed it.

I can’t answer the main question, but anecdotally I find different distros work differently on different hardware. Like one laptop I have will not install, or if it does install it won’t boot, any Debian based distro, but RPM based is fine. There is some bios bug or quirk that fails with deb, but rpm distros acknowledge and move on. So sometimes distro hopping can help.