Link is not loading over HTTPS
If you are trying to view an SSL secure page on a web host that does not yet have an SSL certificate for your account, you will see a blank page.
Installing any SSL certificate (regardless of whether it was issued for a different domain name, is expired or self-signed) should work.
Alternatively, you can create a temporary link by setting the HTTPS port to the same port used by HTTP (usually 80). It triggers "Flexible SSL" mode, causing SkipDNS to forward HTTPS requests using HTTP.
We've added several checks to ensure internal links maintain the HTTPS protocol; however, depending on how your site is encoded, the links may be broken, point to HTTP or you may experience redirect loops.
In these cases, you will need to "teach" your application that a protocol change is taking place during the forward step.
If your host is using Apache, you can do this by adding the following lines to the public_html/.htaccess file (add them to the beginning of the file if you're not sure).
These lines are telling Apache "if you get an X-SkipDNS-Proto header stating that the original request was received over HTTPS, always treat it as coming over HTTPS over port 443".
If that doesn't work, or if you're not using Apache, you can add the following lines to your site's startup script (for a WordPress site, add them to the wp-config.php file, anywhere after the PHP opening tag, which is located on the first line of the file, and before the line that says "Stop editing").
The second line is not always needed. WordPress, for example, does not rely on this information to build internal links and completely ignores the port in the environment variables, relying exclusively on the port defined in the 'siteurl' database entry in the wp_options table, when present, therefore, the first line should be enough. For some other CMS, however, the communication port is relevant. Adding the two lines does no harm, it just forces your scripts to treat all requests as coming from port 443, which is the standard for HTTPS.
I am a hosting provider. How can I prevent my customers from having to do this themselves?