Open benblasco opened 2 years ago
Will share logs privately for review.
@benblasco I'm not sure how the deployment of this workshop uses acme.sh but I ran into an issue using acme.sh earlier this year for something else. It turned out some dependencies in the acme.sh tool had changed. I had to delete my git checkout of acme.sh and any config files for it, clone the repo again and it worked right away. It seemed like my old checkout had the earlier dependencies or cache or something in it that was causing an issue.
Hi @dmc5179 thanks for letting me know. This was a fresh checkout on a fresh fedora 35 VM and deployment was via a container. Will have a look again tomorrow. @ajacocks has a copy of the logs as they may contain sensitive data I cannot post here.
I’ll take a look at this and see what is going on.
I made no changes and re-ran everything tonight, and it went through cleanly. Possibility of a transient issue with LetsEncrypt itself?
Workshop provisioner failing at the mentioned step. Tested via native Fedora/RHEL deployment by my colleague Mark, and in container format by me. Logs attached appear to show a
Create account key error.
Is this a transient issue or has something changed at the LetsEncrypt end? I see our code hasn't changed at all in 2022, and I deployed this workshop successfully earlier this month.