You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have previously used this wireguard-kmod module with my UDM Pro for a long time, and I was very happy with it.
However, recently I've updated my unifi OS to 3.X from 1.X and then from 2.X, and my wireguard installation seems to have become borked.
I can not access my wireguard network anymore from any of my devices... Which means, I can not access any of my TrueNAS files from outside of my network anymore.
Are there specific steps I need to take before upgrading from 1.x to 2.x and then 3.x in order for this not to go wrong?
Are there any steps I can take to fix the current issues and still be able to use wireguard? I'm fine with using the built-in wireguard module and removing this one, but I'm not quite sure how I should go about doing that.
The text was updated successfully, but these errors were encountered:
Simbaclaws
changed the title
Wireguard stopped working after installing wireguard-kmod and then upgrading to 2.X
Wireguard stopped working after installing wireguard-kmod and then upgrading to 3.X
May 11, 2023
Hi there,
I have previously used this wireguard-kmod module with my UDM Pro for a long time, and I was very happy with it.
However, recently I've updated my unifi OS to 3.X from 1.X and then from 2.X, and my wireguard installation seems to have become borked.
I can not access my wireguard network anymore from any of my devices... Which means, I can not access any of my TrueNAS files from outside of my network anymore.
Are there specific steps I need to take before upgrading from 1.x to 2.x and then 3.x in order for this not to go wrong?
Are there any steps I can take to fix the current issues and still be able to use wireguard? I'm fine with using the built-in wireguard module and removing this one, but I'm not quite sure how I should go about doing that.
The text was updated successfully, but these errors were encountered: