Tuesday's VPN Beta maintenance made a change that requires downloading a new VPN profile, as stated in Sonic's last status update. Linux users may notice that the new profile doesn't work when imported into NetworkManager.
The problem is that Sonic switched from OpenVPN's tls-auth feature to tls-crypt-v2, which is not correctly handled by NetworkManager's importer.
You can fix the imported profile with the nmcli command line tool. Here's what to type:
The entry might also be missing entirely, depending on how you imported the profile. In that case, you can add it by editing the connection in NetworkManager's GUI, and setting Advanced: TLS Settings: Mode: TLS-Auth. Then apply your change and fix it as described above.
The problem is that Sonic switched from OpenVPN's tls-auth feature to tls-crypt-v2, which is not correctly handled by NetworkManager's importer.
You can fix the imported profile with the nmcli command line tool. Here's what to type:
- nmcli connection edit <connection-name>
- goto vpn.data
- change
- move the cursor to the part that says tls-crypt, change it to tls-crypt-v2, and press Enter.
- back
- save
- quit
The entry might also be missing entirely, depending on how you imported the profile. In that case, you can add it by editing the connection in NetworkManager's GUI, and setting Advanced: TLS Settings: Mode: TLS-Auth. Then apply your change and fix it as described above.