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

Let's encrypt request error #79

Closed
pvanhemmen opened this issue Nov 1, 2019 · 1 comment
Closed

Let's encrypt request error #79

pvanhemmen opened this issue Nov 1, 2019 · 1 comment

Comments

@pvanhemmen
Copy link

Hey there,

I'm trying to configure proxmox with let's encrypt support enabled. During installation I run into the following issue:

TASK [systemli.letsencrypt : register Let's Encrypt certificate with HTTP challenge] ***************************************************************************************************************************************************************************************************************************************
fatal: [vm1.my.domain]: FAILED! => {"msg": "The conditional check 'not \"no action taken\" in letsencrypt_reg_certbot_http.stdout' failed. The error was: error while evaluating conditional (not \"no action taken\" in letsencrypt_reg_certbot_http.stdout): Unable to look up a name or access an attribute in template string ({% if not \"no action taken\" in letsencrypt_reg_certbot_http.stdout %} True {% else %} False {% endif %}).\nMake sure your variable name does not contain invalid characters like '-': argument of type 'AnsibleUndefined' is not iterable"}

ansible 2.8.5 on macOS 10.15.1
Debian 10.1
Proxmox 6.0-9

I don't know if it's related but I found a similar issue here: #31. If this problem not related to this role please feel free to close this issue.

Thanx

@lae
Copy link
Owner

lae commented Nov 1, 2019

Hi, thanks for the report. The current implementation this role takes for LE I'm not personally supporting, since PVE introduced LE support internally, and there is currently an open issue to move the role over to it (#34). @mejo- may want to pitch in some thoughts, however.

For the time being, I would recommend you use PVE's certificate management until #34 gets implemented (which'll depend on when I have time, or another contributor does - I'll keep this issue open since someone else might have the same problem).

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

2 participants