The dashboard can be accessed at pangolin.example.com.
If you configure the same subdomain as a resource, you will be redirected in a loop (HTTP 302).
I configured it this way on purpose to test whether anything would break, and it did. :)
I don't think that's a common issue.
I fixed it by changing the dashboard's subdomain in the configuration; you can then remove the resource.
Environment
OS Type & Version: Debian 13
Pangolin Version: 1.16.2
Gerbil Version: 1.3.0
Traefik Version: 3.6
To Reproduce
Setup Pangolin on pangolin.example.com
Add local site
Create public resource
HTTPS Settings
Subdomain pangolin
Base Domain example.com
Targets Configuration
Local site
Protocol https
Host localhost
Port 443
Expected Behavior
There should be a warning or error message.
Originally created by @Root-Core on GitHub (Mar 4, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2595
### Describe the Bug
The dashboard can be accessed at `pangolin.example.com`.
If you configure the same subdomain as a resource, you will be redirected in a loop (HTTP 302).
I configured it this way on purpose to test whether anything would break, and it did. :)
I don't think that's a common issue.
I fixed it by changing the dashboard's subdomain in the configuration; you can then remove the resource.
### Environment
- OS Type & Version: Debian 13
- Pangolin Version: 1.16.2
- Gerbil Version: 1.3.0
- Traefik Version: 3.6
### To Reproduce
1. Setup Pangolin on `pangolin.example.com`
2. Add local site
3. Create public resource
- HTTPS Settings
- Subdomain `pangolin`
- Base Domain `example.com`
- Targets Configuration
- Local site
- Protocol `https`
- Host `localhost`
- Port `443`
### Expected Behavior
There should be a warning or error message.
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 @Root-Core on GitHub (Mar 4, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2595
Describe the Bug
The dashboard can be accessed at
pangolin.example.com.If you configure the same subdomain as a resource, you will be redirected in a loop (HTTP 302).
I configured it this way on purpose to test whether anything would break, and it did. :)
I don't think that's a common issue.
I fixed it by changing the dashboard's subdomain in the configuration; you can then remove the resource.
Environment
To Reproduce
pangolin.example.compangolinexample.comhttpslocalhost443Expected Behavior
There should be a warning or error message.