Chrome 53 breaks HTTPS Everywhere - gHacks Tech News

Chrome 53 breaks HTTPS Everywhere

If you are a Google Chrome user on the stable channel, you may have noticed that some of your extensions stopped working with the update to Chrome 53.

While any number of extensions may be affected by this, the issue has been confirmed for HTTPS Everywhere and Privacy Badger.

Here is what is happening:

The extensions install fine when you click on the install button on Google's official Chrome Web Store. You see the icon in the toolbar for a brief moment, but it is removed automatically after a second or so.

The extension is at that point no longer enabled, and you may verify that by opening the extensions manager in the browser. Load chrome://extensions/ in the browser's address bar to do so.

The same happens if the extension is already installed as it will show up as corrupted as well.

chrome extension corrupted

All affected extensions are listed as corrupted (This extension may have been corrupted). The only options you get for those extensions is to click on repair to try and resolve the issue, or to uninstall it from Chrome.

Repair attempts to install the extension again. First, it removes the installed copy of the extension. Once done, it attempts to reinstall the extension.

repair extension

This worked fine on a test system. The extension was listed as installed and enabled after the repair process finished.

reinstall chrome extension

It is unclear why extensions become corrupt after upgrading to Chrome 53. The issue was first reported on the HTTPS Everywhere Github page at the end of July. Users who reported the issue are also noticing it when running Dev versions of Google Chrome. This means that issue exists not only in Chrome 53 but also Chrome 54.

If you are using Google Chrome, you may want to check the status of all extensions installed in the web browser to make sure none has been deactivated silently in the background due to corruption.

Some users stated on Github that repairing did not resolve the issue for them.

Now You: Did you notice any corrupt extensions after upgrading to Chrome 53?

Summary
Chrome 53 breaks HTTPS Everywhere
Article Name
Chrome 53 breaks HTTPS Everywhere
Description
If you are a Google Chrome user on the stable channel, you may have noticed that some of your extensions stopped working with the update to Chrome 53.
Author
Publisher
Ghacks Technology News
Logo

We need your help

Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.

We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.

If you like our content, and would like to help, please consider making a contribution:

Comments

  1. Anonymous said on September 4, 2016 at 11:55 am
    Reply

    Interestingly, it works for me.

  2. Huub de Waard said on September 4, 2016 at 12:26 pm
    Reply

    It did not break down for me, it still works.

  3. Dan said on September 4, 2016 at 1:43 pm
    Reply

    It was “corrupted” in my Chrome install. I tried the “repair” it twice, even uninstalling it before the second try, and it was still not working/”corrupt”. So I uninstalled it again and downloaded the extension at EFF’s website. Now it’s back to normal. Life is good.

  4. CHEF-KOCH said on September 4, 2016 at 2:00 pm
    Reply

    Can’t confirm.

  5. Andrew K said on September 4, 2016 at 2:07 pm
    Reply

    I have the same problem with Privacy Badger. HTTPS Everywhere works fine.

  6. Ed Bilder said on September 4, 2016 at 2:15 pm
    Reply

    Still not workin’ here. No matter how hard I try: Not repairing, not uninstalling/reinstalling, not anything. Extension still down. Some alternative?

  7. broken said on September 4, 2016 at 3:24 pm
    Reply

    I noticed my incognito mode is broken now. It’s black everywhere, hardly can see anything

  8. RSSaddict said on September 4, 2016 at 3:57 pm
    Reply

    “Smart HTTPS” is better and much lighter than the resource hog HTTPS Everywhere (14mb vs 150mb on Google Chrome) also noticed HTTPSE has a bit higher CPU utilization when i open web pages.

    https://chrome.google.com/webstore/detail/smart-https/dmgoegolinaceglokfijjabfplickbgn?utm_source=chrome-ntp-icon

    (if i’m not wrong it’s also available on Firefox)

    1. ilev said on September 4, 2016 at 8:40 pm
      Reply
      1. FuzzyUnLogic said on September 4, 2016 at 9:10 pm
        Reply

        The first comment by [GnomeGo] it’s not true.

        I tested Smart HTTPS on DeviantArt and the website load in HTTPS just fine.

    2. ilev said on September 5, 2016 at 9:04 am
      Reply

      FuzzyUnLogic : The big problem with Smart HTTPS is that the extension is “White listing” Http sites , so when these sites switch to Https the browser will continue to connect with Http.

  9. Solidstate said on September 4, 2016 at 4:30 pm
    Reply

    Broke for me and the repair did not work.

  10. G00gle D0rker said on September 4, 2016 at 6:19 pm
    Reply

    Thank You, G00gle, now ALPHABET INCORPORATED:

    Alphabet Inc. is a holding company that gives ambitious projects the resources, ”’freedom”’, and focus to make their ideas happen — GOOGL – Alphabet Inc. NASDAQ

    Alphabet Inc. – Official Site
    abc.xyz

  11. ajthemacboy said on September 4, 2016 at 8:29 pm
    Reply

    This is a known issue. See here; https://github.com/EFForg/https-everywhere/issues/5874

    This is being worked on and is fixed for me in Chrome Dev.

  12. ilev said on September 4, 2016 at 8:32 pm
    Reply

    No problem with Chrome Version 53.0.2785.89 beta-m (64-bit) HTTPS Everywhere is active.

  13. geoff said on September 4, 2016 at 10:01 pm
    Reply

    It seems to me like it is either a Chrome-specific issue or it has been fixed. I’ve been using Chromium 55 and everything seems to be just fine.

  14. chesscanoe said on September 5, 2016 at 5:21 pm
    Reply

    All my Chrome extensions work well including Privacy Badger 2016.8.29 using Chrome Version 53.0.2785.89 m (64-bit) under latest Windows 10 x64 Home Anniversary Edition.

  15. Traveltravel said on September 5, 2016 at 6:54 pm
    Reply

    Hi

    Yes, the extension was indicated as corrupted when I installed it in Chrome v53. However, you can go to the developer’s website and install from there. It works fine for me

    https://www.eff.org/https-everywhere

  16. beergas said on September 6, 2016 at 1:40 pm
    Reply

    Oh crud, I had v 52.0.27 or some such and now the muther is d/ling the v53 it seems. Gonna be some major fup if this goes badly. Had an online bank let me login other day on Chrome but refuses to load up the details, transfers, bill payment fields. Just nothing. Ran Edge and boom right in as usual. Surprisingly Edge isn’t that heavy on ads running either, though now it accepts some ad blockers which helps. Also Time Warner cable’s webmail wouldn’t load the login page so had to use Edge on it. All that just last week. I was putting it down to TWC/Chart merger but no… TWC idiot squad tried to force me to go to IMAP from POP3 to “solve the recurring issue”. What a laugh.

  17. Anonymous said on September 7, 2016 at 2:00 pm
    Reply

    Installed from EFF and works fine

  18. bpphantom said on September 21, 2016 at 4:08 pm
    Reply

    Using Chrome 53.0.2785.116 m and it reports as corrupted. Repair did not resolve it, and installing from EFF directly gave the same issue. *glares at Google*

  19. daniel said on September 25, 2016 at 8:15 am
    Reply

    Same for me as reported above:

    It was “corrupted” in my Chrome 53 install. I tried to “repair” it four times, even uninstalling it before a new install, and it was still not working/”corrupt”.

    So I uninstalled it again and downloaded the extension at EFF’s website and did a manual install. Now it is working again.

    1. tod said on October 3, 2016 at 6:10 am
      Reply

      Thanks for the advice. I have it working now after reading your post. :)

    2. tod said on October 3, 2016 at 6:12 am
      Reply

      Thanks your post helped me fix it. :)

  20. tod said on October 3, 2016 at 6:03 am
    Reply

    It’s still working in Canary Build

  21. Andy said on October 7, 2016 at 9:56 am
    Reply

    Repair Failed
    Delete, re-install worked.
    Chrome Version 53.0.2785.116 m (64-bit)

  22. Nelson said on October 22, 2016 at 5:46 pm
    Reply

    eff worked like it was meant to, thanks a bunch

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

Please note that your comment may not appear immediately after you post it.