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.
It probably wouldn’t do you any good. Most of the time, the configuration files are kept in place when a package is uninstalled. And if a configuration issue is the problem, well, those configuration files which were kept in place would still give you a problem when you install the webserver again.
You should try to debug your problem. Reinstalling a package is almost never the answer.
I have run this below command
sudo service apache2 start
Got Result
Job for apache2.service failed because the control process exited with error code. See “systemctl status apache2.service” and “journalctl -xe” for details.
I have again run another command and get below out
And Then get output result
/usr/lib/python3/dist-packages/ndg/httpsclient/subj_alt_name.py:22: UserWarning: Error importing pyasn1, subjectAltName check for SSL peer verification will be disabled. Import error is: No module named 'pyasn1'
warnings.warn(import_error_msg)
/usr/lib/python3/dist-packages/ndg/httpsclient/ssl_peer_verification.py:25: UserWarning: SubjectAltName support is disabled - check pyasn1 package installation to enable
warnings.warn(SUBJ_ALT_NAME_SUPPORT_MSG)
/usr/lib/python3/dist-packages/ndg/httpsclient/subj_alt_name.py:22: UserWarning: Error importing pyasn1, subjectAltName check for SSL peer verification will be disabled. Import error is: No module named 'pyasn1'
warnings.warn(import_error_msg)
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for www.qa.kerloresearch.com
Enabled Apache rewrite module
Waiting for verification...
Cleaning up challenges
Created an SSL vhost at /etc/apache2/sites-available/000-default-le-ssl.conf
Enabled Apache socache_shmcb module
Enabled Apache ssl module
Deploying Certificate to VirtualHost /etc/apache2/sites-available/000-default-le-ssl.conf
Enabling available site: /etc/apache2/sites-available/000-default-le-ssl.conf
We were unable to find a vhost with a ServerName or Address of www.qa.kerloresearch.com.
Which virtual host would you like to choose?
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
Deploying Certificate to VirtualHost /etc/apache2/sites-available/000-default-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
Enabled Apache rewrite module
Redirecting vhost in /etc/apache2/sites-enabled/000-default.conf to ssl vhost in /etc/apache2/sites-available/000-default-le-ssl.conf
Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/qa.kerloresearch.com/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/qa.kerloresearch.com/privkey.pem
Your cert will expire on 2020-07-12. 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:
Doesn’t really look anything wrong with that output to me. So the certificate was installed to 000-default-le-ssl.conf, but /etc/apache2/sites-enabled/default-ssl.conf is having difficulty loading the fake snakeoil certificate.
I’m no Ubunty expert, but can’t you just comment out the virtualhost block where that error about the snakeoil certificate is being made, around line 32?
Did you start your Apache server this time? Did you check for any new error messages preventing it from starting? Because as far as I (and SSLLabs) can tell, it's still down.
You probably shouldn't have mysqld available over the internet. Install a firewall to block port 3306 or even better if you're only using MySQL locally: disable access to it through TCP altogether.
You can. But like I said before, it probably won't fix your problem. Debugging your Apache issue is key here.
What command did you run to get your certificate in the first place?