bug?An error occurred while applying for a certificate, error

[hktalent]

projectdiscovery/interactsh v1.0.7

1.6746582486760027e+09  error   acme_client     cleaning up solver      {"identifier": "*.xxx1.com", "challenge_type": "dns-01", "error": "no memory of presenting a DNS record for \"_acme-challenge.xxx1.com\" (usually OK if presenting also failed)"}
1.6746582487523222e+09  error   obtain  could not get certificate from issuer   {"identifier": "*.xxx1.com", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[*.xxx1.com] solving challenges: waiting for solver certmagic.solverWrapper to be ready: checking DNS propagation of \"_acme-challenge.xxx1.com\": dial tcp: lookup ns1.xxx1.com.: i/o timeout (order=https://acme-v02.api.letsencrypt.org/acme/order/933097807/160934339777) (ca=https://acme-v02.api.letsencrypt.org/directory)"}
1.674658248753018e+09   info    obtain  releasing lock  {"identifier": "*.xxx1.com"}
[ERR] An error occurred while applying for a certificate, error: [*.xxx1.com] Obtain: [*.xxx1.com] solving challenges: waiting for solver certmagic.solverWrapper to be ready: checking DNS propagation of "_acme-challenge.xxx1.com": dial tcp: lookup ns1.xxx1.com.: i/o timeout (order=https://acme-v02.api.letsencrypt.org/acme/order/933097807/160934339777) (ca=https://acme-v02.api.letsencrypt.org/directory)

error   acme_client     cleaning up solver      {"identifier": "*.xxx2.com", "challenge_type": "dns-01", "error": "no memory of presenting a DNS record for \"_acme-challenge.xxx2.com\" (usually OK if presenting also failed)"}
1.6746582711675534e+09  error   obtain  could not get certificate from issuer   {"identifier": "*.xxx2.com", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[*.xxx2.com] solving challenges: waiting for solver certmagic.solverWrapper to be ready: checking DNS propagation of \"_acme-challenge.xxx2.com\": dial tcp: lookup ns1.xxx1.com.: i/o timeout (order=https://acme-v02.api.letsencrypt.org/acme/order/933097807/160934403287) (ca=https://acme-v02.api.letsencrypt.org/directory)"}
1.6746582711682625e+09  info    obtain  releasing lock  {"identifier": "*.xxx2.com"}

An error occurred while applying for a certificate, error: [*.xxx2.com] Obtain: [*.xxx2.com] solving challenges: waiting for solver certmagic.solverWrapper to be ready: checking DNS propagation of "_acme-challenge.xxx2.com": dial tcp: lookup ns1.xxx1.com.: i/o timeout (order=https://acme-v02.api.letsencrypt.org/acme/order/933097807/160934403287) (ca=https://acme-v02.api.letsencrypt.org/directory)

ns1\ns2 is ok

[thepoorhacker]

Hello,
I am getting this error while applying for certificates:
[ERR] An error occurred while applying for a certificate, error: [*.mydomain.com] Obtain: [*.mydomain.com] solving challenges: waiting for solver certmagic.solverWrapper to be ready: checking DNS propagation of "_acme-challenge.mydomain.com": EOF (order=https://acme-v02.api.letsencrypt.org/acme/order/) (ca=https://acme-v02.api.letsencrypt.org/directory)

I am using version: 1.1.0
Regards

[Mzack9999]

@thepoorhacker Sometimes, let's encrypt resolver is unable to reach the interactsh-server due to propagation errors which are difficult to investigate and fix. As a generic solution, you can try to obtain them via certbot and then specify their path with interactsh-server command line flags

[thepoorhacker]

it really was a propagation error, and I solved the problem. Thanks

…

On Wed, Mar 15, 2023 at 1:40 AM Mzack9999 ***@***.***> wrote: @thepoorhacker <https://github.com/thepoorhacker> Sometimes, let's encrypt resolver is unable to reach the interactsh-server due to propagation errors which are difficult to investigate and fix. As a generic solution, you can try to obtain them via certbot and then specify their path with interactsh-server command line flags — Reply to this email directly, view it on GitHub <#447 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQFLEWKBZKD5AVN2Y45WJGDW4DXXFANCNFSM6AAAAAAUG752SY> . You are receiving this because you were mentioned.Message ID: ***@***.***>