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.
My domain is:mahabazaaronline.com
I ran this command:sudo certbot --apache -d mahabazaaronline.com
It produced this output:/etc/letsencrypt/options-ssl-apache.conf has been manually modified; updated file saved to /usr/lib/python3/dist-packages/certbot_apache/options-ssl-apache.conf. We recommend updating /etc/letsencrypt/options-ssl-apache.conf for security purposes.
Plugins selected: Authenticator apache, Installer apache
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
Attempting to parse the version 1.9.0 renewal configuration file found at /etc/letsencrypt/renewal/magento2.vismayaonline.com.conf with version 0.31.0 of Certbot. This might not work.
Attempting to parse the version 1.9.0 renewal configuration file found at /etc/letsencrypt/renewal/maha.vismayaonline.com.conf with version 0.31.0 of Certbot. This might not work.
Obtaining a new certificate
Created an SSL vhost at /etc/apache2/sites-available/mahabazaaronline.com-le-ssl.conf
Deploying Certificate to VirtualHost /etc/apache2/sites-available/mahabazaaronline.com-le-ssl.conf
Enabling available site: /etc/apache2/sites-available/mahabazaaronline.com-le-ssl.conf
Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.
1: No redirect - Make no further changes to the webserver configuration.
2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for
new sites, or if you're confident your site works on HTTPS. You can undo this
change by editing your web server's configuration.
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
Redirecting vhost in /etc/apache2/sites-enabled/mahabazaaronline.com.conf to ssl vhost in /etc/apache2/sites-available/mahabazaaronline.com-le-ssl.conf
Congratulations! You have successfully enabled https://mahabazaaronline.com
You should test your configuration at:
IMPORTANT NOTES:
-
Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/mahabazaaronline.com/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/mahabazaaronline.com/privkey.pem
Your cert will expire on 2021-02-09. To obtain a new or tweaked
version of this certificate in the future, simply run certbot again
with the "certonly" option. To non-interactively renew all of
your certificates, run "certbot renew" -
If you like Certbot, please consider supporting our work by:
Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate
Donating to EFF: https://eff.org/donate-le
My web server is (include version):2.4.18
The operating system my web server runs on is (include version): Ubuntu 16.04
My hosting provider, if applicable, is: DO
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): no
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you're using Certbot): 1.9.0
Everything went well. My e-commerce store's front end and admin end worked well with https://mahabazaaronline.com. I checked if the certificate works for www.mahabazaaronline.com, it gives me error NET::ERR_CERT_COMMON_NAME_INVALID
Strangely, from that point onward, home page gives me an error (Whoops our bad! Typical magento error message for a bad url) but all pages work properly. What could go wrong with perfectly working URL?
Can someone please help me, That would be very helpful