Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS RHEL workshop provisioning failing at TASK [acme.sh to issue certs with session token] #177

Open
benblasco opened this issue Feb 21, 2022 · 5 comments

Comments

@benblasco
Copy link
Contributor

benblasco commented Feb 21, 2022

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.

@benblasco
Copy link
Contributor Author

Will share logs privately for review.

@dmc5179
Copy link
Contributor

dmc5179 commented Feb 21, 2022

@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.

@benblasco
Copy link
Contributor Author

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.

@ajacocks
Copy link
Contributor

I’ll take a look at this and see what is going on.

@benblasco
Copy link
Contributor Author

I made no changes and re-ran everything tonight, and it went through cleanly. Possibility of a transient issue with LetsEncrypt itself?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants