HTTPS Protocol error with Ghostery

[calvinthefreak]

If I use D.Tube, I get certain problem because the gateways are https ones... but my local one does not understand HTTPS... but the companion ext is still redirecting with https protocol in version 2.2.1 for chrome.

(I did setup my own gateway with an http in the companion config.)

[lidel]

Interesting: I am unable to replicate this with v2.2.1: both Firefox and Chrome redirect and load content fine using a LAN IP of my non-HTTPS gateway.

I think what may be happening is some other extension or userscript is interfering with your requests, replacing HTTP ones with HTTPS.

Are you able to replicate with no other extensions and userscripts running?
Try running test with chrome --user-data-dir=$(mktemp -d) for empty profile.

[calvinthefreak]

Ok, for all of us, that R using Ghostery addon, whitelist your Domains for IPFS... this did the Trick for me, because I found out that ghostery has an int. http to https.

[lidel]

Thank you @calvinc64.

I've added a note about it to our README.

ps. I looked at it closer and Ghostery provides no documentation nor controls to disable this forced protocol upgrade. I think it is a bug – filled an upstream issue: ghostery/ghostery-extension#44