OPNsense Forum

English Forums => Virtual private networks => Topic started by: RamSense on November 23, 2022, 07:56:22 pm

Title: [SOLVED] WG suddenly doesnt finish handshakes after updating adguard home
Post by: RamSense on November 23, 2022, 07:56:22 pm
strange things here.... I have, for more than 1 year, been running Wireguard without any problems.
I also have Adguard Home Running. As soon as i updated to v0.107.19 my WG devices can't load data / internet etc. lost connection
In the WG app on the iphone I see this in the log:
Handshake did not complete after 5 seconds, retrying (try 2)
2022-11-23 19:53:17.375
[NET] peer(TX....) - Sending handshake initiation
2022-11-23 19:53:22.473
[NET] peer(TX....) - Handshake did not complete after 5 seconds, retrying (try 3)

I can't understand what is going wrong. Rebooted the opnsense box just in case, but no change in result.
Others having problems with WG and or after updating Adgusad Home v0.107.19 ??

Help is really appreciated
Title: Re: WG suddenly doesnt finish handshakes after updating adguard home to v0.107.19
Post by: mimugmail on November 23, 2022, 09:38:27 pm
You can remove the plugin and install again to downgrade and test again
Title: Re: WG suddenly doesnt finish handshakes after updating adguard home to v0.107.19
Post by: RamSense on November 23, 2022, 10:14:11 pm
thnx, i tried it. removed adguard home, and installed it again. Now I am back to v0.107.15

But it is still not working. And I know for sure updating Adguard home was the only thing I did....

When rebooting the opnsense box again and looking at the log - web gui, i noticed this what i think was not there before. Maybe related?

Error   lighttpd   (configfile.c.1287) WARNING: unknown config-key: server.dir-listing (ignored)   
Error   lighttpd   (mod_deflate.c.803) DEPRECATED: compress.cache-dir replaced with deflate.cache-dir   
Error   lighttpd   (mod_deflate.c.740) DEPRECATED: compress.filetype replaced with deflate.mimetypes
Title: Re: WG suddenly doesnt finish handshakes after updating adguard home to v0.107.19
Post by: RamSense on November 24, 2022, 08:19:50 am
  :-[
found it.... It was a problem at my ISP side.... happend just at the same time as the adguard home update... grmbl... took me a day to check. First time again I'll start with my isp checking instead of my config :-)