letsencrypt dns-directadmin not working anymore

[DirkKalkman]

Describe the issue you are experiencing

certbot-dns-directadmin packed is version 1.04
This does not work with directadmin anymore and produces an error:
Encountered exception during recovery: ValueError: too many values to unpack (expected 2)

This is fixed in version 1.06

What type of installation are you running?

Home Assistant Supervised

Which operating system are you running on?

Debian

Which add-on are you reporting an issue with?

Let's Encrypt

What is the version of the add-on?

5.2.1

Steps to reproduce the issue

1. Request certificate with dns-directadmin

System Health information

System Information

version	core-2024.10.0
installation_type	Home Assistant Supervised
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.12.4
os_name	Linux
os_version	6.6.47+rpt-rpi-2712
arch	aarch64
timezone	Europe/Amsterdam
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	5000
Installed Version	2.0.1
Stage	running
Available Repositories	1428
Downloaded Repositories	1

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Debian GNU/Linux 12 (bookworm)
update_channel	stable
supervisor_version	supervisor-2024.09.1
agent_version	1.6.0
docker_version	27.3.1
disk_total	200.0 GB
disk_used	10.4 GB
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
supervisor_api	ok
version_api	ok
installed_addons	NGINX Home Assistant SSL proxy (3.11.0), Vaultwarden (Bitwarden) (0.23.0), File editor (5.8.0), Get HACS (1.3.1), Syncthing (1.19.0), Let's Encrypt (5.2.1)

Dashboards

dashboards	2
resources	0
views	0
mode	storage

Recorder

oldest_recorder_run	September 26, 2024 at 4:54 PM
current_recorder_run	October 3, 2024 at 9:31 AM
estimated_db_size	29.37 MiB
database_engine	sqlite
database_version	3.45.3

Anything in the Supervisor logs that might be useful for us?

No response

Anything in the add-on logs that might be useful for us?

s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun lets-encrypt (no readiness notification)
s6-rc: info: service legacy-services successfully started
[15:12:16] INFO: Selected DNS Provider: dns-directadmin
[15:12:16] INFO: Use propagation seconds: 300
[15:12:16] INFO: Detecting existing certificate type for jarvis.kalkman.eu
Saving debug log to /var/log/letsencrypt/letsencrypt.log
[15:12:17] INFO: No certificate found - using 'ecdsa' key type.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for jarvis.kalkman.eu
Encountered exception during recovery: ValueError: too many values to unpack (expected 2)
An unexpected error occurred:
ValueError: too many values to unpack (expected 2)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Additional information

No response

[mantaalex]

I have the same problem i hope someone can fix it

[mantaalex]

s6-rc: info: service legacy-services successfully started [22:28:31] INFO: Selected DNS Provider: dns-directadmin [22:28:31] INFO: Use propagation seconds: 60 ./run: line 317: unexpected EOF while looking for matching ''
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/file-structure.sh
cont-init: info: /etc/cont-init.d/file-structure.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun lets-encrypt (no readiness notification)
s6-rc: info: service legacy-services successfully started
[03:00:04] INFO: Selected DNS Provider: dns-directadmin
[03:00:04] INFO: Use propagation seconds: 60
./run: line 317: unexpected EOF while looking for matching '' s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting cont-init: info: running /etc/cont-init.d/file-structure.sh cont-init: info: /etc/cont-init.d/file-structure.sh exited 0 s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting services-up: info: copying legacy longrun lets-encrypt (no readiness notification) s6-rc: info: service legacy-services successfully started [21:17:59] INFO: Selected DNS Provider: dns-directadmin [21:17:59] INFO: Use propagation seconds: 60 ./run: line 317: unexpected EOF while looking for matching ''
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/file-structure.sh
cont-init: info: /etc/cont-init.d/file-structure.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun lets-encrypt (no readiness notification)
s6-rc: info: service legacy-services successfully started
[21:21:50] INFO: Selected DNS Provider: dns-directadmin
[21:21:50] INFO: Use propagation seconds: 60
./run: line 317: unexpected EOF while looking for matching '' s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting cont-init: info: running /etc/cont-init.d/file-structure.sh cont-init: info: /etc/cont-init.d/file-structure.sh exited 0 s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting services-up: info: copying legacy longrun lets-encrypt (no readiness notification) s6-rc: info: service legacy-services successfully started [21:22:10] INFO: Selected DNS Provider: dns-directadmin [21:22:10] INFO: Use propagation seconds: 60 ./run: line 317: unexpected EOF while looking for matching ''
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped`

[mantaalex]

anyone an idea to fix this manually?

[Rolfieo]

Looks like i'm not the only one. I have indeed exactly the same issue.

Encountered exception during recovery: ValueError: too many values to unpack (expected 2)
An unexpected error occurred:
ValueError: too many values to unpack (expected 2)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile 

[sloetr]

I encountered the same issue.

For me, the temporary fix was to downgrade to version 5.1.0. This can be done by taking a backup of the add-on, replace the version number in the backup files with 5.1.0 (3 times in my situation) and then restore that backup.

[MathieuIci]

If your certificate is about to expire and need a temporary fix, the above suggestion worked for me. I downgraded the Let's Encrypt add-on to version 5.1.0 by restoring an old backup and now all is well:

[peterwesterlund]

I encountered the same issue.

For me, the temporary fix was to downgrade to version 5.1.0. This can be done by taking a backup of the add-on, replace the version number in the backup files with 5.1.0 (3 times in my situation) and then restore that backup.

Would you mind sharing your tar file? I have tried myself but I can't get it tor work. I suspect something gets wrong when I compress it back and forth.

[sloetr]

I used 7-Zip to edit the .tar file. The backup.json file is located in the '.' folder. I won't share my .tar file since it requires me to remove a lot of security related information, sorry.

[old-square-eyes]

Same problem. Also finding the instructions very unclear. Does this open up ports on the built-in haos web server, and reference the installed certs (if you can ever get them to install)? Or do I need yet another web server like the NGINX Addon.

How does it interact with default 8123 (or is 8123 reserved for MDNS)?

I already have a reverse proxy downstream. I just want to point to HA so I can use a Cloudflare tunnel (like I do with my other websites). Nothing but 502 errors doing that.