Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
The operating system my web server runs on is (include version): Ubuntu
My hosting provider, if applicable, is: Amazonlightsail
I can login to a root shell on my machine (yes or no, or I don’t know): Yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): I am using amazon lightsail console to manage my site.
My Question is different. The SSL Certificate generated has www before the domain. While I want it to be without www. So my domain is www.example.com. Certificate is generated for www.example.com. But for some reasons I need it to be example.com.
Kindly let me know what is the issue.
Nice Site and support is ready to chat! Looks like a port redirect is in place. might want to remove it and make sure that your root host (without the “www”) has a vhost configured… lets start with that.
SEO is a totally different subject, but search engines give “weight” to sites using encryption.
LE will be issuing wildcard certificates for domains. I know there is someone that knows more on this subject… But take a look at [https://letsencrypt.org/2017/12/07/looking-forward-to-2018.html] in regard to that.
Apache has configuration guides to assist in setting up your virtual hosts dealing with your issue. (I had a similar problem) Look at https://httpd.apache.org/docs/2.4/vhosts/name-based.html … you should be able to browse to wordsuccor.com, or www.wordsuccor.com before you configure a cert.
Try running “certbot certificates” from the command line to determine what domain info certbot sees. (the output may help)
apachectl -S should show you the vhosts… if you don’t see wordsuccor.com in the output, there’s a need to reconfigure your subdomain. (off topic here I think)
The output from apachectl -S and certbot certificates should reveal the fundamental issue holding you up.
If you are already set up, try removing the port redirect in your vhost config or your httpd.conf