Problem with snap cerbot

I recently wanted to renew a certificate and it gave an error that no longer worked in a traditional way but had to be installed again with snap, following the tutorial on the page I find that it gives me the following message:

snap install --classic certbot

error: snap "certbot" is not available on stable but is available to install on the following
channels:

   edge       snap install --edge certbot

   Please be mindful pre-release channels may include features not completely tested or
   implemented. Get more information with 'snap info certbot'.

my system is Debian 9 i686

if I want to execute the command that tells me the classic gives the following error:

snap install --edge certbot

error: This revision of snap "certbot" was published using classic confinement and thus may perform
arbitrary system changes outside of the security sandbox that snaps are usually confined to,
which may put your system at risk.

   If you understand and want to proceed repeat the command including --classic.
1 Like

AFAIK certbot isn't actively packaged for x86 any longer (latest release on 14 June 2020), but @certbot-devs may correct me on that.

If I understand the warning message from snap correctly, you should be able to install certbot by combining the --edge and --classic options to the install command.

That said, you might be better off using the pip method of installing certbot, although I'm not sure if the certbot devs agree with me on this one. For that see Certbot - Pip Apache or Certbot - Pip Nginx or Certbot - Pip Other (depending on your webserver and if you want to use a webserver certbot plugin or not..)

1 Like

I believe the OP just wants to say "Yes" and continue.

The certbot snap modifies files outside of the typical snap sandbox (see Snap confinement | Snapcraft documentation) - it's working on /etc/letsencrypt.

1 Like

I believe the --classic command line option is always necessary to install the certbot snap for exactly the reason you've given, but the information in the first error (when trying to install from "stable") lacks the --classic part when it suggests you should need to use --edge. I believe there is no option given by snap to say "Yes" to. Therefore my suggestion to add both options on the command line.

2 Likes

It does not give me the option to continue, it simply does not install, I follow the installation steps as the web says, it installs the snap correctly but it does not install the cerbot and previously uninstall as the page says. I don't understand why it won't let me

1 Like

Please read my post(s). It should explain everything. I've even given a (possible) solution to install certbot through snap anyway. If you don't understand my post, I'd like to see what's unclear about it (sentence by sentence if you would be so kind), so I can improve my communication :slight_smile:

2 Likes

You are absolutely correct! I misread your post. Apologies to all!

1 Like

Certbot itself is written entirely in Python and therefore should work on (essentially) all architectures, however, we don't support i686 through snaps (because newer versions of Ubuntu have also dropped support for the architecture which makes it more difficult for us to support it). Ideally, snap install --classic certbot would error out with a message about this when it is run on an i686 system, however, an i686 Certbot snap was uploaded when we first started experimenting with snaps a long time ago and there's a bug in the snap store that makes it impossible for us to delete it. I hope we can get this fixed soon to improve the experience here.

In the meantime, the package python3-certbot provided by your OS should work, however, it's missing many of the improvements we've made to the project over the last few years. If you want to install an up-to-date version of Certbot on an i686 system, your best option is to use pip as suggested by Osiris by following the instructions linked in their post.

2 Likes

Of course I should have specified "packaged for x86 on snap" :wink:

2 Likes

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