Closed kradalby closed 4 years ago
Sorry for the slow reply on this. Can you share the arguments you're passing to simp_le, and also a full log having passed --verbose
?
Hi there,
Also facing this issue. See this issue for an error log: https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion/issues/634
@zenhack Is my error log sufficent, or do you need any additional information to troubleshoot the issue?
@OscarKolsrud, would you be willing to share that log with the certs not censored? It looks like the issue is that it's somehow not parsing that correctly, so having those removed from the log makes it hard to debug. (If it says "certificate" it's the public part of the cert, so not sensitive, but if you want to avoid sharing it with the whole world anyway, you can email me, address in the commit logs).
@zenhack Working on sending those over now via email.... Expect them from the email oscar @
Sending over the logs of a completely new instance of the docker nginx lets encrypt companion using buypass as CA
@zenhack I might be able to help if @OscarKolsrud is ok about sharing the cert with me too.
@buchdag Check your gmail (the one listed in your github profile)
Can confirm pull request https://github.com/zenhack/simp_le/pull/137 solved this issue
Ok, the fix is on master. I'll try to get a release out soonish.
@zenhack could you try to release the fixed version as soon as convenient for you ? It can't go into letsencrypt-nginx-proxy-companion
if this isn't a tagged release.
Done.
Hi
I attempted to use BuyPass as my ACME provider through this docker project https://github.com/jwilder/docker-letsencrypt-nginx-proxy-companion.
But I keep getting this:
The documentation and ACME URL for BuyPass is provided here: https://community.buypass.com/t/k9r5cx/get-started
Any idea why this might happen?