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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Still having issues with Confconsole Let's Encrypt plugin with DNS-01 challenge setup #1895

Closed
JedMeister opened this issue Jan 25, 2024 · 0 comments 路 Fixed by turnkeylinux/confconsole#83

Comments

@JedMeister
Copy link
Member

As reported by Mark in the forums, despite spending a ton of time and energy on fixing it (see #1876) it seems that there are still issues with the setup component of Confconsole Let's Encrypt plugin - DNS-01 challenge. 馃槩

I'm 99.9% certain that I explicitly tested that exact same appliance (v18.0 OpenLDAP) prior to release (albeit in a VM rather than a container), but still it's not quite right. I can only assume that there is some race condition somewhere in the code?

I note that after following the manual instructions I gave him (which I copy/pasted from #1876 (comment) - which essentially does what the python code does) he got it working.

However, I also note that he also said:

I had to pip install python3.1-venv but otherwise worked

And in the original issue thread zndrr noted:

apt install python3.11-venv

Was required.

That particular Debian package (and the python3.1-venv noted by Mark) should be essentially the same. I also note that the python3.11-venv Debian package is a dependency of python3-venv which is what Confconsole should be installing!?

So despite the fact that it seemed to work ok for me, my guess is that it is indeed a race condition and it occurs when installing python3-venv from Debian!?

I've pinned this to the v18.1 milestone, but ideally I'd like to look a bit closer sooner than that.

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

Successfully merging a pull request may close this issue.

1 participant