This FAQ contains any workarounds, fixes and recommendations from the Heart Internet support team for customers experiencing problems with their Heart Internet services. The FAQ will be updated as new information becomes available.
For regular service updates please visit https://www.webhostingstatus.com/
What caused the current service outage?
For full details, please see this blog post.
Why did you originally report the outage as a DDOS?
We came under a DDOS attack shortly before the service outage, however it later became clear that it was not the cause of the outage and so we removed this message to prevent confusion. You can read the full details of the power outage which caused the disruption here.
My Linux VPS is unavailable. What can I do?
All kvmhosts (machines that host our Virtual Private Servers) are operational and so the most likely cause is corruption in your VPS’ database or file system. You should follow the steps below in the “How can I restore my VPS” section to restore your VPS. If the steps below do not work, you will need to restore your VPS from your backups.
If you do not have backups, support can attempt to restore your VPS. We cannot guarantee that we will be able to restore your VPS to its original state via this method, and we strongly advise that you restore from backups wherever possible. Please also note that if you are on an unmanaged package it will take support a significant amount of time to complete this work as we do not regularly monitor unmanaged servers.
How can I restore my VPS?
If your VPS is unable to boot or show sites, then this machine may have suffered corruption due to the unexpected power loss. The fastest way to get this server online is to re-provision it and restore from your backups. If you have no available backups, please follow these instructions:
If this machine is a Linux machine that fails to boot and shows filesystem errors
Please attempt to start the machine in recovery and run a filesystem check by running this command:
fsck –y /dev/sda3
If this machine is a Linux VPS with MySQL database corruption the fastest way to get this server online is to re-provision it and restore from your backups.
It is possible to recover from MySQL corruption using the following process. This is not a guaranteed fix but if the databases are recoverable this process will allow that.
- Open the /etc/my.cnf file (MySQL’s config file)
- It should look similar to this (however options may vary)
[mysqld] innodb_file_per_table=1 open_files_limit=2164 max_allowed_packet=268435456
- Add this line to the end:
innodb_force_recovery = 1
- Try starting MySQL again.
If it fails, change the line you added to my.cnf to:
innodb_force_recovery = 2
- Try restarting MySQL again.
- If it still fails, change the line you added to my.cnf to:
innodb_force_recovery = 3
- You can keep going up to 6 if needed however this should be a last resort as anything over 3 can cause data los
- As soon as you get MySQL started, take a full backup of your databases. MySQL is now is read only recovery mode so your sites may not be online but you should take a copy of your data as soon as possible
- To take full backups, run this command from the command line:
# mysqldump --all-databases --lock-tables --compress --routines --comments --extended-insert > new_all_databases.sql
- log in as the root MySQL user, check the DB, exit, stop MySQL and remove the “innodb_force_recovery = […]” line from my.cnf.
- Start MySQL one more time. It should now be running normally
- You may need to repair corrupted tables using the following method:-
mysql> USE databasename; mysql> REPAIR TABLE `table1` , `table2`;
- The above should work for you and will allow MySQL to start and run however once you do this get this started. There is more information regarding this here: https://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
If the above method is unsuccessful, the below method may prove successful:
- Add the following lines to /etc/my.cnf – this will prevent the need for a password and set the database into recovery mode:
innodb_force_recovery = 3
- Next, attempt to start MySQL in read only recovery mode using the following commands:
[root@vps ~]# mysql_upgrade --force
[root@vps ~]# service mysql restart
- Dump your existing databases using:
[root@vps ~]# mysqldump --all-databases --lock-tables --compress --routines --comments --extended-insert > /backups/new_all_databases.sql
- Stop MySQL and move the corrupt /var/lib/mysql folder:
[root@vps ~]# service mysql stop
[root@vps ~]# mv /var/lib/mysql /var/lib/mysql_bak
- Add this comment to /et/my.cnf:
- Restart MySQL:
[root@vps ~]# service mysqld restart
The above guide should correct any issues, however if the above fails to work or if you may need to restore from your backups.
If the recovery process fails, and you do not have backups please raise a support ticket and we will attempt to recover your data. Please understand however that we have an extremely large backlog of tickets and we are handling them in chronological order, it may be some time before we can arrive at and address your ticket.
I’m seeing MySQL Connection Errors on my Shared Hosting Database, what can I do?
This could have been caused by the unexpected power outage causing the last active table in your database to crash. To resolve this, log in to PHPMyAdmin and repair all database tables:
- Log in to PHPMyAdmin
- Select the affected database
- Select all database tables
- Click”Repair All”
This should allow the site to load.
How can I backup/restore my VPS from a Plesk Database Dump?
There’s an excellent guide here which may help you to restore your VPS from a Plesk Database dump.
If Nginx is non responsive on your plesk server, use the following commands to restart it:
[root@server ~]# /usr/local/psa/admin/bin/nginxmng -d
[root@server ~]# /usr/local/psa/admin/bin/nginxmng -e
[root@server ~]# service nginx restart
My Shared Hosting package is hosted on web75/web76/web77/web78 and is unavailable. What can I do?
These servers were taken offline as a result of the power outage. They are being rebuilt and we’re working to have them online as soon as possible. This is a lengthy process and support will not be able to hasten it for you. Once these servers are rebuilt and put back online, your services will be restored automatically with no need for support interaction. Updates will be posted as we receive them to https://www.webhostingstatus.com/. Thanks for your patience.
These shared hosting servers are now available and sites are displaying. If you are seeing additional errors, please contact support.
I’ve raised a support ticket about my VPS / Shared Hosting and have not received a response yet. When can I expect one?
Our support team are working as fast as they’re able to address these tickets and are prioritising tickets related to unavailable services. We understand that this is causing you frustration and we’re sorry for the delays. Our support team and SysAdmins are working 24 hours to get you back online. Please keep an eye on your email inbox for updates on your tickets. Please be aware that if you have a non-urgent issue we are unable to offer support at this time as our resource is focussed on restoring unavailable services.