greenlock 2.7.2 broke usage with "dynip domain names" #38

Closed
opened 2019-05-14 07:02:19 +00:00 by Ghost · 3 comments

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

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
Owner

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.

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.
coolaj86 referenced this issue from a commit 2019-11-01 11:10:12 +00:00
Owner

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.

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.
Author

cool to hear ...

cool to hear ...
Sign in to join this conversation.
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coolaj86/greenlock.js-ARCHIVED#38
No description provided.