It found out that I have a website on unfalsecoding.net and gave me a choice to make a redirect or not (1 or 2). I chose 1.
After that it worked for a while and then wrote
- Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/unfalsecoding.net/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/unfalsecoding.net/privkey.pem
Your cert will expire on 2019-04-24. 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"
Everything seems installed properly and port 443 is opened but I cannot open my website anymore as chrome shows an error
This site can’t be reached
**unfalsecoding.net** refused to connect.
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. Authentication failed because the remote party has closed the transport stream.
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. Authentication failed because the remote party has closed the transport stream.
blocks everything.
Active blocking or closing the transport stream. Is there a firewall or something else? Are you able to connect the website from the server (using curl with 127.0.0.1 and port 80)?
sudo service apache2 restart
* Restarting web server apache2
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:443
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
AH00015: Unable to open logs
Action 'start' failed.
The Apache error log may have more information.
...fail!
* The apache2 instance did not start within 20 seconds. Please read the log files to discover problems
I am trying now to solve it by myself but I highly appreciate any help.
Thanks a lot!
I have just found a docker-proxy on :443
So I launched sudo docker stop and sudo service apache2 restart and my website is running now on http now but still not on https. Maybe I need to comment out the config for http and port 80.
Now everything is working!
I forgot that I have a couple of other virtual hosts and it seems that the automated cert-bot found the first virtual host and installed the certificates on it. So I removed them and only one has left. Ran sudo certbot --apache and restarted the Apache.
It has now a gray lock icon in Chrome but I think it’s another issue that I will solve later.
Thanks for help!
First, you have the www version defined in your dns settings. But the certificate has only the non-www domain name. So perhaps create a new certificate with both domain names.