Firefox Nightly: Loading failed for the <script> with source...

[rwaldron]

Console shows these errors:

Loading failed for the <script> with source “https://static.jsbin.com/js/vendor/jquery-1.11.0.min.js”.
Loading failed for the <script> with source “https://static.jsbin.com/js/prod/jsbin-4.1.2.min.js”.

I can't figure out why they aren't loading, but I'll keep looking.

[scheinercc]

It is due to a cert error for the subdomain https://static.jsbin.com due failing as SEC_ERROR_UNKNOWN_ISSUER
Just filed a bug in bugzilla against it: https://bugzilla.mozilla.org/show_bug.cgi?id=1444687. Will link to this page from there as well.

[scheinercc]

Apparently a Symantec cert is in use here and the distrust (Firefox/Chrome) of these certs has started: see reference bug https://bugzilla.mozilla.org/show_bug.cgi?id=1434300

[remy]

Except i updated the certs…

…

On Mon, 12 Mar 2018, 09:54 Albert Scheiner, ***@***.***> wrote: Apparently a Symantec cert is in use here and the distrust (Firefox/Chrome) of these certs has started: see reference bug https://bugzilla.mozilla.org/show_bug.cgi?id=1434300 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3219 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAA1hBZF0j3ni-AqRKLTNxaQEFYKhHxcks5tdkXggaJpZM4SfiJd> .

[scheinercc]

@remy quick turn around! then I'd suggest you reopen and comment on bug 1444687 maybe there is something else going on or buggy in bug 1434300

[remy]

No, I update the cert 3 weeks ago. *that's* the problem. You (and many others) are somehow seeing a cached cert.

…

On Mon, 12 Mar 2018, 11:28 Albert Scheiner, ***@***.***> wrote: @remy <https://github.com/remy> quick turn around! then I'd suggest you reopen and comment on https://bugzilla.mozilla.org/show_bug.cgi?id=1444687 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3219 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAA1hMbE5zzeFT2LaWFOF6PabPAQW_Y5ks5tdlvmgaJpZM4SfiJd> .

[scheinercc]

Sorry, I am not really into the whole cert thing. Just follow along the news.
Wouldn't the caching be something with the browser? And therefore part of the bug I linked?

[remy]

This is actually a dupe of #3214 - so I'm going to close and track on #3214.

I just pushed a code change to the static server, which…I'm hoping causes CloudFront to flush it's cached SSL certificate. If anyone can give it a retest I'd appreciate it (I'm not able to replicate as, for some reason, I'm routing through a different path to the cert).

[scheinercc]

remy, it's still blocked for me. Checked in Nightly and DevEdition with VPN set to Europe and US. Will try again later.

[rwaldron]

Still having the issue here.

[scheinercc]

It's back :) Thank you!

[remy]

Finally solved it last night. Turned out i had a damn etc/hosts entry that was confusing me!