Anecdotally after the most recent update, WireGuard seems to be having issues after a reboot of OPNsense now. WG clients aren't able to connect, I restart the WG service, and they're able to connect again. Easy to mitigate, but it's very manual intervention, and not sure why it started happening. Just thought I'd mention it.
Same here. I´ve seen this before (don´t remember the exact version numbers), and suddenly "it got fixed" in a later release, so I didn´t bother reporting it. But now it´s back with 24.7.7. What I can see in the WG logs after reboot is a log line like this (for an instance X), right after WG start:
2024-10-26T19:24:47 Notice wireguard wireguard instance X (wg0) can not reconfigure without stopping it first.
Then, after restarting the service manually, the issue is resolved. Same log content, except for the line above.
My setup is pretty straight forward, on bare metal. Single WG instance.
Exactly the same here, logs show the same. Restart helps.
No problem here, maybe you share a misconfiguration? Show what you can and also show your rule for the WireGuard port.
sorry to bring this up but I am having the same issue.
I am on the latest opnsense version, and using DDNS as hostname for wireguard
Got Adguard home running on opnsense
Was there a solution for this problem?
tried various scripts to restart wireguard but none of them worked, the only way to make it work is by logging into the opnsene gui and restarting the wireguard tunnel from the dashboard.
when i check the vpn > wireguard > status - seems it shows the wrong port/tunnel before i restart it from the gui, after the restart from gui, all works fine
Same problem even in most recent 25.7 version, after rebooting OPNsense, wireguard clients connect and make handshake but data only goes in one direction, clients send data but don't receive.
Only works if service is restarted using the dashboard (clicking in button restart) or cli using: configctl wireguard restart <name of instance>