←back to thread

All extensions disabled due to expiration of intermediate signing cert

(bugzilla.mozilla.org)
1318 points xvector | 3 comments | 04 May 19 01:31 UTC | HN request time: 0.416s | source
Show context
fnrslvr ◴[04 May 19 05:40 UTC] No.19824683[source]▶
Mozilla doesn't seem to have communicated the issue well. I could imagine a lot of unsavvy users have tried some wild things in an attempt to fix the problem, and maybe made a mess in the process. Doesn't Mozilla have a mechanism for blasting out a message to all Firefox browsers? Also I have a Firefox account, why haven't I been inboxed about this?

Otherwise I'm not bothered. I won't be switching as long as this gets resolved within the next few days.

replies(5): >>19824714 #>>19824763 #>>19824776 #>>19824785 #>>19824978 #
1. mirimir ◴[04 May 19 06:21 UTC] No.19824776[source]▶
https://twitter.com/mozamo

https://discourse.mozilla.org/t/certificate-issue-causing-ad...

replies(2): >>19824820 #>>19825071 #
2. pinjiz ◴[04 May 19 06:36 UTC] No.19824820[source]▶
> 429 Too Many Requests

Mozilla's discourse forum is now offline :)

3. fnrslvr ◴[04 May 19 07:54 UTC] No.19825071[source]▶
lol, both pivotal sources that I'll swiftly consult when something in my browser goes haywire.

Seriously though, when I checked the Mozilla and Firefox twitters (and I don't use twitter, so even going that far was a stretch for me) just before I wrote the parent post, they hadn't gotten around to tweeting a notice about this there, either. The Mozilla Add-ons twitter account is not the highest-level place that should be talking about this situation.