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.
Instantly talk to one of our support team, we're here to help.
For our clients only. Open a ticket you can track and reply to.
Monday–Friday 9am – 8pm we're ready to assist you.
We pride ourselves on offering a hosting support service like no other; polite, knowledgeable & fast.
Your typical .htaccess SSL redirections will NOT work on Onyx when our caching is enabled. However, the steps below will ensure https redirection works as intended.
So, you've signed up for Onyx, you've configured your domain names and are using your free LetsEncrypt SSL certificates but you're still not seeing the green padlock or secure notice in your web browser. The steps in this guide will walk you through forcing all website traffic to use the https:// protocol.
First lets force the use for SSL for all visitors to our primary domain name:
That's it. Your domain will now forward all requests to the secure copy of your site. Note, some WordPress sites may still display not-secure errors, or mixed content warnings. If you receive these notices it is highly likely that your website theme and/or plugins are calling content in a non-secure manner. See step two for ways to fix this.
The changes made in Step One should handle SSL forcing for you in the vast majority of cases. However, where certain plugins are installed or modifications to themes have been made you may experience mixed content / non-secure warnings in your web browser. To fix these we would recommend installing the "Really Simply SSL" plugin which makes changes to WordPress's output at runtime and aims to replace all http:// with https:// for dynamically generated content.
If you still get these notices after installing the above plugin we would then suggest looking at your theme files to replace references to http:// with the https:// variant.