NinerNet Communications™
System Status

Server and System Status

Chromium certificate issue resolved

17 November 2016 20:08:44 +0000

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.

Issues with *.niner.net certificate

16 November 2016 10:34:52 +0000

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.

SSL certificate update 2

20 September 2016 11:57:43 +0000

The SSL certificate has been replaced on all servers. If you still get errors, please restart the program in question or, if necessary, restart the machine or device.

If you need any assistance, please contact NinerNet support. Thank-you.

SSL certificate update 1

20 September 2016 10:19:12 +0000

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.

NinerNet SSL certificate

20 September 2016 09:05:00 +0000

Our wildcard SSL certificate for *.niner.net has expired in some time zones. It will be updated within the hour and an update posted here.

Our apologies for the delay.

POODLE maintenance: Complete

23 October 2014 22:54:04 +0000

We have completed the maintenance to mitigate against exploitation of the POODLE vulnerability.

Because the effects of this maintenance could potentially be wide-ranging, please contact support if you have any issues with connecting over a secure connection to any of our servers. We don’t believe there will be any issues with web (HTTPS) connections, but there may be with some email (SMTP, IMAP and POP) connections by older email programs. That said, an exploit against this vulnerability has only been demonstrated using JavaScript and a web browser, so email connections (even if using SSLv3) are not generally considered to be at risk.

Thanks for your patience during this maintenance.

UPDATE, 2014-10-24: Please read some details on this maintenance, and learn more about SSL and TLS and email security, on our corporate blog.

POODLE maintenance: Update 1

19 October 2014 00:33:28 +0000

The maintenance described in our last post is under way, but we are running into some issues that are delaying completion. While there may be sudden and unexpected interruptions in some services for some clients, we are aware of them and are working on them. If necessary, we will revert to old configurations while we re-evaluate the new configurations recommended to defend clients against the POODLE vulnerability.

Thank-you for your patience.

SSL version 3 “POODLE” vulnerability, system-wide maintenance

17 October 2014 05:25:59 +0000

We will be conducting maintenance this weekend to address the above noted vulnerability. Please read more details about this on our corporate blog.

NinerNet SSL certificate fully installed

21 July 2014 12:10:11 +0000

We have solved the issue with the new NinerNet SSL certificate not fully propagating to all servers. All SSL web and email connections should now be using the new SSL certificate, which expires in 2015.

If you are having any issues, please restart your computer to ensure that all software on the computer uses the new SSL certificate. If you still have problems, please contact NinerNet support with a full description of the error message you are seeing.

Thank-you for your patience.

NinerNet SSL certificate

21 July 2014 07:41:35 +0000

We are aware that the new NinerNet SSL certificate has not properly propagated to all servers. We are working to fix this and will post an update here as soon as we believe the issue has been resolved.

In the meantime it is usually possible to override any warnings and continue with whatever you are doing.

NinerNet home page

Systems at a Glance:


SystemStatusPing
NC020OperationalPing
NC023OperationalPing
NC024InternalPing
NC027OperationalPing
NC028InternalPing
NC031OperationalPing
NC033OperationalPing

Subscriptions:

RSS icon. RSS

Twitter icon. Twitter

General Information:

This blog provides information about the status of NinerNet Communications systems. Dates and times of posts to this blog are in the UTC time zone, and dates and times given for events are also in the UTC time zone, although conversions may be offered for some time zones common to our clients. Please use the World Time Server to ensure accurate conversion of dates and times to your own time zone.

Search:

 

Recent Posts:

Archives:

Categories:

Links

Tags:

.co.zm domains .com.zm domains .zam.co domains browser warnings connection issues database dns dos attack dot-zm domains down time email delivery ftp hardware mailing lists mail relay migration nameservers performance phplist reboot smtp spam spamassassin ssl ssl certificate tls tls certificate web server

Resources:

Unable to open ninernet_xsite: Access denied for user 'ninernet_x_site'@'173.45.228.52' to database 'ninernet_xsite'