Includes free SSL certificate, unlimited bandwidth & fully optimised for WordPress.
Fully PCI-DSS compliant hosting, backups every 6 hours & free DDoS protection.
Unlimited bandwidth, WHM & cPanel control panel & fully white label.
Great value domain names available.
Create a professional looking website in minutes. Over 190 templates.
Speed up the delivery of your site.
Beautifully Simple. Massively Configurable. Scales from 1 VPS cloud, all the way up to a load balanced cluster.
Fully managed, high-spec dedicated servers deployed on our gigabit network, backed by our superior 24/7 UK support.
For our clients only. Open a ticket you can track and reply to.
Instantly talk to one of our support team, we're here to help.
Talk to us: 020 8050 1337 (Monday–Friday 9am – 8pm)
Business plans have access to 24/7 emergency phone support.
Search our extensive archive of guides to help you with your hosting account.
or go directly to our support site:
If you see an Internal Server Error (http status code 500) then something has gone seriously wrong. It might be our fault, but more often it's due something that's been misconfigured in your home directory. Common reason are:
Oops, you have a bug in your code
If PHP comes across a FATAL error that cannot be handled, then you will get a 500 error. If you are developing a website then this is probably your first stop on the bug-fix highway. Check your error_log files for clues.
Syntax error or disallowed directive in .htaccess files
.htaccess files are very sensitive things. You have to treat them with great care or they will bite! The quick and dirty (tried and true) way to work out where your error is, is to simply backup the file and then start hacking chunks of it out until the error goes away.
Common directives that Krystal do not allow in .htaccess files are
Wrong permissions have been set on a PHP script
If the Write bit is set for Other on a PHP file, then a 500 error will result. So, if the last digit of the file's three digit chmod is 7, 6, 3 or 2 then it's going to fail. This is a security feature of the suPHP environment we run. You don't want your PHP scripts to be writeable by just anyone!
PHP files should always be chmod 600, 640 or 644 (although 644 should not be used for scripts containing usernames or passwords.)
Wrong permissions have been set on public_html
It can be easy to accidentally alter permissions on files and directories. If the Write bit is set for Group or Other on this directory then a 500 error will result. The public_html directory should always be chmod 750.
Your account has exceeded it's allowed share of server resources
It is possible that because your account is exceeding it's allowed shared of the server's resources that your processes are either being delayed, or refused access to further memory. In some cases this can cause your website to produce errors. Please read the article - How to check your account's resource usage - for further information.