I then view the certsage.php in the cpanel and have to highlight and copy the content, then I paste this into the cpanel install an ssl website heading - then paste into the certificate section but a box comes up saying certificate is invalid ? not sure what I am doing wrong? thanks for your help with this
You need to "view" that file in your browser.
It's as @rg305 stated.
You can visit your CertSage page here:
You should now have a
CertSage directory located one level above where
certsage.php is located. You don't want that directory to be accessible from the internet. Once you acquire your certificate, you can find your certificate and its private key in the
CertSage directory. Be sure to carefully follow the instructions to install your certificate into cPanel.
For the domains box, you want to enter
regresyondmp.com on the first line and
www.regresyondmp.com on the second line so that your certificate covers both domain names.
From your certificate history, it looks like you successfully acquired a certificate yesterday covering only
So I managed to install the certif and key but I am having problems with the last instructions about forcing the HTTPS. on the cpanel I go to domains which has my list of domains but at the top is one listed as - main domain titled 'dummy' and has document listed as public_html then the other domains are listed underneath with /addtional-domains/regresyondmp.com etc . but under the heading 'forcing https' it has this info - addons and parked domains inherit their https redirect status from their associated subdomain.
I may be doing some thing wrong ? any ideas
In cPanel your primary/parent domain name has
public_html as its webroot directory while your secondary/child domain names have subdirectories inside the
public_html directory as their webroot directories.
Furthermore, in cPanel if you "add" a secondary/child domain name it is always accessible as a subdomain name of your primary/parent domain name in addition to through the actual secondary/child domain name itself.
For example, let's say you registered
example2.com. You make
example1.com your primary domain name and
example2.com a secondary domain name. You would assign a subdomain name of
example2.com. Now, the content of
example2.com is accessible via
http://sub.example1.com. In cPanel, you manage
example2.com through its subdomain name of
sub.example1.com. Weird, I know, but that's how it works.
You might want to also read through this excellent post:
thanks that is something I will do for security. I am stuck at the last instructions on your list to force https. I do not know what to do. below isthe cpanel screen shot (hopefully this will work)
I have just uploaded the certificate for reygressondmp.com to day 22 jan and it expires on 4/21/22
will I have to keep uploading these or can I automatically renew them ?
The renewal process is the same as the initial process. If you leave everything in place, it should only take a few minutes to renew.
This should be the answer you seek:
Thanks, in the end after trying to communicate with tsohost, as it is difficult as I do not understand the techy lang. In the end I could upload the certif but not redirect so they suggested to put the plugin really simple ssl and force the https from the websites. which I did.
the final thing you mentioned was to make sure the public could not reach inside website , Is there a way to see if it is ok or not ?
Why install a plugin rather than just follow the instructions in the link above?
With your having installed a plugin, I'm not exactly sure what your site is now doing in terms of SSL maintenance. The comment I made before was regarding the use of CertSage for embedded/addon domain names. This post clearly explains the issue there and how to deal with it.
Hi, I really do appreciate your help as I would not have got as far as I have. I did look several times at the link you sent about solved force https redirect... I went to the cpanel - and found all the domains/addons but i could not change anything (see screen shot) and I did not understand the box info at each site for on and off force https redirect eg.- you can not activate HTTPS redirect because autossl is not currently active for this domain or the ssl certificate is not valid. So I tried to find out what this meant and had to contact the help at tsohost and their advice was plugin. I do apologise for my lack of techy lang and understanding. I would rather follow your advice as then I would have the step by step process which I could repeat everytime. it was the panel that stopped me (see image), what could I do ?
While we wait for his reply...
At first glance, those names appear to be duplicated.
But that seems unlikely, so, I surmise they are the "www" of the names shown below them.
And the error message makes it clear that a valid cert is required before HTTPS redirection is allowed.
If that is the case, then those sites seem to be missing the "www" from their certs OR the panel isn't reading the certs correctly.
[just my observation]
No issued certificates:
Issued certificates expired:
Issued certificates valid and installed:
Before we go any further though, do you have AutoSSL in your cPanel?
I hit the same problem with TSOHOST, in the short-term I fixed it with CertSage but the need to renew quarterly, although easy is an extra task. I felt badly let down by tso not just for withdrawing LetsEncrypt but also for doing so with no warning - so suddenly my site was displaying an "insecure" alert. I took this as the final push I needed to move sites to better hosting (not part of the GoDaddy empire).
#MeToo! I look after my brass band's website, which I kept on TsoHost after they took over 5quidhost because they're local and offered free charity hosting. I only discovered they'd been taken over by GoDaddy when I got the warning message about the certificate expiring soon. I'm now mid-way through transferring the site to Krystal.uk, to carry on using Let's Encrypt, hence was looking for info on transferring from cPanel to cPanel.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.