I run command: sudo certbot --apache -d xxx sitename
And result:
This log line repeated 12 times all my https pages:
Attempting to parse the version 0.24.0 renewal configuration file found at /etc/letsencrypt/renewal/xxxx.conf with version 0.14.2 of Certbot. This might not work.
And final log lines are:
Obtaining a new certificate
Performing the following challenges:
Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA.
Do I get new certificate correctly when current certificates end?
What should I do to get new certificate to my current http page?
I have site http conf file /etc/apache2/sites-available/xxx.conf
and symbol link /etc/apache2/sites-enabled/xxx.conf -> …/sites-available/xxx.conf
Once you do that, running your command should just work. Using --apache should automatically install the certificate to your Apache virtual hosts, and it should also automatically renew.
“Or maybe you used certbot-auto previously?”
Yes I use certbot-auto. My certbot version has years be 0.14.
So I wonder if there something went wrong with current working certificates
if I run:
sudo add-apt-repository ppa:certbot/certbot
sudo apt-get update
Just one question is my mind. https certificate is
new even certbot version has been old long time.
So old version certbot-auto works right. I just can get
totally new certificate for new site with this old version.
So I just run
sudo apt-get install --only-upgrade certbot
and I can get new certificate for new site?
/root/certbot-auto, which is a portable version of Certbot that is based on a shell script and upgrades itself automatically.
certbot, which is installed from package repositories and upgrades are managed by the package manager.
Both installations will use the same certificate and renewal settings from /etc/letsencrypt, so you don’t need to worry about that.
In the past, you’ve obviously been using certbot-auto. I would suggest that you continue to use it for your new certificates, by running /root/certbot-auto instead of certbot.
If you wish, you can switch to certbot from package repositories instead, but you need to ensure that you install it from the PPA, as documented, or you will have an old version that might not work so well.
One question is:
Ubuntu 14.04 LTS which i use End of Life date April 2019
So after that I need to update it example
Ubuntu 18.04 LTS. To get new certificates.
Is that right? Or do certbot-auto get new
certificates after that?
I just had about one year time to prepare that changes.
Or do certbot-auto works correclty after April 2019.
This https certificate refreshing is only outside thing in my
websites.
In particular, since certbot-auto probably won’t be in your PATH, you’ll need to specify a directory in the shell, which could be done with something like sudo /root/certbot-auto or cd /root; sudo ./certbot-auto.