You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The exact command to do this depends on your OS, but common examples are sudo apt-get remove certbot, sudo dnf remove certbot, or sudo yum remove certbot.
Notice that none of those command use Snap ... but in the very next instruction, you're going to tell people to install with Snap:
sudo snap install --classic certbot
In summary, you tell people to install with Snap, and then when they come back months later to reinstall, you give them every removal command except the Snap one.
It would make much more sense for the Snap removal command to be the first recommended command, since anyone who has used Certbot before will have it installed that way.
The exact command to do this depends on your OS, but common examples are sudo snap remove certbot, sudo apt-get remove certbot, sudo dnf remove certbot, or sudo yum remove certbot.
The text was updated successfully, but these errors were encountered:
My operating system is (include version): Ubuntu 20
I installed Certbot with (snap, OS package manager, pip, certbot-auto, etc): snap
Let's stop right here, because the issue is with the documentation for this step of Certbot. If you go to https://certbot.eff.org/instructions?ws=nginx&os=ubuntufocal you'll see these instructions:
Notice that none of those command use Snap ... but in the very next instruction, you're going to tell people to install with Snap:
In summary, you tell people to install with Snap, and then when they come back months later to reinstall, you give them every removal command except the Snap one.
It would make much more sense for the Snap removal command to be the first recommended command, since anyone who has used Certbot before will have it installed that way.
Thus, I propose modifying that section of https://certbot.eff.org/instructions?ws=nginx&os=ubuntufocal to:
The text was updated successfully, but these errors were encountered: