acme: Let's Encrypt certificates stuck in PENDING after upgrade from 1.16 to 1.19.2 (EE-Latest)
### Describe the Bug
Hi,
I recently upgraded our Pangolin deployment from version 1.16 to the current 1.19.2. As part of this upgrade process, I performed the following steps:
1. Upgraded all corresponding dependencies (gerbil, trafik, and bager).
2. Switched the image tag from community to ee-latest.
3. Generated and configured a valid license key for enterprise operation.
The core application starts up, but I am now facing an issue with ACME certificate generation. Let's Encrypt certificates are no longer being issued successfully; the challenge status remains stuck at PENDING indefinitely. Prior to the upgrade, certificate generation worked flawlessly.
I suspect there might be a configuration change between 1.16 and 1.19.2 or an issue related to how traffic is routed to the validation endpoint after the upgrade.
Note: Existing Let's Encrypt certificates that were created under version 1.16 (or earlier) are still working fine and remain valid. The issue only affects new certificates or renewals.
Log (anonymized):
---
look my next post
---
Any idea?
### Environment
- OS Type & Version: Debian Trixie, acutal
- Pangolin Version: 1.19.2
- Edition (Community or Enterprise): Enterprise
- Gerbil Version: 1.4.2
- Traefik Version: 3.7.5
- Newt Version: 1.13.0
- Client Version:
### To Reproduce
?
### Expected Behavior
?
9 条评论