Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Catch renew errors & Delete certs #173

Closed
prionkor opened this issue Apr 2, 2019 · 3 comments
Closed

Catch renew errors & Delete certs #173

prionkor opened this issue Apr 2, 2019 · 3 comments
Milestone

Comments

@prionkor
Copy link

prionkor commented Apr 2, 2019

We have a white labeled part in our app where we provide le ssl for our users. However in few cases users changes their domain or no longer using our app in those cases attempt to renew domain fails. Here is a related log:

Processing login.example.com
 + Checking domain name(s) of existing cert... unchanged.
 + Checking expire date of existing cert...
 + Valid till Apr  1 12:40:01 2019 GMT (Less than 30 days). Renewing!
 + Signing domains...
 + Generating private key...
 + Generating signing request...
 + Requesting authorization for login.example.com...
 + 1 pending challenge(s)
 + Deploying challenge tokens...
 + Responding to challenge for login.example.com authorization...
Invalid challenge: DOMAIN=login.example.com RESPONSE={
  "type": "http-01",
  "status": "invalid",
  "error": {
    "type": "urn:acme:error:connection",
    "detail": "dns :: DNS problem: NXDOMAIN looking up A for login.example.com",
    "status": 400
  },
  "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/-UWJLolllllllllllllllllll/14288788129",
  "token": "-GgMs_L_llllllllllllllloTb6fw1CKKZoic"
}

Is it possible to perhaps cache these errors and remove these domains certs from the directory so the auto ssl doesn't attempt to renew them again?

@prionkor prionkor changed the title Cache renew errors & Delete certs Catch renew errors & Delete certs Apr 3, 2019
@danDanV1
Copy link

Related to an issue I opened. A possible solution is here: #150 (comment)

@prionkor
Copy link
Author

@edeis53 Thank you, the solution provides catching the now allowed domain. Not expired or DNS errored domains

@GUI
Copy link
Collaborator

GUI commented Sep 30, 2019

I think this should hopefully be resolved in v0.13.0 between the combination of #176 and #128. Sorry for the long delay in addressing this! So I'm going to close this, but let me know if there were still any outstanding issues with the behavior in the new release.

@GUI GUI closed this as completed Sep 30, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants