# Help with Certbot and ACME v2 **URL:** \ **Category:** Help\ **Created:** [February 19, 2020, 9:17pm UTC](https://community.letsencrypt.org/t/help-with-certbot-and-acme-v2/113655 "2020-02-19T21:17:51Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![rempfer](https://avatars.discourse-cdn.com/v4/letter/r/22d042/32.png) [@rempfer](https://community.letsencrypt.org/u/rempfer)\ **Post date:** [February 19, 2020, 9:17pm UTC](https://community.letsencrypt.org/t/help-with-certbot-and-acme-v2/113655/1 "2020-02-19T21:17:51Z")
Is there a step-by-step of what one should do to change from a working ACMEv1 to ACMEv2? I am very much a novice and am kinda scared I’ll mess something up and not know how to recover. ``` dick@debian9mail:~$ certbot --version certbot 0.10.2 dick@debian9mail:~$ certbot-auto --version bash: certbot-auto: command not found dick@debian9mail:~$ ``` Some of my questions are: Do I need to apt-get install ACMEv2? What command line would I run after that? I’d be glad to provide any other info. It’s been long enough since I did the first Let’s Encrypt set-up (and especially since it’s worked so flawlessly) that I don’t recall what all was involved in getting it going the first time. I apologize for my ignorance, Dick Rempfer ---
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [February 19, 2020, 9:20pm UTC](https://community.letsencrypt.org/t/help-with-certbot-and-acme-v2/113655/2 "2020-02-19T21:20:39Z")
Hi @rempfer, welcome to the community forum 👋 I moved your post to its own topic because I think that will make it easier for you to find help. > [@rempfer](#): > > I’d be glad to provide any other info. It’s been long enough since I did the first Let’s Encrypt set-up (and especially since it’s worked so flawlessly) that I don’t recall what all was involved in getting it going the first time. Not a problem 🙂 Could you try to answer as many of the following questions as possible? 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. [crt.sh | example.com](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: I ran this command: It produced this output: My web server is (include version): The operating system my web server runs on is (include version): My hosting provider, if applicable, is: I can login to a root shell on my machine (yes or no, or I don't know): I'm using a control panel to manage my site (no, or provide the name and version of the control panel): The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): ---
**Author:** ![rempfer](https://avatars.discourse-cdn.com/v4/letter/r/22d042/32.png) [@rempfer](https://community.letsencrypt.org/u/rempfer)\ **Post date:** [February 20, 2020, 1:35am UTC](https://community.letsencrypt.org/t/help-with-certbot-and-acme-v2/113655/3 "2020-02-20T01:35:51Z")
> [@cpu](#): > > Not a problem 🙂 Could you try to answer as many of the following questions as possible? > > 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](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 domains are: > [rempfer.net](http://rempfer.net), [r2bbs.com](http://r2bbs.com) > > I ran this command: > certbot renew --dry-run -v > > It produced this output: > Congratulations, all renewals succeeded. The following certs have been renewed: > /etc/letsencrypt/live/rempfer.net/fullchain.pem (success) > \*\* DRY RUN: simulating 'certbot renew' close to cert expiry > \*\* (The test certificates above have not been saved.) > > My web server is (include version): > root@debian9mail:~# apache2 --v > [Wed Feb 19 17:25:04.207256 2020] [core:warn] [pid 14088] AH00111: Config variable ${APACHE\_RUN\_DIR} is not defined > apache2: Syntax error on line 80 of /etc/apache2/apache2.conf: DefaultRuntimeDir must be a valid directory, absolute or relative to ServerRoot > > The operating system my web server runs on is (include version): > root@debian9mail:~# uname -a > Linux [debian9mail.rempfer.net](http://debian9mail.rempfer.net) 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86\_64 GNU/Linux > > My hosting provider, if applicable, is: > N/A > > 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): > > The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you’re using Certbot): > root@debian9mail:~# certbot --version > certbot 0.28.0 Thanks for moving this thread to an appropriate location. I had a dickens of a time getting certbot to upgrade from version 0.10.x, but it seems I've got it now. May I ask you though, will the default entry certbot's install routine made in /etc/cron.d/certbot be satisfactory for updating my certificates in a timely manner? ``` root@debian9mail:/etc/cron.d# cat certbot # /etc/cron.d/certbot: crontab entries for the certbot package # # Upstream recommends attempting renewal twice a day # # Eventually, this will be an opportunity to validate certificates # haven't been revoked, etc. Renewal will only occur if expiration # is within 30 days. # # Important Note! This cronjob will NOT be executed if you are # running systemd as your init system. If you are running systemd, # the cronjob.timer function takes precedence over this cronjob. For # more details, see the systemd.timer manpage, or use systemctl show # certbot.timer. SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin 0 */12 * * * root test -x /usr/bin/certbot -a \! -d /run/systemd/system && perl -e 'sleep int(rand(43200))' && certbot -q renew ``` Many thanks for the Let's Encrypt service and your help here! ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [March 21, 2020, 1:35am UTC](https://community.letsencrypt.org/t/help-with-certbot-and-acme-v2/113655/4 "2020-03-21T01:35:51Z")
Closed on March 21, 2020, 1:35am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.