Setting up SSL gives me a headache. After wasting countless hours, especially tonight where I kept messing up and regenerating the CSR code, canceling out my SSL cert, and kept getting an error that my private key doesn’t match the SSL. This caused some of my hair to go gray. When I get beyond frustrated, I then investigate a completely different approach, so here are my findings.
I wanted to share the simplest solution in the shortest amount of steps so you too can get SSL done within 2 minutes of time!
Step 1 — Sign in & Enable Namecheap SSL plugin
Click on Namecheap SSL
This entire time I have been doing it MANUALLY by requesting a certificate, having it signed via the browser and it’s code, going under SSL in cPanel, creating a CSR, adding it into the namecheap domain SSL certificate, then going back to cPanel, creating private key, generating a CRT, and then installing the SSL. BLAH! My brain turned into mush as I only do this maybe once a year, so trying to remember the exact steps in exact order is like relearning this from scratch every time.
Well, no more of that, you old school website makers that don’t do this for a living anymore! You can simply install the Namecheap SSL Plugin in cPanel as your first step. How long has this plugin been around? I’m afraid to ask…
Step 2 — Click on “Installed via plugin”
Simply click on the second tab over. Why? Because that’s what Namecheap documentation told me to do. The plugin is pulling the data from your Namecheap account, I’m assuming.
Step 3-Reissue your SSL and Enable it!
Under “Status” click on “Reissue and install” and then enable “HTTPS Redirect”. Be patient though! Oh, not patient? Okay, there’s a trick for that.
What about subdomains?
You can install an SSL on each subdomain at no cost by going back to Step 2 and clicking on the “My Namecheap SSL” and clicking on “install” for each of them.
You can test your URL to see if your SSL is enabled in an SSL Checker tool. All green check marks? Great, you are good to go!
Oh no, but your website stopped working? Well it’s probably some kind of server configuration issue. Maybe check your .htaccess / web.config file and see if you have any redirects or misconfiguration? Check the config file of your CMS and see if you have SSL disabled on your site? That’s a whole other level of debugging. My popcorn is currently popping, I umm…have to go!
Now that I realized I wasted dozens of hours of time not knowing this, it’s time for me to eat a large bowl of popcorn and shed tears for the rest of the night knowing I’ll never get those hours back in my life. I’m also specifically writing this, so I can go back to my own tutorial because the next time I’ll need to do this is probably in a year, in which I’ll completely forget how to do this again. Oh please, don’t tell me you haven’t went back to read your own tutorials written years ago! *smirks*
I hope I saved you some time! Cheers!