Accidentally installed certbot-auto over existing install, uninstall instructions?

My domain is: dorifuto.moe

I ran this command:
sudo /opt/certbot-auto

It produced this output:
The usual output. The installation was successful, and this is dpkg.log after installing:

2017-10-07 09:50:46 status installed install-info:armhf 6.3.0.dfsg.1-1+b1
2017-10-07 09:50:46 status installed libssl-dev:armhf 1.1.0f-3
2017-10-07 09:50:47 status installed libffi-dev:armhf 3.2.1-6
2017-10-07 09:50:49 status installed python3-pkg-resources:all 33.1.1-1
2017-10-07 09:50:49 status installed libc-bin:armhf 2.24-11+deb9u1
2017-10-07 09:50:51 status installed python3-virtualenv:all 15.1.0+ds-1
2017-10-07 09:50:51 status installed libpython2.7:armhf 2.7.13-2
2017-10-07 09:50:51 status installed augeas-lenses:all 1.8.0-1+deb9u1
2017-10-07 09:50:51 status installed python-virtualenv:all 15.1.0+ds-1
2017-10-07 09:50:51 status installed libexpat1-dev:armhf 2.2.0-2+deb9u1
2017-10-07 09:50:54 status installed man-db:armhf 2.7.6.1-2
2017-10-07 09:50:54 status installed libpython2.7-dev:armhf 2.7.13-2
2017-10-07 09:50:54 status installed virtualenv:all 15.1.0+ds-1
2017-10-07 09:50:54 status installed python2.7-dev:armhf 2.7.13-2
2017-10-07 09:50:54 status installed libpython-dev:armhf 2.7.13-2
2017-10-07 09:50:54 status installed python-dev:armhf 2.7.13-2
2017-10-07 09:50:54 status installed libaugeas0:armhf 1.8.0-1+deb9u1
2017-10-07 09:50:55 status installed libc-bin:armhf 2.24-11+deb9u1

My web server is (include version):
nginx/1.10.3

The operating system my web server runs on is (include version):
Raspbian 9.1 stretch

My hosting provider, if applicable, is:
Not applicable.

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

So I had some trouble getting certbot to automatically renew certificates with cron jobs and started following some instructions, which used certbot-auto. Dumb be then proceeded to just follow the instructions installing that without realizing it’s intended for distributions without certbot.

Well, everything still works, but how do I undo the installation of certbot-auto and get my machine back to pre-installation? Or is it fine like it is now? Or should I remove the apt-installed certbot?

Installing certbot-auto is actually a good thing (normally).
What problem(s) have you encountered since the install (if any)?
What problem(s) did you have before the install (if any)?

No problems since the install. Before the install I had trouble getting automatic renewal working. I’m wondering if I’m better off removing the certbot-auto package and its dependencies and keep using the certbot that’s from the stretch packages, or go the certbot-auto-only route. Right now I don’t know if certbot is doing the renewal or certbot-auto, so I’d just like to get back to only 1 certbot install, and not have both 0.19.0 and 0.10.2 at once.

To remove the Debian certbot package:

sudo apt-get remove certbot

Note that certbot-auto does not set up a cronjob for you like the Debian package does, so if automatic renewal is taking place without any attention from you, and you didn’t set up a cronjob yourself, the Debian certbot package is probably the one being executed for autorenewal.

To autorenew with certbot-auto you must set up a cronjob that executes /path/to/certbot-auto -q renew yourself. We recommend you run it twice daily, as it checks for renewal and only renews 30 days before expiry. (By running it twice daily, you have 60 chances to get a certificate before it expires in case there’s any trouble.)

To remove certbot-auto, just delete it and the files it places in /opt, along with any cronjob you may have created.

1 Like

Ah, thanks, so just removing the certbot-auto file and /opt/eff.org/ (and the dependencies it installed while running it for the first time) should be enough then? Just did that and nothing broke, so I guess it’s fine.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.