Issue metadata
Sign in to add a comment
|
Attempts to turn on a VPN fail, whether by entering credentials manually in settings, or by using a VPN App
Reported by
annahuan...@gmail.com,
May 1 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9334.58.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.89 Safari/537.36 Platform: ASUS C302CA Steps to reproduce the problem: 1. Enter L2TP Credentials in settings 2. OR Install A VPN from then APP Store (tested with blackvpn and expressvpn apps). 3. What is the expected behavior? VPN should connect and change IP address when requested. What went wrong? 1) If L2TP Credentials are entered manually, request to connect will fail with "Internal Error", and eventually a "Network Connection Error" 2) If a VPN app is installed and activated, when a server connection is requested, the App will report that it is successfully connected. However, the IP Address will NOT actually change. Did this work before? Yes Not sure, but I have seen reports from users on forums using VPNs on Chromebooks in the past. Chrome version: 58.0.3029.89 Channel: beta OS Version: 9334.58.0 Flash Version: Shockwave Flash 25.0 r0 This is a VERY SEROUS problem for 2 reasons. First, VPN is a missiopn critcal application for many Chromebook users. 2) VPN Apps will "appear" to be connected, giving a false sense of security that the VPN is connected when it is not. (Both blackvpn and expressvp will give instant trials from within the app to use for testing purposes). While there are other VPN problem reports, this is new in that VPN functionality is not working at all, manually or by App. I have also tested/verified this behavior in the Stable Channel.
,
May 1 2017
I have done further testing, and found that the L2TP connection problem (#1) above is intermittent, and not always reproducible. However, Apps reporting that they are connected, but not actually being connected is reproducible. In addition, it is NOT an App/vendor specific problem, as it occurs in multiple Apps across multiple vendors, suggesting a fundamental problem in the way VPN Apps interact with Chrome OS.
,
May 1 2017
More testing on the most significant issue: that VPN Apps are reporting they are connected, but in fact, are not Both VPN Apps used for testing (expressvpn and blackvpn) DO connect to VPN servers correctly (and change the IP) on the latest version of Android on a Nexus 6P. The issue on Chromebook OS is 100% reproducible by installing the App, enabling an instant trial account, connecting, and then running iplocation.net to see that the location has not changed.
,
May 1 2017
Same issue here. I cannot get any VPN to properly connect. Most report as connected, but are not. Some just hang, and never connect.
,
May 1 2017
I am an ExpressVPN user on Chromebook. I THOUGHT it was working fine. However, after seeing a post in the forums and this report, I tested my IP. All this time, the VPN has NOT been connecting! Apparently, this bug is affecting all VPN Apps. Be very careful; many act like Expressvpn and appear to be connected. I retested Expressvpn (and the others) and they all connect properly on my Samsung Phone.
,
May 2 2017
It appears that the VPN Apps that are failing are trying to connect with Openvpn protocol.
,
May 5 2017
Further testing shows that Other Browsers (e.g. Firefox) WILL change IP's with VPN Apps., but the Chrome Browser will not.
,
Jun 13 2017
,
Jun 15 2017
My OpenVPN connection has stopped working and now gives "Internal Error". I am on Version 60.0.3112.26 (Official Build) beta (64-bit)
,
Feb 28 2018
,
Dec 7
Hello! This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time. - If you are currently working on this bug, please provide an update. - If you are currently affected by this bug, please update with your current symptoms and relevant logs. If there has been no updates provided by EOD Wednesday, 12/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary. Thank you!
,
Dec 13
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by leonstev...@gmail.com
, May 1 2017