You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are happy to answer your questions about the code or discuss technical ideas.
Please complete the following checklist (by adding [x]):
[ x] I have searched open and closed issues for duplicates
[ x] This isn't a feature request
[ x] This is not a report about my app not working as expected
I was testing the robustness of proton VPN web filter avoidance, and I came across an interesting scenario:
When proton VPN connects from Chrome OS on a network filtered by Fortiguard with standard anti-VPN configuration, it can bypass it with no problem. HOWEVER, if you put the Chromebook to sleep (close the lid) with the connection severed, you get failed connections and a lot of interesting log reports about a failed handshake due to a closed network connection. Do you have any idea why this might happen?
Please complete the following checklist (by adding [x]):
I was testing the robustness of proton VPN web filter avoidance, and I came across an interesting scenario:
When proton VPN connects from Chrome OS on a network filtered by Fortiguard with standard anti-VPN configuration, it can bypass it with no problem. HOWEVER, if you put the Chromebook to sleep (close the lid) with the connection severed, you get failed connections and a lot of interesting log reports about a failed handshake due to a closed network connection. Do you have any idea why this might happen?
Log file:
protonvpn_7497251493884640209.log
The text was updated successfully, but these errors were encountered: