pangolin | 2026-04-29T22:51:23+00:00 [warn]: Certificate not found for domain: domain1
pangolin | 2026-04-29T22:51:23+00:00 [warn]: Certificate not found for domain: domain1
pangolin | 2026-04-29T22:51:23+00:00 [warn]: Certificate not found for domain: domain1
pangolin | 2026-04-29T22:51:23+00:00 [warn]: Certificate not found for domain: domain1
Additional info:
-I use DNS-01 challenge for a wildcard certificate.
-I only have one domain.
Expected Behavior
All certificates are fine.
Originally created by @Schnookeuz on GitHub (Apr 29, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2935
### Describe the Bug
I updated to v1.18.1 and the new certificate indicator for private ressources shows that the certificate is invalid.
### Environment
- OS Type & Version: Debian 13
- Pangolin Version: 1.18.1 EE
- Gerbil Version: 1.3.1
- Traefik Version: 3.6.14
- Newt Version: 1.12.2
### To Reproduce
- Update to v1.18.1
- Create a privateConfig.yml in config/ with content (i also tried without that):
```
acme:
acme_json_path: "config/letsencrypt/acme.json"
sync_interval_ms: 5000
```
- Start Compose stack
- Go to private ressouces
<img width="1075" height="662" alt="Image" src="https://github.com/user-attachments/assets/71d1a739-d34a-4b7c-ad5c-78dafae3cd01" />
The logs are showing:
```
pangolin | 2026-04-29T22:51:23+00:00 [warn]: Certificate not found for domain: domain1
pangolin | 2026-04-29T22:51:23+00:00 [warn]: Certificate not found for domain: domain1
pangolin | 2026-04-29T22:51:23+00:00 [warn]: Certificate not found for domain: domain1
pangolin | 2026-04-29T22:51:23+00:00 [warn]: Certificate not found for domain: domain1
```
Additional info:
-I use DNS-01 challenge for a wildcard certificate.
-I only have one domain.
### Expected Behavior
All certificates are fine.
GiteaMirror
added the bug label 2026-06-15 09:45:30 -05:00
I also entered a shell inside the pangolin container and my acme.json is accessible:
root@pangolin:~# docker exec -it pangolin /bin/bash
root@fe18cd5de0b0:/app# ls -l config/letsencrypt/acme.json
-rw------- 1 root root 7922 Mar 12 21:07 config/letsencrypt/acme.json
<!-- gh-comment-id:4348123061 -->
@Schnookeuz commented on GitHub (Apr 29, 2026):
I also entered a shell inside the pangolin container and my acme.json is accessible:
```
root@pangolin:~# docker exec -it pangolin /bin/bash
root@fe18cd5de0b0:/app# ls -l config/letsencrypt/acme.json
-rw------- 1 root root 7922 Mar 12 21:07 config/letsencrypt/acme.json
```
<!-- gh-comment-id:4348152654 -->
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Could you do the following to help us troubleshoot?
```
sudo apt install sqlite3
sqlite3 config/db/db.sqlite
> select domain,domainId,wildcard,valid from certificates;
```
and let us know the output?
#With your query
sqlite> select domain,domainId,wildcard,valid from certificates;
Parse error: no such column: valid
select domain,domainId,wildcard,valid from certificates;
error here ---^
#Then without 'valid'
sqlite> select domain,domainId,wildcard from certificates;
obfuscated.de|domain1|0
<!-- gh-comment-id:4348163767 -->
@Schnookeuz commented on GitHub (Apr 29, 2026):
There u go:
```
#With your query
sqlite> select domain,domainId,wildcard,valid from certificates;
Parse error: no such column: valid
select domain,domainId,wildcard,valid from certificates;
error here ---^
#Then without 'valid'
sqlite> select domain,domainId,wildcard from certificates;
obfuscated.de|domain1|0
```
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Whoops sorry the column is status
Okay so it is not storing the domain as a wildcard in the database which is the problem. Would you mind sharing what your acme.json looks like? You can remove the base64 cert sections. I want to see how the domain is represented.
<!-- gh-comment-id:4348179083 -->
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Whoops sorry the column is `status`
Okay so it is not storing the domain as a wildcard in the database which is the problem. Would you mind sharing what your acme.json looks like? You can remove the base64 cert sections. I want to see how the domain is represented.
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Hum I wonder if the sans fix in this release did not work. Looking into it now
<!-- gh-comment-id:4348218617 -->
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Hum I wonder if the sans fix in this release did not work. Looking into it now
@AstralDestiny commented on GitHub (Apr 29, 2026):
Though think I recall Loz mentioning it doesn't look at the sans field.
<!-- gh-comment-id:4348218829 -->
@AstralDestiny commented on GitHub (Apr 29, 2026):
Though think I recall Loz mentioning it doesn't look at the sans field.
I created a new private ressource to check if they are also affected. Here the certificate stays on "Pending"
Logs:
pangolin | 2026-04-29T23:25:27+00:00 [warn]: No valid certificate found for SSL site resource 4 with domain speedtester.obfuscated.de
pangolin | 2026-04-29T23:25:27+00:00 [info]: Created site resource 4 for org zorg
pangolin | 2026-04-29T23:26:15+00:00 [info]: Checking Docker socket for site 3 with Newt b8nifb5ex1sx15p
pangolin | 2026-04-29T23:26:15+00:00 [info]: Checking Docker socket for site 2 with Newt f8sr7mehn6i06al
pangolin | 2026-04-29T23:26:15+00:00 [info]: Checking Docker socket for site 4 with Newt yjj3ns0ihszfyi4
pangolin | 2026-04-29T23:26:15+00:00 [info]: Checking Docker socket for site 6 with Newt uux5x7ogi0ux56l
pangolin | 2026-04-29T23:26:15+00:00 [info]: Triggering fetch containers for site 3 with Newt b8nifb5ex1sx15p
pangolin | 2026-04-29T23:26:15+00:00 [info]: Triggering fetch containers for site 2 with Newt f8sr7mehn6i06al
pangolin | 2026-04-29T23:26:48+00:00 [info]: Certificate already exists for domain speedpublic.obfuscated.de
Then i also created a new public ressource. In that moment ALL public ressources switched to the status "Pending"
Nothing to mention in the logs of pangolin or traefik for the public ressource.
<!-- gh-comment-id:4348257872 -->
@Schnookeuz commented on GitHub (Apr 29, 2026):
Oh, interesting.
I created a new private ressource to check if they are also affected. Here the certificate stays on "Pending"
<img width="1058" height="152" alt="Image" src="https://github.com/user-attachments/assets/e9e75b3b-c4f9-4a8d-8237-615305fb1edf" />
Logs:
```
pangolin | 2026-04-29T23:25:27+00:00 [warn]: No valid certificate found for SSL site resource 4 with domain speedtester.obfuscated.de
pangolin | 2026-04-29T23:25:27+00:00 [info]: Created site resource 4 for org zorg
pangolin | 2026-04-29T23:26:15+00:00 [info]: Checking Docker socket for site 3 with Newt b8nifb5ex1sx15p
pangolin | 2026-04-29T23:26:15+00:00 [info]: Checking Docker socket for site 2 with Newt f8sr7mehn6i06al
pangolin | 2026-04-29T23:26:15+00:00 [info]: Checking Docker socket for site 4 with Newt yjj3ns0ihszfyi4
pangolin | 2026-04-29T23:26:15+00:00 [info]: Checking Docker socket for site 6 with Newt uux5x7ogi0ux56l
pangolin | 2026-04-29T23:26:15+00:00 [info]: Triggering fetch containers for site 3 with Newt b8nifb5ex1sx15p
pangolin | 2026-04-29T23:26:15+00:00 [info]: Triggering fetch containers for site 2 with Newt f8sr7mehn6i06al
pangolin | 2026-04-29T23:26:48+00:00 [info]: Certificate already exists for domain speedpublic.obfuscated.de
```
Then i also created a new public ressource. In that moment ALL public ressources switched to the status "Pending"
<img width="1110" height="688" alt="Image" src="https://github.com/user-attachments/assets/e6470c90-36b5-4219-b53e-9972be9c6aed" />
Nothing to mention in the logs of pangolin or traefik for the public ressource.
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Okay I think I know whats happening here. In 1.18.0 we were not detecting the sans field in the acme.json. We are detecting it now in the 1.18.1 update. But because you had already inserted domains from the previous update and the cert has not changed it is not updating the database to reflect the now detected wildcard option. There was another issue with the 1.18.1 we are patching over it. I will let you know when you can pull and try again.
It is triggering pending because it thinks you dont already have a cert saved in the database that matches.
You can resolve this probably by running:
sqlite3 config/db/db.sqlite
> delete from certificates;
<!-- gh-comment-id:4348272408 -->
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Okay I think I know whats happening here. In 1.18.0 we were not detecting the sans field in the acme.json. We are detecting it now in the 1.18.1 update. But because you had already inserted domains from the previous update and the cert has not changed it is not updating the database to reflect the now detected wildcard option. There was another issue with the 1.18.1 we are patching over it. I will let you know when you can pull and try again.
It is triggering pending because it thinks you dont already have a cert saved in the database that matches.
You can resolve this probably by running:
```
sqlite3 config/db/db.sqlite
> delete from certificates;
```
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Okay great thanks for confirming and helping to pin down the issue! A patch for 1.18.1 is going out now so I will mark this as resolved.
<!-- gh-comment-id:4348302066 -->
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Okay great thanks for confirming and helping to pin down the issue! A patch for 1.18.1 is going out now so I will mark this as resolved.
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 @Schnookeuz on GitHub (Apr 29, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2935
Describe the Bug
I updated to v1.18.1 and the new certificate indicator for private ressources shows that the certificate is invalid.
Environment
To Reproduce
The logs are showing:
Additional info:
-I use DNS-01 challenge for a wildcard certificate.
-I only have one domain.
Expected Behavior
All certificates are fine.
@Schnookeuz commented on GitHub (Apr 29, 2026):
I also entered a shell inside the pangolin container and my acme.json is accessible:
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Looking into it
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Could you do the following to help us troubleshoot?
and let us know the output?
@Schnookeuz commented on GitHub (Apr 29, 2026):
There u go:
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Whoops sorry the column is
statusOkay so it is not storing the domain as a wildcard in the database which is the problem. Would you mind sharing what your acme.json looks like? You can remove the base64 cert sections. I want to see how the domain is represented.
@Schnookeuz commented on GitHub (Apr 29, 2026):
Sure...
and before you ask, here the section in the config.yml:
@AstralDestiny commented on GitHub (Apr 29, 2026):
Same here,
config/privateconfig.yml
config/config.yml
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Hum I wonder if the sans fix in this release did not work. Looking into it now
@AstralDestiny commented on GitHub (Apr 29, 2026):
Though think I recall Loz mentioning it doesn't look at the sans field.
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Thanks for your help @Schnookeuz and @AstralDestiny
@AstralDestiny commented on GitHub (Apr 29, 2026):
Or maybe is it because we're both using p384 over RSA4096?
@Schnookeuz commented on GitHub (Apr 29, 2026):
Oh, interesting.
I created a new private ressource to check if they are also affected. Here the certificate stays on "Pending"
Logs:
Then i also created a new public ressource. In that moment ALL public ressources switched to the status "Pending"
Nothing to mention in the logs of pangolin or traefik for the public ressource.
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Okay I think I know whats happening here. In 1.18.0 we were not detecting the sans field in the acme.json. We are detecting it now in the 1.18.1 update. But because you had already inserted domains from the previous update and the cert has not changed it is not updating the database to reflect the now detected wildcard option. There was another issue with the 1.18.1 we are patching over it. I will let you know when you can pull and try again.
It is triggering pending because it thinks you dont already have a cert saved in the database that matches.
You can resolve this probably by running:
@Schnookeuz commented on GitHub (Apr 29, 2026):
Yep, that fixed it!
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Okay great thanks for confirming and helping to pin down the issue! A patch for 1.18.1 is going out now so I will mark this as resolved.