Mozilla/5.0 (X11; Linux x86_64; rv:13.0a1) Gecko/20120202 Firefox/13.0a1 Start with a clean profile. 1. Open the addon manager. 2. Select the Plugins pane 3. Click "Check to see if your plugins are up to date". Previously, this would list your plugins and show a status for each one, such as "Up to date", "Out of date (vulnerable)", "Out of date (not vulnerable)" or "Unknown". Now it just shows: -------- Plugin Finding Service Error We've encountered an error. Please try your request again later. -------- There are no errors in the error console other than about CSS and web fonts. I'm not sure if this depends on the set of plugins that are enabled or not. I'll test that in a moment. I think this is quite an important feature because it allows users to quickly see if they have plugins with known security vulnerabilities.

Confirmed on today's moz central nightly build

That's a win32 build on win 7 32bit.

It seems that this is actually not a regression from bug 90268. It looks like a website problem. After loading the page and seeing the error, changing from https:// to http:// makes the page work.

works for me, the Plugin Finding Service Error etc is normally a temporary error. Does the site works for you guys again?

Still not working. Might be ABP/NoScript related?

(In reply to Carsten Book [:Tomcat] from comment #4) > works for me, the Plugin Finding Service Error etc is normally a temporary > error. Does the site works for you guys again? No, the site still doesn't work with https: but does work with http:. (In reply to DB Cooper from comment #5) > Still not working. Might be ABP/NoScript related? DB, comment 0 says start with a clean profile. This is reproducible without any extensions. Could it be related to this?: -------- https://plugins.stage.mozilla.com/ This Connection is Untrusted You have asked Nightly to connect securely to plugins.stage.mozilla.com, but we can't confirm that your connection is secure. Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified. What Should I Do? If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue. Technical Details plugins.stage.mozilla.com uses an invalid security certificate. The certificate expired on 01/11/11 19:31. The current time is 03/02/12 11:21. (Error code: sec_error_expired_certificate) -------- I'm pretty sure I've seen it working since November though... Regardless, that's something that needs fixing isn't it?

I can confirm the error. (In reply to Daniel Cater from comment #6) > Could it be related to this?: > > -------- > https://plugins.stage.mozilla.com/ > > This Connection is Untrusted Sounds like it.

yeah i can reproduce the problem now on 1 of 2 maschines here - very odd :(

really not sure if its related to the ssl cert because in my case its working on a other maschine (with same location etc) but we had issues with plugincheck in the past see https://bugzilla.mozilla.org/show_bug.cgi?id=675426

over to server ops to investigate. Guys can you take a look at the plugincheck system?

pfs is referring to plugins.stage.mozilla.com instead of the production site plugins.mozilla.org. This is from webdev console (Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0) Gecko/20100101 Firefox/10.0): [19:47:21.313] GET https://plugins.stage.mozilla.com/pfs/v2?appID=%7Bec8030f7-c20a-464f-9b0e-13a3a9e97384%7D&appRelease=10.0&appVersion=20120123235200&clientOS=Intel+Mac+OS+X+10.7&chromeLocale=en-US&detection=version_available&mimetype=application%2Fphoto&callback=C [undefined 682ms] [19:47:22.043] Error Type [ error ] retrying on mime/plugin ({callback:"C", url:"https://plugins.stage.mozilla.com/pfs/v2", cache:true, callbackParameter:"callback", data:{appID:"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}", appRelease:"10.0", appVersion:"20120123235200", clientOS:"Intel Mac OS X 10.7", chromeLocale:"en-US", detection:"version_available", mimetype:"application/photo"}, error:(function () {that.pfs2Error.apply(that, arguments);}), retry:0, success:(function () {that.pfs2Success.apply(that, arguments);}), timeout:3000, abort:(function () {clearTimeout(timeoutTimer);document.open();removeVariable(errorCallbackName);removeVariable(successCallbackName);document.write(empty);document.close();frame.remove();})}) error undefined application/photo ({plugin:(void 0), mimes:["application/photo"], detection_type:"version_available", classified:false, raw:({}), detected_version:"7.0"}) @ https://www.mozilla.org/js/plugincheck.js:3489

(In reply to Carsten Book [:Tomcat] from comment #9) > really not sure if its related to the ssl cert because in my case its > working on a other maschine (with same location etc) but we had issues with > plugincheck in the past see > https://bugzilla.mozilla.org/show_bug.cgi?id=675426 I can confirm that the expired cert is causing the problem because if I go to https://plugins.stage.mozilla.com/ and temporarily add a certificate exception, then the https: plugin check page works. If you can get it to work on one particular computer perhaps that is because it has the certificate exception permanently stored? Does it work with a clean profile? Anyway, it looks like Ashish has identified the main problem.

I filed bug 723941 for IT to fix this.

Should be fixed now.

(In reply to James Long (:jlongster) from comment #14) > Should be fixed now. Yes, it works now. Thanks.

Don't we maintain lists of certs we use for services? (I think we do) If we do, can we verify plugincheck is on that list? Thanks!

verified fixed https://www.mozilla.org/en-US/plugincheck/