Wireguard VPN doesn't active through plugin about tunneldeck HOT 9 OPEN

I actually got it to work. Changed the settings for the vpn while in desktop mode to allow password for every user, or something similar, and it fixed the problem.

from tunneldeck.

When I press to trigger wireguard connection, switch changes its position to active meanwhile on server side I do not have connection. As soon as I reopen three point menu, switch returns to main position. Earlier have not tested if plugin works. Connection in desktop mode works

from tunneldeck.

When I press to trigger wireguard connection, switch changes its position to active meanwhile on server side I do not have connection. As soon as I reopen three point menu, switch returns to main position. Earlier have not tested if plugin works. Connection in desktop mode works

Have the same problem, only I can't even connect in desktop mode.

from tunneldeck.

@erbmur Are you able to let me know which version of SteamOS you're using and if possible, manually install 1.0.2 which was submitted today: SteamDeckHomebrew/decky-plugin-database#195

from tunneldeck.

Hi @steve228uk
Thanks for getting back to me. I was origonally on the beta branch, but moved back to stable. It wasn't working on either.
I am unsure as to how I would install the plugin manually.

from tunneldeck.

@erbmur 1.0.2 is now available on the Decky store. Does this problem persist?

from tunneldeck.

@steve228uk I can confirm the issue persists. Using Decky V2.7.0 and V1.0.2 TunnelDeck. Switching on the VPN 'toggles' on, but immediately toggles off upon closing out of the plugin screen and never actually takes effect. Interestingly enough, however, switching on wireguard manually through Desktop mode, the plugin does work for switching off the VPN connection.

from tunneldeck.

I can confirm this setting also resolved the issue for me! The setting was: store this password for all users (not encrypted). Thank you for sharing that fix

from tunneldeck.

Not to Necro this thread, but I had the same issue just now. Seems the KDE keyring isn't initialized in gaming mode, so any keys stored using it (i.e. the "encrypted" option) will not be available in gaming mode as well. Storing the private key (and preshared key, if applicable) in plaintext via the "all users" mode alleviates this issue.

It would be nice if the plugin could display an error popup if a wireguard connection fails to initialize. It looks like the stdout is already being captured in the python plugin. Change that to stderr and it shouldn't be too hard to implement. I'll try to open a PR when I get some time. :)

from tunneldeck.