NinerNet Communications™
System Status

Server and System Status

NC020: Web server problem

4 June 2016 06:49:09 +0000

The web server on server NC020 experienced a problem at 04:45 UTC on 4 June 2016, and shut itself down. The problem was rectified at 06:00.

We apologise for the problem, and will resume migration of the websites on NC020 to NC031 this coming week. If you have asked us to delay the migration of your website, please contact us if you still need a further delay.

NC020: Data centre maintenance complete

28 April 2016 22:20:58 +0000

We’ve been informed that the network maintenance within the NC020 data centre was completed successfully this morning. All services are running normally.

NC020: Data centre network maintenance

16 April 2016 10:52:19 +0000

The data centre where server NC020 is located plans to do some possibly disruptive network maintenance. They write, “We have taken precautions in preparation for this maintenance and do not anticipate a disruption lasting longer than one hour during the scheduled maintenance window.”

The maintenance window will be on Thursday, 28 April, between 05:00 and 10:00 UTC.

Please use the WorldTimeServer.com website to convert this time into your time zone.

Server NC020 still hosts a few websites that have not yet been migrated to server NC031. It also hosts some custom mailing lists and some secondary email domains. And it hosts this status blog, actually.

If you have any questions or concerns or want to find out if any of your services are hosted on this server, please let us know. Thank-you.

Web server upgrade

12 March 2016 12:33:12 +0000

We’ll be sending out an email shortly to informĀ NinerNet clients that over the next few weeks we will be moving all of the shared hosting websites hosted on servers NC018, NC020 and NC026 to a new server, NC031. While this might look like one server is taking on the workload of three, that’s not quite the case; servers NC020 and NC026 are currently hosting only a relatively few websites that had outgrown the limitations of NC018. On top of that, server NC031 is a shiny new server, running the latest commercially available versions of all software, with far more resources than the servers it is replacing, and an increasing emphasis on secure connections.

The new server is also running a new control panel. The one on server NC018 (Plesk) has served us well. In fact, server NC026 was running the latest version of Plesk when it was set up a couple of years ago, but our experience with the new version has — to put it simply — been disastrous. In fact, we’ve gone out of our way to avoid clients actually using it. We evaluated another popular control panel — cPanel — but we came away with much the same opinion as we’ve developed of Plesk, but for different reasons.

The new control panel we’re using is called Virtualmin, and is based on a control panel (Webmin) that we first used privately in 2006 but which has been around since 1997 … almost as long as NinerNet! There will no doubt be a period of adjustment as we switch — for you and for us, especially as we develop support documentation — but we’re confident that Virtualmin is far better than other control panels that we have evaluated, and we’ve been impressed by their responsive support so far.

With that background information out of the way, here are a few points you need to know:

  • As we set up your domain(s) in the new control panel you will receive an automated email with the log-in information you will need for the control panel and for FTPS (FTP Secure) for uploading files to your server. Please keep this information in a safe and secure place, for future reference. Your website will be moved shortly after that, but not necessarily immediately.
  • Where possible we will move your website without any coordination with you. Where coordination is necessary or desirable, we will contact you at least 24 hours in advance.
  • If you or your web manager, designer or developer would like to contact us in advance of moving your website to discuss any particular needs or requirements, please feel free to do so as soon as possible.
  • We will be starting with websites on server NC026, then server NC018, and lastly server NC020.
  • All files in the “web root” on the old server will be moved. Where necessary (rarely) we’ll rename existing directories if their names clash with directories set up by default on the new server — unless this will cause a problem with your website, in which case we’ll rename the directories on the new server. If you have any files stored outside of the “web root” — the “httpdocs” directory on NC018 and NC026, or the “htdocs” directory on server NC020 — please either download them to your local computer, or contact us so that we’re aware that they need to be moved too.
  • Speaking of the web root, the file path on the server to your website will change. The new path will be /home/USERNAME/public_html , where you will replace “USERNAME” with your actual user name, of course. Most of the time this is irrelevant, but for some web applications it might be important to know this.
  • If the nameservers for your domain are hosted elsewhere — i.e., we cannot access them to update the information for your domain to point it to the new web server — you will need to do this yourself. The IP address of the new server is 173.255.231.250; you will need to know this to point your domain to it after we transfer the files.
  • We will manually check to ensure that your site is online after the move and check a few additional pages, but please check yourself to make sure everything is good. Once a day we’ll email the owners of the websites that were moved that day.
  • Your website will not be down during the transfer. Where there is the possibility of complications, we will leave your domain pointing to the old website until any complications have been resolved.
  • This migration has nothing to do with email in any way. The email server is not involved, and your email will continue to flow uninterrupted while we migrate websites.

One other item to note is that we’re really emphasising the importance of complex passwords. These have always been important to us, but our older systems haven’t always enforced complex passwords. Complex passwords are vital to the security of everything you do online that requires you to log in to view private data (such as your email or bank account) or manage services that unauthorised users should not access (such as the back-end of your website). This is why we set longer (a minimum of 12 characters) and more complex passwords by default. To manage long and complex passwords we use and recommend a program called KeePass, which has versions and clones made for all major systems — e.g., Windows, Linux, Mac, Android and iOS (iPhone/iPad). We strongly recommend this program or one like it. It will make your life so much easier, and more secure too.

As always, we strive to ensure that your hosting (and the move to the new server) are without any headaches, and that attitude will apply to this move as well. Please feel free to contact us if you have any questions or concerns. Thank-you.

NC020: Earlier server reboot

21 November 2015 02:16:43 +0000

We have determined from monitoring logs that server NC020 was only offline for a few minutes, and was rebooted at 09:46 UTC on 20 November within a few minutes of the problem being discovered.

We apologise to those few clients still using server NC020 who may have been inconvenienced at that time.

If you have any questions about this, please let us know. Thanks.

NC020: Server rebooted

20 November 2015 10:07:39 +0000

We have rebooted server NC020 after it was overwhelmed. We’re looking into it right now and will post details here as soon as we have them.

NC020: Credits for outage

11 September 2015 19:16:40 +0000

Further to our previous posts, we will be processing credits to the accounts of all affected clients for the outage on NC020.

NC020: Web server stoppage update

11 September 2015 18:59:36 +0000

After some research, combing of the logs on the server, and reading of documentation, we believe we found a reason that the web server stopped working, but we believe the cause evaporated when, in our desire to get everything working again as quickly as possible, we just rebooted the machine after other options to restart the web server failed. However, even the suspected cause does not fully jibe with the observed symptoms.

The good news is that we have recently commissioned a new server (NC030) to take on the websites hosted on NC020. We are still working on setting up the control panel on that, but we hope to have it in production as soon as possible.

We apologise for this incident, and thank you for your patience and understanding.

NC020: Server rebooted

11 September 2015 14:20:56 +0000

The web server on NC020 was found to be unresponsive today, but would also not respond to commands to restart. As a result we rebooted the machine and this seems to have fixed the problem.

We’re busy analysing the logs to determine the cause, and will post an update here if we find anything.

SSL/TLS certificate renewed

21 August 2015 12:05:08 +0000

The *.niner.net wildcard SSL/TLS certificate has been renewed and has been installed for all services on all servers, except NC026 as it will be shut down any day now.

If you receive any SSL/TLS warnings, please try restarting the application (program) in question — e.g., web browser or email client. If that doesn’t work, try rebooting. If you’re still running into issues, please contact NinerNet support with the exact text of any error messages.

Thank-you.

NinerNet home page

Systems at a Glance:


Loc.SystemStatusPing
Server NC020, Chicago, United States of America, OPERATIONAL.NC020OperationalPing
Server NC023, London, United Kingdom, OPERATIONAL.NC023OperationalPing
Server NC027, London, United Kingdom, INTERNAL.NC027InternalPing
Server NC028, Vancouver, Canada, INTERNAL.NC028InternalPing
Server NC031, New York, United States of America, OPERATIONAL.NC031OperationalPing
Server NC033, Toronto, Canada., OPERATIONAL.NC033OperationalPing
Server NC034, Lusaka, Zambia, INTERNAL.NC034InternalPing
Server NC035, Sydney, Australia, PROVISIONING.NC035ProvisioningPing
Server NC036, Amsterdam, Netherlands, OPERATIONAL.NC036OperationalPing

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 back-up bounce messages browser warnings configuration connection issues control panel database dns dos attack dot-zm domains down time email delivery error messages ftp hardware imap mailing lists mail relay mail server microsoft migration nameservers outlook performance phplist pop power failure reboot smtp spam spamassassin ssl ssl certificate tls tls certificate viruses webmail web server

Resources:

On NinerNet: