ERROR curl failed with 0 and returned ""

[pherrera-tamu]

I have the latest client v2.49, running on Ubuntu 24.04.
I've configured GetSSL with a private_key.pem generated via acme-toolkit.py script using https://acme.enterprise.sectigo.com as the CA.
When attempting to generate a certificate, I'm getting the following error:

ERROR curl "https://acme.enterprise.sectigo.com/new-nonce" failed with 0 and returned ""

I've attached debug text.

I have a working instance of GetSSL with a different CA https://acme.sectigo.com/v2/InCommonRSAOV. I don't see a significant difference in the getssl.cfg between the two instances. Ideas for debugging and solutions are appreciated.

getssl-debug.txt

[pherrera-tamu]

UPDATE: To make sure my EAB ID and key were good, I successfully generated a certificate using Certbot.

[timkimber]

Hi @pherrera-tamu

Thanks for reporting this and thinks for including the logs. It's very strange as it appears to have failed on accepting the terms of service, but I would have hoped to get an error message back if there was a problem with that request. I'll see if I can reproduce and fix.

[adaugherity]

I think this is same as #859, which has been fixed but only in git, after the latest release.

Pablo, we should test this again with the latest getssl from git master.

[timkimber]

Thanks @adaugherity I'd noticed that the line numbers from the log file didn't match with with the current release but didn't realise that this bug has already been fixed! I'll push a new release version soon

[pherrera-tamu]

I ran with git master branch version with --account-id and attached output. Now I'm getting 400 error with badNonce.

debug-2.txt

[adaugherity]

I think badNonce would be fixed by my other PR, but that's not the real problem since it appears to generate a new nonce and then retry. This is now looking like a key/credential error, but I'm pretty sure we've successfully used this key before... strange.