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
I am unable to connect to any endpoints following an update to v2.1.0.
Steps to reproduce
(Please provide detail steps).
Ensure that the extension is up to date.
Try to connect to an endpoint.
Wait for a minute or two, or however long it is before you get bored.
Try to connect to a different location.
GOTO 3.
What is the current bug behaviour?
(What actually happens).
I am unable to connect. If I choose a different location, I get the following error in the console:
Uncaught (in promise) TypeError: Invalid invocation at chrome-extension://jplnlifepflhkbkgonidnobkakhmpnmh/js/background.js:5869
Full error information is below.
What is the expected correct behaviour?
(What you should see instead).
I should be able to connect to the VPN.
Relevant logs and/or screenshots
The below comes from the console.
foreground.js:8117 Uncaught (in promise) TypeError: Invalid invocation
at chrome-extension://jplnlifepflhkbkgonidnobkakhmpnmh/js/background.js:5869
at new Promise (<anonymous>)
at proxy_BrowserProxy.set (chrome-extension://jplnlifepflhkbkgonidnobkakhmpnmh/js/background.js:5867)
at proxy_BrowserProxy.enable (chrome-extension://jplnlifepflhkbkgonidnobkakhmpnmh/js/background.js:6182)
at RegionListItem_RegionListItem.onClick (foreground.js:8117)
at Object.ca (foreground.js:3023)
at ja (foreground.js:3024)
at ka (foreground.js:3024)
at wa (foreground.js:3026)
at Aa (foreground.js:3027)
(anonymous) @ chrome-extension://jplnlifepflhkbkgonidnobkakhmpnmh/js/background.js:5869
set @ chrome-extension://jplnlifepflhkbkgonidnobkakhmpnmh/js/background.js:5867
enable @ chrome-extension://jplnlifepflhkbkgonidnobkakhmpnmh/js/background.js:6182
onClick @ foreground.js:8117
ca @ foreground.js:3023
ja @ foreground.js:3024
ka @ foreground.js:3024
wa @ foreground.js:3026
Aa @ foreground.js:3027
ya @ foreground.js:3027
Da @ foreground.js:3030
Ad @ foreground.js:3093
Gi @ foreground.js:3259
Kb @ foreground.js:3048
Dd @ foreground.js:3095
(anonymous) @ foreground.js:3260
exports.unstable_runWithPriority @ foreground.js:3315
Ii @ foreground.js:3260
Cd @ foreground.js:3094
async function (async)
onClick @ foreground.js:8117
ca @ foreground.js:3023
ja @ foreground.js:3024
ka @ foreground.js:3024
wa @ foreground.js:3026
Aa @ foreground.js:3027
ya @ foreground.js:3027
Da @ foreground.js:3030
Ad @ foreground.js:3093
Gi @ foreground.js:3259
Kb @ foreground.js:3048
Dd @ foreground.js:3095
(anonymous) @ foreground.js:3260
exports.unstable_runWithPriority @ foreground.js:3315
Ii @ foreground.js:3260
Cd @ foreground.js:3094
The extension debug log produces the following output over and over again.
exclusions value: [object Object]
typeof exclusions: object
https-upgrade/rulesets#applyRuleset: invalid exclusions
https-upgrade: secured cookie "ecos.dt" for ".www.bbc.co.uk"
https-upgrade: attempting to secure cookie: ecos.dt
https-upgrade: secured cookie "ecos.dt" for ".www.bbc.co.uk"
https-upgrade: attempting to secure cookie: ecos.dt
https-upgrade: secured cookie "ecos.dt" for ".www.bbc.co.uk"
https-upgrade: attempting to secure cookie: ecos.dt
https-upgrade: secured cookie "ecos.dt" for ".www.bbc.co.uk"
https-upgrade: attempting to secure cookie: ecos.dt
Please update to the latest release (2.1.1). We think we've solved the issue in that release. If not, please let us know, by adding another copy of the error from the console logs here. Thank you!
Summary
I am unable to connect to any endpoints following an update to v2.1.0.
Steps to reproduce
(Please provide detail steps).
GOTO 3
.What is the current bug behaviour?
(What actually happens).
I am unable to connect. If I choose a different location, I get the following error in the console:
Uncaught (in promise) TypeError: Invalid invocation at chrome-extension://jplnlifepflhkbkgonidnobkakhmpnmh/js/background.js:5869
Full error information is below.
What is the expected correct behaviour?
(What you should see instead).
I should be able to connect to the VPN.
Relevant logs and/or screenshots
The below comes from the console.
The extension debug log produces the following output over and over again.
Possible fixes suggested remediation
Assignees and labels
( please add labels as applicable )
~bug ~confirmed
~feature ~suggestion
~Windows ~Linux ~OSX
~Emergency ~Major ~Minor
%"milestone"
/cc @dev /assign @tester
The text was updated successfully, but these errors were encountered: