flaminiom

Ugh! Figured it out after sufficiently banging my head against the wall. It was a firewall rule. The rule was activated a while ago, but this is the first time launching a VPN session with it in place. Which is a little weird because I guess it prevented the session handshake and it couldn't get off the ground. I didn't think of it because the change happened weeks ago. Anyway, I'll leave my post below for anyone in might help the future. My VPN for tunneled access for dockers suddenly stopped working. I had shut down to add a new drive and decided to change up my VPN config to a new server, which I do occasionally just because. The new config loaded, I flipped the active switch, but I have no access on that network. It says Last Handshake: Not connected and it sends a few kb and nothing received. I tried testing with a Firefox container and nothing. Also tried pinging 8.8.8.8 in the console of the container and nothing. I can successfully ping the peer endpoint. Peer tunnel address fails. Not sure if it matters, but I accidentally hit tunneled access for system when adding that new config. Could something there have made it go loopy? I'm using IPv4 only. I tried creating new configs, different servers. I tried the config file for the server that was just working for me and nothing. I tried going into /host/config and deleting everything in wireguard. I tried adding a config for Proton VPN which also worked for me in the past and that doesn't work either. I tried flipping it on/off countless time. I tried rebooting a few times. The log seems to indicate the VPN starts with no other entries. Nov 28 09:20:06 XXXXXX wireguard: Tunnel WireGuard-wg0 started Nov 28 09:20:06 XXXXXX network: update services: 1s Any suggestions or an approach to troubleshoot?