Replies: 2 comments 1 reply
-
|
@morikplay it's possible the CA process itself is not able to resolve the |
Beta Was this translation helpful? Give feedback.
-
|
Thank yoou @hslatman for your patience and willingness to help. Same result from running dig for client from CA dig for CA from client step-ca service: docker-central log: step-ca logs: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello experts,
I've searched these discussions, stackoverflow, reddit, and few other avenues for answers but I was unable to find a solution.
The issue
step-ca 0.24.2 linux/amd64was installed, configured and working fine (100+ certs issued) for past 1.5 years. Few days ago, it stopped working. Network topology or configuration have not changed. Upgrade to0.27.2hasn't fixed the issue either.ca.json
Scenario
certbotfrom a newly provisioned VM attempting to acquire a cert usingclient-side result:
step-ca side error:
What can be ruled out?
docker-central.esco.ghaar) can ping server (ldap.esco.ghaar)curlissued from server when client has spun a standalone server and is re-trying attempts to server succeeds withI'd be grateful for pointers steering me in the right direction.
Thank you in advance.
Beta Was this translation helpful? Give feedback.
All reactions