greenlock 2.7.2 broke usage with "dynip domain names" #38
Cargando…
Referencia en una nueva incidencia
No se ha proporcionado una descripción.
Eliminar rama "%!s(<nil>) "
Eliminar una rama es permanente. Aunque la rama eliminada puede continuar existiendo durante un corto tiempo antes de que sea eliminada, en la mayoría de los casos NO PUEDE deshacerse. ¿Continuar?
We have reports from users from our project thet 2.7.2 of greenlock broke the usage with a external dynip domain. see https://github.com/ioBroker/ioBroker.js-controller/issues/372
In the commit of that I only saw that a check was changed from "domain" to "challenge.altname" ... maybe it has somehting to do with this?
Thank you for checking this issue.
Ingo
Can you give me a sample config and and the plugins that were being used?
I'm having difficulty reading the issue, but there should not be a breaking change and I want to fix the issue as soon as possible.
Greenlock v3 is out and v2 is deprecated.
v3 has a much simpler set of challenge callbacks with a full test suite.
I'll put up a video on how to use it soon.
cool to hear ...