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:
Displaying the details of your website's failed code to the world is a terrible security risk as it's impossible to predict what might get displayed.
For this reason Krystal's servers are set to NOT display your script errors to the public. This means if your website goes wrong, it won't normally display the reasons to the public. This is a common reason for a website showing a blank or partially blank page.
Errors generated by PHP are recorded, but instead of being shown to the world at large, they are recorded in files called error_log. These files get created in the directory containing the script that caused the error.
Erros can also be generated by the web server itself - these are more fundamental errors, and they are sometimes viewable using the cPanel Error Logs icon. These are separate from the PHP error described above.
How to check your web server Error Log files
In cPanel, you can click on the Error Logs icon (in the Logs section of cPanel) to see the most recent errors logged for your account. This is not an exhaiustive list of errors the webserver might have logged, so if you can't figure what's gone wrong from whatr you see, let us know and we can dig a little deeper for you.
PHP error_log files
If you want to look at all historic PHP errors then you will want to look through all the error_log files in your home directory. You can find them by opening FileManager from within cPanel.
Once FileManager is open, you can search for all files called error_log by entering error_log in the top right hand search box and clicking the GO button.
This will show you the location of all of your error_log files. You can then double click the entries to open FileManager in that directory so you can read the particular error_log file.