Certbot "Illegal instruction"

I’m getting the following error running the command:

$ certbot
Illegal instruction

I also cannot successfully receive a certificate when starting the swag docker container.

Output of uname -mr && docker version and share your compose

> uname -mr && docker version 
6.1.79-Unraid x86_64
Client:
 Version:           24.0.9
 API version:       1.43
 Go version:        go1.20.13
 Git commit:        2936816
 Built:             Thu Feb  1 00:47:46 2024
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          24.0.9
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.13
  Git commit:       fca702d
  Built:            Thu Feb  1 00:49:16 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.7.13
  GitCommit:        7c3aca7a610df76212171d200ca3811ff6096eb8
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Docker:

docker run
  -d
  --name='swag'
  --net='proxynet'
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="swag"
  -e 'URL'=<redacted>
  -e 'VALIDATION'='http'
  -e 'SUBDOMAINS'=<redacted>
  -e 'CERTPROVIDER'=''
  -e 'DNSPLUGIN'=<redacted>
  -e 'PROPAGATION'=''
  -e 'EMAIL'='email@email.com'
  -e 'ONLY_SUBDOMAINS'='false'
  -e 'EXTRA_DOMAINS'=''
  -e 'STAGING'='false'
  -e 'DOCKER_MODS'='linuxserver/mods:swag-dashboard'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='022'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:81]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/linuxserver-ls-logo.png'
  -p '1443:443/tcp'
  -p '180:80/tcp'
  -p '81:81/tcp'
  -v '/mnt/user/appdata/swag':'/config':'rw'
  --cap-add=NET_ADMIN 'lscr.io/linuxserver/swag'

can you share the full container logs, beginning with our ascii logo too please. as a side note, you may be better served coming on discord for help

find: ‘/var/lib/letsencrypt’: No such file or directory
find: ‘/var/log/letsencrypt’: No such file or directory
/etc/s6-overlay/s6-rc.d/init-certbot-config/run: line 372:   699 Illegal instruction     certbot certonly --non-interactive --renew-by-default
User GID:    100
───────────────────────────────────────

using keys found in /config/keys
Variables set:
PUID=99
PGID=100
TZ=America/Los_Angeles
URL=<redacted>
SUBDOMAINS=<redacted>
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=false
VALIDATION=http
CERTPROVIDER=
DNSPLUGIN=<redacted>
EMAIL=email@email.com
STAGING=false

**** Permissions could not be set. This is probably because your volume mounts are remote or read-only. ****
**** The app may not work properly and we will not provide support for it. ****
Using Let's Encrypt as the cert provider
SUBDOMAINS entered, processing
Sub-domains processed are: <redacted>
E-mail address entered: email@email.com
http validation is selected
Generating new certificate
ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container
[mod-init] Running Docker Modification Logic
[mod-init] Adding linuxserver/mods:swag-dashboard to container
[mod-init] linuxserver/mods:swag-dashboard at sha256:71c6dd5d43e9202721c5d880ad7ffde14c610f45266ca74044464c2b6e4cc07d has been previously applied skipping
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
find: ‘/var/lib/letsencrypt’: No such file or directory
[migrations] done
find: ‘/var/log/letsencrypt’: No such file or directory
usermod: no changes
/etc/s6-overlay/s6-rc.d/init-certbot-config/run: line 372:   691 Illegal instruction     certbot certonly --non-interactive --renew-by-default
───────────────────────────────────────

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

   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:    99
User GID:    100
───────────────────────────────────────

using keys found in /config/keys
Variables set:
PUID=99
PGID=100
TZ=America/Los_Angeles
URL=<redacted>
SUBDOMAINS=<redacted>
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=false
VALIDATION=http
CERTPROVIDER=
DNSPLUGIN=<redacted>
EMAIL=email@email.com
STAGING=false

**** Permissions could not be set. This is probably because your volume mounts are remote or read-only. ****
**** The app may not work properly and we will not provide support for it. ****
Using Let's Encrypt as the cert provider
SUBDOMAINS entered, processing
Sub-domains processed are: <redacted>
E-mail address entered: email@email.com
http validation is selected
Generating new certificate
ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

Permissions:

> ls -l /config/keys
total 11
-rwxrwxrwx 1 abc  abc  1342 Apr 16 09:34 cert.crt
-rwxrwxrwx 1 abc  abc  1704 Apr 16 09:34 cert.key
lrwxrwxrwx 1 root root   43 Apr 24 19:18 letsencrypt -> ../etc/letsencrypt/live/<redacted>

I also tried changing PUID to 0 (root), no success.

I also had this working a few weeks ago, and then something happened to cause SWAG to stop working.

I don’t have a phone number to provide to discord.

I downgraded to version-2.9.0, and it works now.

thank you for that info, ill pass this to the team. unfortunately this is the first instance we’ve seen so it may take some time to determine what the issue is, especially with you being unwilling to join discord.

what is your CPU?

what is your CPU?

AMD Athlon II X4 635

There have been recent changes to some libraries like lxml that now require features that 15 yr old cpus don’t support

I’m afraid there is no fix or workaround at the moment and it will likely get worse as more libraries follow suit

Thank you for the assistance.

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