-
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
Choose new server throws Can't connect to server
error in both profile 1 and profile 2
#25789
Comments
Verified the issue again, the issue happens on the Profile1 also when user tries to connect the new server. |
Can't connect to server
error Can't connect to server
error in both profile 1 and profile 2
Can't connect to server
error in both profile 1 and profile 2Can't connect to server
error in both profile 1 and profile 2
I suspect that this failure comes from vpn disconnect before starting re-connect to new region. When failure happens, vpn service can't fetch new credentials from guardian. Maybe disconnect could make network unavailalbe shortly. issue: brave/brave-browser#25789
fix brave/brave-browser#25789 Initially vpn state was per-profile. However, we decided to share vpn state between all profiles. With this change, one profile can have same vpn status if other profile is purchased user. So far vpn service manages two states. The one is purchased state and the other is connection state. Purchased state is still per-profile because skus service is per profile. Although purchased state is managed by each profile, same state is shared for all profiles eventually because skus service's internal data is global. In this PR connection state managing is moved from per-profile vpn service to BraveVPNOSConnectionAPI global instance. Before this PR, BraveVPNOSConnectionAPI didn't have state and only provided abstract interface for os dependent vpn command such as connect or disconnect. In the os system, there is only one connection state. So, connection state also should be managed globally. With that each profile can see same connection state.
The above requires |
@kjozwiak correct afaik, have added |
The issue is still reproducible in the following build hence opened a new follow up issue #26857. Hence marked this issue as QA/No
|
Description
Choose other server in Profile 2 throws
Can't connect to server
errorSteps to Reproduce
Pre-requisites: Enable sku and vpn flags via brave://flags and purchase a vpn
Singapore
)Singapore
Can't connect to server
error is shownCan't connect to server
error is shownActual result:
Choose other server in Profile 2 throws
Can't connect to server
errorExpected result:
Should not throw any error
Reproduces how often:
Easy
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc: @brave/qa-team @bsclifton @spylogsster @mattmcalister
The text was updated successfully, but these errors were encountered: