It seems I am not the first one to report on very unfortunate way of co-existence of 2 plugins in Chrome
https://github.com/EFForg/https-everywhere/issues/7224
but may I ask again, why does this conflict happen? Are 2 plugins irreplaceable by each other or not?
What OS/SP ?
What exact version of avast ?
Avast 12.3.2280.
Windows 10 Home 64-bit
Chrome 54.0.2840.71 m
Does it also happen in other browsers ?
Since avast scans all internet HTTP and HTTPS traffic. My only assumption is it is getting in the way when avast is trying to scan http traffic and https everywhere it is trying to force https connections.
Personally I wouldn’t use https everywhere as you are forcing http sites that aren’t geared up for https connections to do so.