Maybe try activating Development Mode in Edge Caching settings then try CertSage for Staging?
https://www.stackcp.com/services/b6a281ca222e41a2/cdn/caching
2 Likes
Still trying. I have generated account.key, certificate.crt and certificate.key.
I am pasting them into Certificate, Key and CA Bundle / Intermediate Certificate. So a bit confused which bit of code goes into which box!
All the variations I have tried so far have come out as invalid.
ADDING: Global Edge Caching is currently not activated. As I recall, it doesn't play nice with Wordpress/Divi. The only way to turn on Development Mode is to turn on Edge, but the all the option seems to do is disable Edge Caching, so I don't think that will make any difference.
1 Like
- Certificate: first certificate inside certificate.crt
- CA Bundle: second certificate inside certificate.crt
- Key: only key in certificate.key
You can identity individual certs by their begin and end lines in certificate.crt. You need to include the begin and end lines with each cert!
2 Likes
If you have certificate.key and certificate.crt, clearly production acquisition worked! 
2 Likes
It's quite possible you could be a genius!
The certificate has been accepted. Just have to wait for it to populate.
It was completely unclear which bit of code went into which box until you told me.
2 Likes
The confusion is fully understandable, my friend. The older versions of CertSage all used manual cPanel certificate installation, so I used to include instructions for that, which works the same way as StackCP.
2 Likes
You can check your cert install through this:
Port 443 is default HTTPS
2 Likes
Thanks! My other website uses a certificate generated by stackcp and I literally have had to do nothing since I clicked that option right at the beginning. It's so much easier.
2 Likes
You could also try the button (for cPanel) in CertSage to install your cert rather than copypasta. If StackCP has uapi under the hood, that button should work. The button in CertSage simply installs whatever certificate.crt and certificate.key are in the CertSage directory.
I generate and install my own certs for griffin.software using CertSage in under 30 seconds every two months just using the interface. Make sure to change the contents of password.txt to whatever is convenient (but still secure) for you.
3 Likes
I will have to try that when I have de-mushed my brain.
1 Like
That has been me today: 
Let us know how it goes, please. 
3 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.