Closed Bug 1148927 Opened 7 years ago Closed 3 years ago

Sandbox uses self-signed certificate for HTTPS


(Websites ::, defect)

Not set


(Not tracked)



(Reporter: anaran, Unassigned)


See these links:

  referenced from


Etherpad users! We are developing an extension that will allow you to create pages from etherpads quickly and easily. Please visit our sandbox and help us test it.

When I click that link, I get:

This Connection is Untrusted

You have asked Nightly to connect securely to, 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.

I guess the site would get more testers with a proper certificate installed.
Summary: User:MyPage - MozillaWiki Please make a trusted site → Sandbox uses self-signed certificate for HTTPS
I guess this bug has ceased to be relevant after the integration of now?
Flags: needinfo?(ckoehler)
It's still relevant in that the sandbox continues to use a self-signed ssl cert. 

We should see if there is a wildcard cert for and if we could use it on the sandbox. Though, overall a self-signed cert doesn't bother me that much on what is generally just used for developer testing.
Flags: needinfo?(ckoehler) hasn't been around for a while as far as I know, so going to close this as invalid.

Closed: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.