In order to meet the latest PCI Data Security Standards (PCI DSS) we will be dropping support for
TLS 1.0 and the TLS_RSA_WITH_3DES_EDE_CBC_SHA ciphers on all servers in our infrastructure.
The deadline set from the PCI Security Standards Council is the
30th of June, 2018. You can read more about it here.
After this update, customers using legacy browsers and user agents will be unable to access any SSL secured website hosted in our platform.
These user agents include but not limited to:
any browser running on Windows XP
any browser running on Android 4.4 or earlier
Internet Explorer 10 and below
Firefox 23 and below
Chrome 21 and below
any clients using Java 1.7 or earlier
curl and wget command line clients using OpenSSL versions priors to v1.0.1
If your browser and operating system is up to date, then you should probably be OK.
If you are unsure whether this change will affect you or not you can visit this
If you have any questions regarding this security change, please
raise a ticket and our support team will gladly answer your questions.
2018-06-01 14:35 UTC: The shared MySQL database service on Web536 is currently down. We’re working to restore service at this time. We’ll update this post when more information is available.
2018-06-01 17:59 UTC: All databases have been restored.
Web560 is currently inaccessible. This appears to be due to routing problems and we are looking into it.
Wed May 30 04:23:50 UTC 2018: The server is back online.
The frontend web server (nginx) on Web505, Web517 and Web630 is currently down. Our system administrators are working to resolve this issue as soon as possible.
2018-05-28 8:22 UTC: The issue has been resolved and nginx on all 3 servers is now back online.
Mailbox26 is currently not accessible. We are looking into the issue and will resolve as quickly as possible.
2018-05-28 03:20 UTC: Mailbox26 is back online and all services are operational.
Web559 is currently not accessible. We are looking into the issue and will resolve as quickly as possible.
2018-05-26 10:00 UTC: Web559 is back online and all services are operational.
is taking effect soon, and we’ll be deploying related updates to various pieces of our infrastructure, including the Control Panel and Community sites, over the next 24 hours. We expect downtime of affected services to last less than an hour, and we’ll mark this post complete as soon as all changes have been fully deployed. General Data Protection Regulation
The server is currently not accessible. We are looking into the issue and will resolve as quickly as possible.
2018-05-22 17:08 UTC: We have identified the problem and are working as fast as possible to bring the machine back online.
2018-05-22 18:36 UTC: We have done a chassis swap and importing the data.
2018-05-22 19:56 UTC: The server is back online.
A recent system update to the core glibc package seems to have caused a small number of python apps hosted on our servers to stop working, showing the following in their error logs:
ImportError: /lib64/libresolv.so.2: symbol __h_errno, version
GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
The Apache stack needs to fully stop for this to be fixed. You can do that by
starting an ssh session, traversing to the directory hosting your app, and using the `stop` and `start` scripts:
If you are having any trouble or need further assistance with this, please
raise aticket and our support team will gladly help you with.
On Sunday, 22nd of April, between 11:00 and 12:00 UTC, we will be migrating our ticketing system to new hardware.
During this time our ticketing system will be unavailable. You will not be able to raise new tickets, nor reply or review old ones.
We expect total downtime to be less than 30 minutes.
2018-04-22 12:10 UTC: We are starting the maintenance.
2018-04-22 12:42 UTC: The maintenance has been successfully completed.