Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some VPN customers on Windows are having the error "Failed to write the VPN config" #31729

Closed
bsclifton opened this issue Jul 19, 2023 · 3 comments
Labels
bug closed/stale Issue is no longer relevant, perhaps because the feature it refers to has been deprecated. feature/vpn OS/Desktop OS/Windows priority/P3 The next thing for us to work on. It'll ride the trains.

Comments

@bsclifton
Copy link
Member

Description

Some VPN customers are getting an error on Windows when they pick a server and the config is written (using RAS on Windows, for the IKEv2 connection).

One workaround we've had in the past is to either go to VPN on system and clear all connections OR delete the rasphone.pbk file located at %APPDATA%\Microsoft\Network\Connections\Pbk. Sometimes a reboot is required. However, this has not been working for affected customers.

Folks affected seem to be an admin on the machine. PowerShell sets some of the IKEv2 connection params:
#30904

However, if it fails there would still be evidence of a connection (ex: there would be an entry in %APPDATA%\Microsoft\Network\Connections\Pbk). In the reported cases, there is nothing there.

Steps to Reproduce

Unknown - need more help here

Actual result:

image

Expected result:

The config should have permission to write. If we have a way to capture and display the error, we should show that

@bsclifton
Copy link
Member Author

Will become less of an issue as we move towards WireGuard on Windows. See #29253

@Shznakl
Copy link

Shznakl commented Jul 25, 2023

We have tagged 26 tickets with this error. Most have closed due to no reply from the customer. This is seen on Windows 10 and Windows 11.

@Shznakl
Copy link

Shznakl commented Aug 2, 2023

Confirmed with one customer that the steps below do not resolve the issue either.

Please try to connect the Brave VPN once more and even when you receive the error message, then kindly use these steps to see if you are able to resolve this error message.

  1. Press the Windows key and type: Find and Fix network problems
  2. Please click on the option that comes up in the Control Panel.
  3. Select Troubleshoot my connection to the Internet

Result: it completed and said it did not detect any issues. The VPN was still unable to activate so there was otherwise no issues with my internet connection.

@mattmcalister mattmcalister added the priority/P3 The next thing for us to work on. It'll ride the trains. label Apr 22, 2024
@mattmcalister mattmcalister added the closed/stale Issue is no longer relevant, perhaps because the feature it refers to has been deprecated. label Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug closed/stale Issue is no longer relevant, perhaps because the feature it refers to has been deprecated. feature/vpn OS/Desktop OS/Windows priority/P3 The next thing for us to work on. It'll ride the trains.
Projects
None yet
Development

No branches or pull requests

3 participants