`Can't connect to server` error trying to enable and connect to VPN, after successfully fetching credentials

Description

Can't connect to server error trying to enable and connect to VPN, after successfully fetching credentials

Steps to Reproduce

1. delete any BraveVPN OS-configs, first
2. install 1.47.81
3. launch Brave using --vmodule="*/skus/*"=2 --enable-logging=stdrr --v=1
4. click Maybe later
5. click Skip welcome tour
6. open brave://flags
7. set brave://flags/#brave-vpn to Enabled
8. click Relaunch (if you want to retain logging, CTRL+C and relaunch from Terminal/console
9. click No thanks on the Tired of cookie consent notices? dialog
10. load account.bravesoftware.com
11. enter staging credentials from 1Password
12. enter a unique email address such as "[e-mail]" or similar
13. click Get login link
14. open the Log in to your Brave Pre... email (https://www.mailinator.com/v4/public/inboxes.jsp?to=unique99 in the above case)
15. click on either the Log in to Brave button -or- the link below it
16. click Browse plans on https://account.bravesoftware.com/account/
17. scroll down
18. click on Buy now beneath Brave VPN Subscription
19. complete the Stripe checkout using https://stripe.com/docs/testing#testing-interactively
20. click on the VPN button in the browser toolbar, and attempt to add and connect to the BraveVPN config

Actual result:

chrome_debug.log

Expected result:

Able to connect to Brave VPN after purchase + successful credentials loading

Reproduces how often:

100% for me

Brave version (brave://version info)

Brave	1.47.81 Chromium: 108.0.5359.40 (Official Build) nightly (64-bit)
Revision	280b5fcaab3e877562b06cfaf2eb51121e13c3b9-refs/branch-heads/5359@{#689}
OS	Windows 10 Version 22H2 (Build 19045.2311)

Version/Channel Information:

• Can you reproduce this issue with the current release? n/a
• Can you reproduce this issue with the beta channel? yes
• Can you reproduce this issue with the nightly channel? yes

/cc @mattmcalister @bsclifton @spylogsster @LaurenWags @MadhaviSeelam @GeetaSarvadnya @rebron @srirambv

[spylogsster]

I have followed the steps from the STR. I am not getting this issue in my Windows 10 x64 on top of master branch. I guess this could be related to the server side state.

[stephendonner]

@mattmcalister @bsclifton @rebron @LaurenWags @brave/user-support-team @MadhaviSeelam @GeetaSarvadnya

We’ll want to document this and investigate/mitigate further, I believe.

But some good-ish news: got my Windows 10 setup working again, and verified a full end-to-end flow (once fixed) with the following build:

Reproduced the issue, and re-verified my environment as fixed, using the same Brave build (confirming code outside of our control):

Brave	1.46.114 Chromium: 107.0.5304.110 (Official Build) beta (64-bit)
Revision	2a558545ab7e6fb8177002bf44d4fc1717cb2998-refs/branch-heads/5304@{#1202}
OS	Windows 10 Version 22H2 (Build 19045.2311)

Non-fix “fix”:

In the end, I “fixed” this and achieved the above expected result by following the (full) steps on https://github.com/trailofbits/algo/issues/1051, summarized here:

• clear networking caches; ran all as Administrator in elevated command console:
  • netsh int ip reset
  • netsh int ipv6 reset
  • netsh int winsock reset
• reset Device-Manager adaptors
  • open Device Manager
  • open Network Adapters
  • uninstall each of the WAN Miniport drivers
  • click Action -> Scan for hardware changes
  • ensure you see the above-removed adapters repopulated
• restart Windows
• remove previous attempt’s BraveVPN config
• restart Windows

Confirmed I could now purchase, configure, and use BraveVPN

error	BraveVPN config	another valid BraveVPN config	BraveVPN removal	success