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
It's not clear to me if this is default behavior, unintended, or even modified by Tunnel Deck at all but I note that when using the "+" under connections to "Import VPN Connection" at the bottom of the list, a standard no-nonsense Wireguard .conf file returns error "failed to import VPN connection: the file to import wasn't a valid OpenVPN client configuration". Is this meant to differentiate between Wireguard and Openvpn? Adding the connection manually as a Wireguard one will still probably work just fine, but this strikes me as inconvenient and slow for adding lots of pre-configured Wireguard config files.
The text was updated successfully, but these errors were encountered:
So i had this problem and the issue was that I downloaded the .conf file and tried to import it as it was, when I renamed it to something simple like steamdeck.conf it imported with no issue at all.
It's not clear to me if this is default behavior, unintended, or even modified by Tunnel Deck at all but I note that when using the "+" under connections to "Import VPN Connection" at the bottom of the list, a standard no-nonsense Wireguard .conf file returns error "failed to import VPN connection: the file to import wasn't a valid OpenVPN client configuration". Is this meant to differentiate between Wireguard and Openvpn? Adding the connection manually as a Wireguard one will still probably work just fine, but this strikes me as inconvenient and slow for adding lots of pre-configured Wireguard config files.
The text was updated successfully, but these errors were encountered: