The issue with the Google Chromium web browser reporting valid certificates as “unsafe” has been resolved today with an update to Chromium.
Update, 2016-11-20: We’ve posted a commentary about this on our blog.
The issue with the Google Chromium web browser reporting valid certificates as “unsafe” has been resolved today with an update to Chromium.
Update, 2016-11-20: We’ve posted a commentary about this on our blog.
We are aware that s small subset of users of the Chromium web browser may receive the following error when trying to access websites and control panels via HTTPS that use the *.niner.net certificate:
Your connection is not private
Attackers might be trying to steal your information from cp31.niner.net (for example, passwords, messages or credit cards). NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
(cp31.niner.net will be replaced by whatever domain you are trying to access.)
If you click the “ADVANCED” link you will see the following additional information:
The server presented a certificate that was not publicly disclosed using the Certificate Transparency policy. This is a requirement for some certificates, to ensure that they are trustworthy and protect against attackers.
This is a bug in Google Chromium, not a problem with our certificate.
Until Google fixes this bug we recommend using a better web browser (e.g., Firefox), or clicking the “Proceed to cp31.niner.net (unsafe)” link that is revealed when you click “ADVANCED” as described above. Clicking the “unsafe” link is indeed safe in this case. Even very big and very busy websites — such as Yahoo and Flickr for example — are currently affected by this bug.
The SSL certificate was upgraded on server NC027 at 10:09 UTC. This covers email services. We’ll be replacing the expired certificates on other server and control panels shortly too.
You may need to restart email programs and web browsers for the new certificate to be recognised. Again, we apologise for the inconvenience.
The upgrade of server NC027 was completed at 02:22 UTC, and the server is up and running. Thanks for your patience.
The upgrade of NC027 started at 01:47 UTC and is currently in progress.
We’re going to continue holding back the upgrade of NC027 for another two hours and re-evaluate at that time. Our apologies for the delays.
Due to the possibility of significant delays, we are postponing the upgrade of NC027 scheduled for this time for another hour. We’ll reassess the situation at that time and re-evaluate. Updates will be posted here.
Thanks for your patience.
The upgrade of server NC031 was completed at 23:16 UTC, and the server is up and running. Thanks for your patience.
In light of this much faster upgrade we’re going to suggest that the bigger upgrade of server NC027 next weekend shouldn’t take nearly as long as is currently scheduled.
The above two servers — the primary mail (NC027) and web (NC031) servers — will undergo hardware upgrades during our regular weekend maintenance windows this weekend and next:
* 16 July, 23:00 UTC: NC031, duration approximately 2 hours
* 23 July, 23:00 UTC: NC027, duration approximately 7 hours
Please click on the above dates and times to use the World Time Server website to convert to your local time zone. The above durations are only estimates. Down time will be slightly less, as some of the work can be done while the servers are still up, and there’s always the possibility that the work will finish more quickly. However, please plan for the servers to be down for the entire durations stated above.
Incoming email during the maintenance of server NC027 on the weekend of 23 July will be held on the sending servers and delivered once the server is back online. No email will be lost.
During the maintenance this status website will be available, and we will post updates when the maintenance starts and ends, as well as during if necessary.
If you have any questions or concerns, please contact us to let us know. Thanks for your patience and understanding as we work to improve our service to you.
As of this moment, the NC027 IP address is no longer blocked by Microsoft on their Hotmail / Outlook.com / Windows Live service. Additionally, test messages we’ve sent have been delivered to the in box of the test account. We have removed the workaround.
Systems at a Glance:
Loc. | System | Status | Ping |
---|---|---|---|
NC023 | Internal | Up? | |
NC028 | Internal | Up? | |
NC031 | Internal | Up? | |
NC033 | Operational | Up? | |
NC034 | Internal | Up? | |
NC035 | Operational | Up? | |
NC036 | Operational | Up? | |
NC040 | Internal | Up? | |
NC041 | Operational | Up? | |
NC042 | Operational | Up? |
Subscriptions:
Search:
Recent Posts:
Archives:
Categories:
Links
Tags:
Resources:
On NinerNet: