You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I can tell, letsencrypt is responding with a 'dns-01' challenge, which simp_le is blowing up on. I believe it previously received a 'http-01' challenge as expected. I'm not sure what changed -- but is there a way to force a http-01 challenge? or to continue gracefully after receiving dns-01 and ask for a http-01 challenge?
I'll attach the full output of our container. The first line contains flags passed to the simp_le client.
so as an update -- this only happens if the domain contains uppercase characters. E.g. our example of AAA.qa-1.blueacorn.net' works when it is replaced with aaa.qa-1.blueacorn.net. I'll see if I can submit a patch.
I'm using simp_le via the https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion to automatically give SSL to our https containers. This has worked fine until now.
From what I can tell, letsencrypt is responding with a 'dns-01' challenge, which simp_le is blowing up on. I believe it previously received a 'http-01' challenge as expected. I'm not sure what changed -- but is there a way to force a http-01 challenge? or to continue gracefully after receiving dns-01 and ask for a http-01 challenge?
I'll attach the full output of our container. The first line contains flags passed to the simp_le client.
towards the end we see the error:
below is the full output:
The text was updated successfully, but these errors were encountered: