and then no thing, no error!
Please mind some.pl or whatever is not registered, so ERROR was correct output.
The problem is no output at all since Fi May 20 night.
Originally created by @bobykus on GitHub (May 23, 2016).
Seems letsencrypt behavior changed recently. Using your tool
_/usr/local/sbin/letsencrypt.sh --cron --domain some.pl --domain www.some.pl --challenge http-01 --config .../some.pl.dk/.letsencrypt/config.sh_
were getting
_ERROR: Challenge is invalid! (returned: invalid) (result: {"type":"http-01","status":"invalid","error":{"type":"urn:acme:error:connection","detail":"DNS problem: NXDOMAIN looking up A for some.pl"},"uri":"https://acme-v01.api.letsencrypt.org/acme/challenge/yx4xQiXuFusLu-MFtAnUFXcBxoIqWWImKq05mNdS0Uw/90567863","token":"hT5T7cDEGdnt4UvHPR4jFkt1C9kU4uoMau3hsp9BxZ4","keyAuthorization":"hT5T7cDEGdnt4UvHPR4jFkt1C9kU4uoMau3hsp9BxZ4.6KqDpmIgUn413LbT6leEv1TfILZqkDmTU7_fuM25T5I","validationRecord":[{"url":"http://some.pl/.well-known/acme-challenge/hT5T7cDEGdnt4UvHPR4jFkt1C9kU4uoMau3hsp9BxZ4","hostname":"some.pl","port":"80","addressesResolved":null,"addressUsed":""}]})_
from Fri May 20 20:50:10 CEST 2016 I getting only
_\+ Requesting challenge for some.pl..._
and then no thing, no error!
Please mind some.pl or whatever is not registered, so ERROR was correct output.
The problem is no output at all since Fi May 20 night.
DNS problem: NXDOMAIN looking up A for some.pl: letsencrypt can't resolve your domain name and can't access your page for receiving the challenge response
@lukas2511 commented on GitHub (May 23, 2016):
This is not a problem with this script.
`DNS problem: NXDOMAIN looking up A for some.pl`: letsencrypt can't resolve your domain name and can't access your page for receiving the challenge response
No, I think your script works perfect. I just trying to say letsencrypt site returns no error or different looked message while error happens. It seems to be changed last Friday. Just FYI.
@bobykus commented on GitHub (May 23, 2016):
No, I think your script works perfect. I just trying to say letsencrypt site returns no error or different looked message while error happens. It seems to be changed last Friday. Just FYI.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @bobykus on GitHub (May 23, 2016).
Seems letsencrypt behavior changed recently. Using your tool
/usr/local/sbin/letsencrypt.sh --cron --domain some.pl --domain www.some.pl --challenge http-01 --config .../some.pl.dk/.letsencrypt/config.sh
were getting
ERROR: Challenge is invalid! (returned: invalid) (result: {"type":"http-01","status":"invalid","error":{"type":"urn:acme:error:connection","detail":"DNS problem: NXDOMAIN looking up A for some.pl"},"uri":"https://acme-v01.api.letsencrypt.org/acme/challenge/yx4xQiXuFusLu-MFtAnUFXcBxoIqWWImKq05mNdS0Uw/90567863","token":"hT5T7cDEGdnt4UvHPR4jFkt1C9kU4uoMau3hsp9BxZ4","keyAuthorization":"hT5T7cDEGdnt4UvHPR4jFkt1C9kU4uoMau3hsp9BxZ4.6KqDpmIgUn413LbT6leEv1TfILZqkDmTU7_fuM25T5I","validationRecord":[{"url":"http://some.pl/.well-known/acme-challenge/hT5T7cDEGdnt4UvHPR4jFkt1C9kU4uoMau3hsp9BxZ4","hostname":"some.pl","port":"80","addressesResolved":null,"addressUsed":""}]})
from Fri May 20 20:50:10 CEST 2016 I getting only
+ Requesting challenge for some.pl...
and then no thing, no error!
Please mind some.pl or whatever is not registered, so ERROR was correct output.
The problem is no output at all since Fi May 20 night.
@lukas2511 commented on GitHub (May 23, 2016):
This is not a problem with this script.
DNS problem: NXDOMAIN looking up A for some.pl: letsencrypt can't resolve your domain name and can't access your page for receiving the challenge response@bobykus commented on GitHub (May 23, 2016):
No, I think your script works perfect. I just trying to say letsencrypt site returns no error or different looked message while error happens. It seems to be changed last Friday. Just FYI.
@lukas2511 commented on GitHub (May 23, 2016):
Do you have the newest version of this script? There have been important changes.
@bobykus commented on GitHub (May 23, 2016):
No, but I will try.
@bobykus commented on GitHub (May 23, 2016):
It looks very nice now - response contains much more readable info. Thank you so much!