Clarify Pangolin docs for wildcard certificates

- add illustrative config.yml snippet
- extend highlight to capture relevant traefik line
- clarify pangolin dashboard is inaccessible at step 3 in the process
This commit is contained in:
Matt Sartwell
2026-01-30 12:21:10 -08:00
committed by Owen Schwartz
parent 85dd215583
commit a3a25608dd

View File

@@ -61,7 +61,14 @@ The [rate limits](https://letsencrypt.org/docs/rate-limits/) for Let's Encrypt a
</Step> </Step>
<Step title="Configure Pangolin"> <Step title="Configure Pangolin">
Set the `prefer_wildcard_cert` flag to `true` in the Pangolin configuration file for your domain. Or update it on the Domains page in the Pangolin dashboard. Set the `prefer_wildcard_cert` flag to `true` in the Pangolin configuration file for your domain. This is also configurable in the Pangolin dashboard (once restarted).
```yaml title="config.yml" highlight={4}
domains:
domain1:
base_domain: "example.com"
prefer_wildcard_cert: true
```
</Step> </Step>
</Steps> </Steps>
@@ -130,7 +137,7 @@ This is the default config generated by the installer. This is shown here for re
<Step title="2. Add Wildcard Domains"> <Step title="2. Add Wildcard Domains">
Add the domain and wildcard domain to the domains section of the next (front end) router in the dynamic config. This tells Traefik to generate a wildcard certificate for the base domain and all subdomains. Add the domain and wildcard domain to the domains section of the next (front end) router in the dynamic config. This tells Traefik to generate a wildcard certificate for the base domain and all subdomains.
```yaml title="dynamic_config.yml" highlight={9-12} ```yaml title="dynamic_config.yml" highlight={8-12}
next-router: next-router:
rule: "Host(`pangolin.example.com`) && !PathPrefix(`/api/v1`)" rule: "Host(`pangolin.example.com`) && !PathPrefix(`/api/v1`)"
service: next-service service: next-service