The owner of www.beeminder.com has configured their website improperly. To protect your information from being stolen, Nightly has not connected to this website.
The certificate is not trusted because the issuer certificate is unknown.
The server might not be sending the appropriate intermediate certificates.
An additional root certificate may need to be imported.
Thanks for the (potential) bug report! So far we’re theorizing (hoping) you’re the only one seeing that. (If anyone else is please chime in or click the heart on @ghf’s post.) Could you tell us what browser and OS you’re using? Does “Nightly” refer to the bleeding edge version of Firefox? Do you see the same problem with the most recent stable version?
Not Beeminder staff here, just someone trying to be helpful:
Not only am I not seeing it, I went to the SSLLabs SSL/TLS checker and they
say Beeminder is mostly good, certainly not drastically misconfigured. (B+,
I think).
Unknown Issuer is an interesting one too–which implies that GlobalSign
isn’t trusted by ghf’s system.
Normally, for weird SSL issues like this, I’d suggest ghf check to make
sure their time isn’t drastically off, but I’m doubtful that would cause
Unknown Issuer.
I suspect that whatever Nightly is, it doesn’t have Globalsign as a trusted
CA–which seems weird. I wonder if it works in other browsers on the same
system?