yegor 0 Posted November 29, 2018 Share Posted November 29, 2018 Extension: https://chrome.google.com/webstore/detail/windscribe-free-vpn-and-a/hnmpcagpplmpfojmgmnngilcnanddlhb?hl=en With SSL scanning enable (default option), loading any website with the extension enabled and proxy loaded results in ERR_SPDY_PROTOCOL_ERROR in the browser. Disabling the feature fixes the issue. This started happening in the last several days, so it sounds like a botched definition update. Link to comment Share on other sites More sharing options...
zijuwonness 0 Posted December 4, 2018 Share Posted December 4, 2018 I have the same problem. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted December 4, 2018 Administrators Share Posted December 4, 2018 I'm unable to install the extension to reproduce the issue. Getting the error below: Link to comment Share on other sites More sharing options...
AdamM 0 Posted December 4, 2018 Share Posted December 4, 2018 Try Firefox (or Vivaldi, or Opera with enabled "Install Chrome Extensions" extension), the problem is same. :) Link to comment Share on other sites More sharing options...
yegor 0 Posted December 4, 2018 Author Share Posted December 4, 2018 Some problem on your computer, as over 10,000 people install it daily. I'm guessing ESET Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted December 4, 2018 Administrators Share Posted December 4, 2018 Please check if enabling pre-release updates in the advanced update setup make a difference. I have no problem browsing in Firefox. Link to comment Share on other sites More sharing options...
yegor 0 Posted December 4, 2018 Author Share Posted December 4, 2018 Issue was reproducible in Google Chrome. Will test what you said shortly. Link to comment Share on other sites More sharing options...
AdamM 0 Posted December 4, 2018 Share Posted December 4, 2018 Tested on chrome, vivaldi, opera, firefox. Tested with enabled pre-release updates. The problem persists. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted December 4, 2018 Administrators Share Posted December 4, 2018 What am I doing differently then? Link to comment Share on other sites More sharing options...
yegor 0 Posted December 4, 2018 Author Share Posted December 4, 2018 Pre-release update channel appears to have resolved the issue. Can no longer reproduce. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted January 15, 2019 Administrators Share Posted January 15, 2019 On 12/5/2018 at 12:23 AM, yegor said: Pre-release update channel appears to have resolved the issue. Can no longer reproduce. Please test it with the Internet protection module 1356 which is going to be put on pre-release servers momentarily. The module that has been available since Dec had the HTTP/2 parser disabled because of that and now we have re-enabled it after fixing the issue. Link to comment Share on other sites More sharing options...
Recommended Posts