My certificate cannot secure the WWW only non-WWW. After a lot of research I have accepted I am not able to fix this myself and need help.
My domain is: aajs.com, and I normally keep the .htaccess with
RewriteCond %{HTTP_HOST} ^aajs.com [NC]
RewriteRule ^(.*)$ "https://www.aajs.com/$1 [L,R=301]"
For now I have excluded it to show the web page with the working SSL.
I ran this command: '.acme.sh/acme.sh --issue -d aajs.com -w /home/xensicom/aajs.'
The operating system my web server runs on is some Linux with kernel vesion 4.18.0-553.lve.el8.x86_64
My hosting provider is:Namecheap
I can't login to a root shell on my machine.
I'm using cPanel with terminal
Not possible to use Certbot with Namecheap. What about using CertSage and will it be creating www and non-www? I cannot test this as I am over the rate-limits until tomorrow.
A certificate only covers the names included on that certificate, unless it's a wildcard (e.g. *.aajs.com) in which case it can cover the first level of subdomains under that name.
Based on crt.sh | aajs.com you seem to managing this ok for your other subdomains.
What I have done gives me 2 separate certificates with no help for me except for in ZeroSSL.
Earlier I had no problems until I got it in to Namecheap and my free period with their certificate expired. I like Let's Encrypt since I can have more sub domains.
Yes, my other domains works because I have only renewed them and that works for me.
Will your acme.sh --issue -d aajs.com -d www.aajs.com -w /home/xensicom/aajs make one certificate or two separate?
