-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Connect failed with Failed to write the VPN config
#29512
Connect failed with Failed to write the VPN config
#29512
Comments
Reopened as brave/brave-core#17927 doesn't fix this issue. |
❤️ |
Latest code changes did help narrow it down completely 😄 Huge thanks to @MadhaviSeelam for testing Here's the behavior we ultimately saw
At that point, @MadhaviSeelam checked and the folder is read-only and this is what seems to be preventing the file from being written. She changed this to NOT be read-only (unticking, clicking Next attempt at connecting worked great 😄 |
Verified using
Confirmed connected to VPN successfully and
|
Verification
|
Brave | 1.52.92 Chromium: 113.0.5672.92 (Official Build) beta (64-bit) |
---|---|
Revision | b6f521170062a1fa8a82c33fb223b06fec566da1-refs/branch-heads/5672_63@{#10} |
OS | Windows 10 Version 22H2 (Build 19045.2965) |
Steps (with credentials and Windows 10
filesystem Read-only
changes already made, from below):
- launched Brave
- connected to
Brave VPN
- confirmed I could switch server regions
- confirmed it wrote out to
rasphone.pbk
Confirmed I could connect to Brave VPN
, without crashing, even with the containing folder for rasphone.pbk
set to Read-only
example | example | example | example |
---|---|---|---|
Attempted to reproduce the issue using 1.49.118
and 1.51.110
Steps:
- installed
1.49.118
/1.51.110
- launched Brave
- restarted (to get Griffin changes)
- purchased, configured, and connected to
Brave VPN
- disconnected from
Brave VPN
- closed Brave
- set
rasphone.pbk
inC:\Users\steph\AppData\Roaming\Microsoft\Network\Connections\Pbk
toRead-only
- tried to reconnect
- confirmed I got the
Failed to write the VPN config.
error - set its containing folder also to
Read-only
- unset
Read-only
forC:\Users\steph\AppData\Roaming\Microsoft\Network\Connections\Pbk
- confirmed I was able to reconnect to
Brave VPN
No crashes, however.
example | example | example |
---|---|---|
Verification
Installed 1.52.93 *Still seeing 2023-05-10_15h03_37.mp4 |
QA passing this issue since #30291 filed as a follow up. |
Description
There was crash when creating os vpn entry with emtpy hostname at
brave_vpn::internal::CreateEntry()
.With brave/brave-core#17917, crash doesn't happen anymore.
But still have connect failed issue with
Failed to write the VPN config
due to empty hostname.backtrace links for crash
https://brave.sp.backtrace.io/p/brave/explore?time=month&aggregations=((callstack%2Chead))&fingerprint=329b1f29ef943e90d7cd52d791d30d622dbfba3f61034ca1e359831cb6a6ff65&
https://brave.sp.backtrace.io/p/brave/explore?time=month&aggregations=((callstack%2Chead))&fingerprint=115990e2619af1f1ac806aec7400f1ebb70b68b3f0932a6a8eacb9fa3c70aa24&
Steps to Reproduce
See #28940 for the STR
Actual result:
Recording from @MadhaviSeelam
2023-04-04_17h12_33.mp4
No more crash but connect failed.
Expected result:
Reproduces how often:
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
The text was updated successfully, but these errors were encountered: