... And why it is necessary to open a ticket to help us to process your request.
This December, we will be making a change to make Simple Hosting easier to use, as well as more manageable.
Currently, there are three separate signatures, one for each datacenter, for the SFTP protocol you use to transfer files to Gandi Simple Hosting instances.
In a few days, we will replace We have replaced these keys so that they are all the same (and thus easier to manage). The new key will have the following signature, whether your instance is hosted in our Paris, Baltimore, or Luxembourg datacenter:
2048 35:e0:5a:a9:54:12:55:6b:ce:41:8c:c1:9e:35:1d:f6 (RSA)
1024 80:c7:a8:05:dc:79:92:f1:9c:b7:61:46:a7:ad:2d:f7 (DSA)
For reference, the outdated key signatures were as follows:
2048 02:15:f6:35:d7:01:3c:58:74:8c:e4:0e:96:61:35:6f (RSA)
1024 36:c2:9c:5c:5b:d0:7e:5b:78:e4:ee:47:ad:aa:1c:8e (DSA)
2048 f8:ed:00:17:1a:88:9f:4d:15:fb:84:46:1e:19:4f:c5 (RSA)
1024 69:84:9b:dd:3b:cd:9a:20:df:60:60:e0:6d:cd:5e:e7 (DSA)
2048 c1:0b:b5:1d:57:cb:00:75:22:a5:6b:d3:bc:73:64:5a (RSA)
1024 7c:ac:f0:23:6b:d6:e8:78:67:4c:72:95:9b:14:61:eb (DSA)
How does this affect me?
In most cases, all you need to do is accept the new key when you log into your instance via SFTP. The client will prompt you the first time you use it to connect after we make the change.
If your client doesn't handle the changed signatures gracefully, you can manually flush the key on the command line (replace dc0 in the command below, if necessary: dc0 = Paris datacenter, dc1 = Baltimore, dc2 = Luxembourg):
$ ssh-keygen -R sftp.dc0.gpaas.net
and then use your sFTP tool and reconnect again and accept the new foreign key.
If you have any questions or concerns about this, let our support team know. We are here to help!
We've developed a new tool to give you better visibility into incidents and the scheduled and unscheduled maintenance that may impact our services.
This tool, which you can access by clicking on the "Service Status" link at the top of each page of our site, is live at https://status.gandi.net, where any unexpected incidents or scheduled maintenance will be reported.
The coders among you can also use the API to query the status of our services from your scripts and monitoring applications. For example, to get the service status in real time, use https://status.gandi.net/api/services. The service catalog is available at https://status.gandi.net/api.
We are available to help you get around any issues you are having using our services. Here's a little primer on how to get our assistance, if you need it:
- First, be sure to check that there are no incidents or ongoing maintenance on the service status page. Maybe your service is affected by an outage, or in maintenance.
- If the status page says everything in fine, your issue may be a problem you can fix by using the administration pages of our site. For instance, your domain may have expired, or a recent change in your DNS zone may be causing a problem. Your hosting might be paused, your credit balance empty, or maybe your email quota was exceeded? All these common issues can be fixed by logging in to your account and taking care of the problem.
If you are unable to identify what is wrong, or to solve it yourself, we are here to help. Contact us using the following methods:
- Chat with us in real time by clicking on the '?' icon on the right-hand side of your account. We are available almost all the time, but if we're busy or unavailable, you can leave a message and we'll respond as soon as we can.
- Open a ticket on our support contact page.
Please be sure to give us the details of your problem so we can help you quickly. We like to get you the right answer as fast as we can.
You will receive an automatic confirmation of your ticket in an email, including a ticket number. A member of the support team will then respond via email. We use the email address listed in your account, by default, so be sure to keep this contact information up to date. Also, sometimes the automated email or even the replies of our agents get filtered as spam. Remember to check your spam folder if you do not receive the automatic confirmation with your ticket number.
We hope you like this new feature. We try our best to be transparent about any problems we encounter, and this is just one of the ways we are trying to prove that to you, our customers.
An emergency maintenance will be carried out Thursday, October 16th 2014 at 4:30PM CEST on the Gandimail platform.
This maintenance will likely cause some email mailboxes to be unavailable during this time.
Please accept our apologies for any inconvenience this emergency maintenance may cause.
5:55 CEST : End of the gandimail emergency maintenance
There is currently a problem with BaseKit, which GandiSite is based on.
Consequently, websites using GandiSite are offline. (SiteMaker sites are not affected.)
Our teams are in the process of investigating the problem. Updates will be provided here.
Update Wed 15 Oct 20:00 UTC (1pm PDT): Everything should be back to normal. Please let us know if you encounter any further issues.
We just suffered a major incident at one of our facilities. A faulty processor caused the shutdown of a storage unit.
As communications to the disk were interrupted, all operations (reboots, changes, etc) were suspended.
We restarted the unit, and all the services have begun recovering. Operations were queed and are being executed once again. No data was lost. Everything should be returning to normal.
This incident started at 16:19 CEST (07:19 Pacific time). The system was recovered at 16:57, and all queed operations were fully resolved at 17:25 CEST (08:25 Pacific time).
We do apologise for this interruption in service.
As a reminder, you can see the status of our services here:
You can also follow our twiiter feed from the Gandi Noc at @gandinoc.
This news feed is available at: https://www.gandi.net/news
In the meantime, please do NOT launch any operation on your server(s). The situation will return to normal shortly.
An incident has occurred on one of our storage units in the Parisian datacenter. Our technical team is working to resolve the issue as quickly as possible.
Please do not perform any operations on your virtual machines in the meantime. Services should be restored automatically once the issue has been corrected.
We will update this post as new information arises.
Update Tue Oct 7 19:28:19 UTC: Some faulty hardware has been identified; we're in the process of swapping it out.
Update Tue Oct 7 22:33:14 UTC: Our technical team is still trying to fix the issue.
Update Tue Oct 7 23:35:44 UTC: A ZIL disk has failed, and its failover also failed. We're currently performing a manual switchover, and are proceeding very carefully to minimize the risk of data loss.
Most importantly: we understand how disruptive this is for you and we're working as hard as we can to fix it. We will do our best to make it right.
Update Wed Oct 8 00:39:21 UTC: Our technical team is bringing the storage unit back up. The incident is nearly resolved and services are already beginning to come back online.
Update 02:31:10 UTC: We're now seeing high loads on the problematic filer. The investigation continues!
Update 04:05:54 UTC: After working all night, our technical team in Paris has resolved the problem. Services should now be back to normal.
A postmortem and compensation details, as described in our IaaS Hosting Contract (section 2.2) will be provided in the days to come.
Update Thu Oct 9 17:31:34 UTC: A postmortem about this incident is available here.
We will be proceeding with some maintenance on a Gandi Mail storage unit.
The window for this maintenance will be from Tuesday October 7th 2014 from 11:30 PM to midnight CET (Paris time).
There will be several thousand Gandimail mailboxes that will be inaccessible for several minutes during that time.
No mails will be lost during this time, they will be held awaiting delivery.
[EDIT] The maintenance is postponed to the 8th of October 2014 from 11:30 PM to midnight CET (Paris time).
We will reboot a storage unit on the Paris/FR datacenter tonight.
The maintenance window will start 3 October at midnight and end at 1am CEST (3-4pm PDT, 22:00-23:00 UTC) Update: the maintenance window has been extended by 30 minutes and is expected to end at 1:30am CEST (4:30pm PDT, 23:30 UTC).
You will not need to reboot your server (IaaS) or instance (PaaS) during this maintenance.
Sorry for the inconvenience.
Update : end of the maintenance at 2AM CEST, sorry for the delay.