Unable to use custom certbot plugin

[ElDani82]

I'm trying to switch from one of the DNS services built into the swag container to another that isn't natively supported, but for which a certbot plugin exists.

I've set up a fresh swag container with a basic docker-compose.yml file that works fine when I choose a built-in DNS validation plugin (tested with desec), but it fails with the following changes to the configuration:

services:
  swag:
    image: lscr.io/linuxserver/swag:latest
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1001
      - PGID=1001
      - TZ=Europe/London
      - URL=subdomain.home64.de
      - VALIDATION=dns
      - SUBDOMAINS=wildcard
      - DOCKER_MODS=linuxserver/mods:universal-package-install
      - INSTALL_PACKAGES=go
      - INSTALL_PIP_PACKAGES=certbot-dns-multi
      - DNSPLUGIN=multi
      - PROPAGATION=90
      - ONLY_SUBDOMAINS=false
      - STAGING=true
      - DISABLE_F2B=true
    volumes:
      - ./config:/config
    ports:
      - 11443:443
      - 11180:80
      - 11443:443/udp
    restart: unless-stopped

The above configuration installs the certbot-dns-multi package with all its dependencies and produces no error messages. Unfortunately swag doesn't seem to accept it, as I get stuck at the following output:

...
swag  | Successfully installed certbot-dns-multi-4.25.1
swag  | Please set the DNSPLUGIN variable to one of the following:
swag  |

Instead of the expected list of the allowed (default) plugins, the output simply stops here.

I've tried looking at previous issues in the linuxserver/swag-docker repo and found similar or identical issues here, here and here.

In reply to what I've read there:

• The CPU may not support SSE 4.2 - It does, I've checked the output of /proc/cpuinfo and SSE4_2 is definitely present.
• The configuration may have been broken due to the change of the DNS plugin - The issue persists even after deleting the config folder and starting the stack again.

At this point I'm wondering if I'm doing anything wrong or if this is a problem in the container that's been around for over a year without getting any developer attention. The issues I linked to have all been closed but not fixed.

[aptalca]

over a year without getting any developer attention

?!?

What kind of attention do you expect it to get? It's been getting weekly package updates as well as near instant certbot and dns plugin updates. I'd argue that it's so stable it doesn't need anything else other than regular updates.

[ElDani82]

I apologize if that came out wrong, but what I intended to say is this: I've searched and found multiple other users who reported the same problem, but aside from two potential reasons (neither applied to me) I haven't found anything. That's why I created this topic here in the support discussions.

And yes, swag has been running great for me for a long time now. Didn't have any problems until I changed things up.

[aptalca]

The linked issues aren't all the same. One of them has the dns plugins listed, but the selected plugin is not installed prior to that so it's not on the list, hence the failure.
Another one involved using a cpu from before 2011, not something we can reproduce.

In your case, you can exec into the container and run certbot plugins --authenticators and see why it's not listing the available plugins.

Also you didn't post a full log so I can't confirm that the multi plugin was indeed installed prior to that step.