Edge certificate installation problems #3147
Replies: 1 comment
-
|
It was a typo in the config. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've gone through the web installer but couldn't to receive a certificate using an existing wildcard cert for godaddy or a letsencrypt certificate.
Here is the log from the letsencrypt attempt:
2026-06-30T19:48:56.518837974+00:00 LEVEL(INFO) defguard_proxy::acme: message=Starting ACME HTTP-01 certificate issuance for domain: testserver.testdomain.com
2026-06-30T19:48:56.518857269+00:00 LEVEL(INFO) defguard_proxy::http: message=ACME task requested port 80; pausing HTTP server
2026-06-30T19:48:56.518871617+00:00 LEVEL(INFO) defguard_proxy::acme: message=Using Let's Encrypt production environment
2026-06-30T19:48:56.518882354+00:00 LEVEL(INFO) defguard_proxy::acme: message=DNS pre-flight check for domain: testserver.testdomain.com
2026-06-30T19:48:56.663973265+00:00 LEVEL(INFO) defguard_proxy::acme: message=DNS pre-flight: domain 'testserver.testdomain.com' resolved (A record found)
2026-06-30T19:48:56.664013395+00:00 LEVEL(INFO) defguard_proxy::acme: message=No stored ACME account found; creating a new one with Let's Encrypt
2026-06-30T19:48:56.675172296+00:00 LEVEL(INFO) defguard_proxy::acme: message=Registering account at ACME directory: https://acme-v02.api.letsencrypt.org/directory
2026-06-30T19:48:56.887220409+00:00 LEVEL(INFO) defguard_proxy::acme: message=ACME account registered successfully
2026-06-30T19:48:56.977489227+00:00 LEVEL(INFO) defguard_proxy::acme: message=ACME order placed for domain: testserver.testdomain.com
2026-06-30T19:48:56.977549652+00:00 LEVEL(INFO) defguard_proxy::acme: message=Waiting for main HTTP server to release port 80 before ACME challenge bind
2026-06-30T19:48:56.977560319+00:00 LEVEL(INFO) defguard_proxy::acme: message=Port 80 released by main HTTP server; binding for ACME challenge
2026-06-30T19:48:56.977615928+00:00 LEVEL(INFO) defguard_proxy::acme: message=ACME challenge server listening on port 80
2026-06-30T19:48:57.035122961+00:00 LEVEL(INFO) defguard_proxy::acme: message=Preparing HTTP-01 challenge for domain: testserver.testdomain.com (token: ZcWgOW0Y3cc-JVdnyUnPFwyQpSbwfisNNuiJ454AWdc)
2026-06-30T19:48:57.091092660+00:00 LEVEL(INFO) defguard_proxy::acme: message=HTTP-01 challenge signalled as ready; waiting for Let's Encrypt to validate
2026-06-30T19:48:57.091122238+00:00 LEVEL(INFO) defguard_proxy::acme: message=Polling Let's Encrypt for domain validation result...
2026-06-30T19:49:13.129960206+00:00 LEVEL(INFO) defguard_proxy::acme: message=ACME challenge server shut down; port 80 released
2026-06-30T19:49:13.130041253+00:00 LEVEL(ERROR) defguard_proxy::grpc: message=ACME HTTP-01 failed for domain 'testserver.testdomain.com': ACME order did not become ready: timed out waiting for an order update
I have changed the server name in the above log entry.
Port 80 is open to the server on the firewall so it shouldn't be blocking LetsEncrypt.
The edge server name is accessible via public dns.
Additionally, the edge server says that the "Core is disconnected" when I access it using a web browser.
The web ui on the core server shows that the edge server and the gateway are online.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions