Empty private key file generated

[clauderobi]

This was tested using the latest master commit: de14d59bb38acc66972787e1f4b058b02619c933

The key file generated while creating an SSL certificate is empty.

This is using Gandi as the DNS provider and Lets Encrypt.

The certificate is good.

Tested with the 2 Lets encrypt servers (prod and staging).

Steps to reproduce

./acme.sh/acme.sh --debug 2 --force --issue --server https://acme-staging-v02.api.letsencrypt.org/directory --dns dns_gandi_livedns --config-home /mnt/data/sbox/NearEDGE/demo/acmeShell/build -d nsl.demo.nearedge.io --log /tmp/acme.log --key-file /mnt/data/sbox/NearEDGE/demo/acmeShell/key.pem

The key-file argument was added for simplicity but even without it no key files gets generated.

The disk location and permission are both Ok (the file do get generated, it is just empty). acmeBug.txt

Debug log

There is nothing suspicious (to my naked eye, as well as gemini's)

I obviously redacted some of the data in the log.

acmeBug.txt

[github-actions[bot]]

Please upgrade to the latest code and try again first. Maybe it's already fixed. acme.sh --upgrade If it's still not working, please provide the log with --debug 2, otherwise, nobody can help you.

[clauderobi]

I am using the latest, by doing a git pull.

AS you can see on the command line I am using --debug 2 and I did provide the log.

Mr Bot, please read carefully before commenting!

[Neilpang]

what is in this file:

cat   /mnt/data/sbox/NearEDGE/demo/acmeShell/build/nsl.demo.nearedge.io_ecc/nsl.demo.nearedge.io.key