[BUG] Please set DNSPLUGIN variable to one of the following:

[ewenlau]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When attempting to switch from HTTP to DNS validation, I get this error when setting DNSPLUGIN to cloudflare: Please set DNSPLUGIN variable to one of the following:
The container then hangs forever.

Expected Behavior

It should not be stuck and not ask for DNSPLUGIN as DNSPLUGIN is set and my CPU supports SSE4.2.

Steps To Reproduce

1. Have a E5-2680 (which supports SSE4.2)
2. Set DNSPLUGIN to cloudflare
3. docker compose up -d

Environment

- Host OS: Proxmox VE 8.2.2
- Guest OS: Debian 12.5
- CPU mode: Host
- CPU: Intel Xeon E5-2680 v1
- Docker: installed via instructions from docs.docker.com, aka custom APT repository.

CPU architecture

x86-64

Docker creation

services:
  swag:
    image: lscr.io/linuxserver/swag:latest
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/paris
      - URL=mydomain.com
      - VALIDATION=dns
      - SUBDOMAINS=wildcard
      - EMAIL=myemail
      - ONLY_SUBDOMAINS=false
      - STAGING=false
      - DOCKER_MODS=linuxserver/mods:swag-dashboard|linuxserver/mods:swag-dbip
      - CERTPROVIDER=zerossl
      - DNSPLUGIN=cloudflare
    volumes:
      - /opt/docker-files/swag/config:/config
    ports:
      - 443:443
      - 80:80
      - 81:81
    restart: unless-stopped
    network_mode: bridge

Container logs

[mod-init] Running Docker Modification Logic
[mod-init] Adding linuxserver/mods:swag-dashboard to container
[mod-init] Downloading linuxserver/mods:swag-dashboard from lscr.io
[mod-init] Installing linuxserver/mods:swag-dashboard
[mod-init] linuxserver/mods:swag-dashboard applied to container
[mod-init] Adding linuxserver/mods:swag-dbip to container
[mod-init] Downloading linuxserver/mods:swag-dbip from lscr.io
[mod-init] Installing linuxserver/mods:swag-dbip
[mod-init] linuxserver/mods:swag-dbip applied to container
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] done
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support the app dev(s) visit:
Certbot: https://supporters.eff.org/donate/support-work-on-certbot

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────

using keys found in /config/keys
Variables set:
PUID=1000
PGID=1000
TZ=Europe/paris
URL=mydomain.com
SUBDOMAINS=wildcard
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=false
VALIDATION=dns
CERTPROVIDER=zerossl
DNSPLUGIN=cloudflare
EMAIL=myemail
STAGING=false

Please set the DNSPLUGIN variable to one of the following:

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[mjessa12]

is there any update to this?

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[ewenlau]

is there any update to this?

I ended up moving away from SWAG because of this very issue. I can't afford to change hardware at the moment.

[FrozenDragoon]

I'm encountering the same issue, but with an E5-2640. What's odd is that I just encountered it with v2.11.0-ls312 but the issue does not occur with v2.11.0-ls310.

The container came right backup when I rolled back.

I'm using the digitalocean DNS plugin.

[FrozenDragoon]

So, after reading this comment in #469 (comment) I took a look at my config/etc/letsencrypt/cli.ini

The file had references to both the dns-googledns-credentials AND the dns-digitialocean-credentials. It seems that my issue (perhaps different than OPs) was due to removal of the GoogleDNS plugin in the most recent update for SWAG.

Removing the line referencing GoogleDNS allows the container to fully start up again without issue.

TLDR: you may have borked your DNS configuration and need to adjust it in config/etc/letsencrypt/cli.ini.

[zc1342303]

If you have changed the DNSPLUGIN environment variable after running docker-compose up, you might need to remove the config directory and restart the Docker container for the changes to take effect. Here's a step-by-step guide:

Stop the Docker container:

docker-compose down

Remove the config directory:

rm -rf /path/to/config

Restart the Docker container:

docker-compose up -d

By following these steps, you ensure that the changes to the DNSPLUGIN environment variable are correctly applied and the container starts with the new configuration.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[FrozenDragoon]

If you have changed the DNSPLUGIN environment variable after running docker-compose up, you might need to remove the config directory and restart the Docker container for the changes to take effect. Here's a step-by-step guide:

Stop the Docker container:

docker-compose down

Remove the config directory:

rm -rf /path/to/config

Restart the Docker container:

docker-compose up -d

By following these steps, you ensure that the changes to the DNSPLUGIN environment variable are correctly applied and the container starts with the new configuration.

I'd agree with this completely, with the caveat of BE CAREFUL WHEN DELETING YOUR WHOLE CONFIG DIRECTORY. This action will delete ALL your settings, not just those settings related to the DNSPLUGIN environment vars.

I'd recommend removing just the file config/etc/letsencrypt/cli.ini rather than the whole /config directory. But, if there is something truly weird, a whole pave and reload may be required. Just be cautious.