Web Hosting

Please find below our list of Web Hosting guides to help with your hosting account.

How to force HTTPS (SSL) on your Onyx Site

This article was posted in: Web Hosting

Video Guide

Text Guide

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.

Configure HTTPS Redirection for Primary Domain

First lets force the use for SSL for all visitors to our primary domain name:

  1. Login to your Onyx Portal
  2. Select the site you wish to make this change to
  3. Select Settings -> Domains on the left hand menu
  4. Click on the domain name shown as Primary
  5. Set the "Require HTTPS (SSL/TLS)?" dropdown to "Yes - Redirect all visitors to a secure HTTPS connection"
  6. Click the "Update domain settings" button

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.

Fix Mixed Content / Non Secure Warnings

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.