Setting up a new resource works with no issues. Trying to set up a prefix-type rewrite rule results in resource-router to stop functioning properly and returns 404 each time.
Environment
OS Type & Version: Debian 12
Pangolin Version: 1.12.1
Gerbil Version: 1.2.2
Traefik Version: 3.5
Newt Version: 1.6
Olm Version: (if applicable)
To Reproduce
According Authentik requirements with OwnCloud, a rewrite is needed: https://owncloud.company/.well-known/openid-configuration to https://owncloud.company/index.php/apps/openidconnect/config. Setting up prefix /.well-known/openid-configuration to be rewritten to /index.php/apps/openidconnect/config. Removing those rules and saving doesn't solve the issue. Resource needs to be deleted and set up again for it to work.
Expected Behavior
Rewrite to work and not influence router.
Originally created by @Lalilalulalam on GitHub (Nov 10, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1842
### Describe the Bug
Setting up a new resource works with no issues. Trying to set up a prefix-type rewrite rule results in resource-router to stop functioning properly and returns 404 each time.
### Environment
- OS Type & Version: Debian 12
- Pangolin Version: 1.12.1
- Gerbil Version: 1.2.2
- Traefik Version: 3.5
- Newt Version: 1.6
- Olm Version: (if applicable)
### To Reproduce
According Authentik requirements with OwnCloud, a rewrite is needed:
`https://owncloud.company/.well-known/openid-configuration` to `https://owncloud.company/index.php/apps/openidconnect/config`. Setting up prefix `/.well-known/openid-configuration` to be rewritten to `/index.php/apps/openidconnect/config`. Removing those rules and saving doesn't solve the issue. Resource needs to be deleted and set up again for it to work.
### Expected Behavior
Rewrite to work and not influence router.
@oschwartz10612 commented on GitHub (Nov 22, 2025):
Hi sorry for the delay. Are you able to reproduce this and turn on debug
logs and tail the logs from pangolin and let me know if you see
anything? I suspect there may be something in the config it does not
like for the rewrite.
Edit config/config.yml:
app:
log_level: debug
docker compose logs -f pangolin
<!-- gh-comment-id:3567088758 -->
@oschwartz10612 commented on GitHub (Nov 22, 2025):
Hi sorry for the delay. Are you able to reproduce this and turn on debug
logs and tail the logs from pangolin and let me know if you see
anything? I suspect there may be something in the config it does not
like for the rewrite.
Edit config/config.yml:
app:
log_level: debug
docker compose logs -f pangolin
@Lalilalulalam commented on GitHub (Nov 23, 2025):
Hi, thanks for the reply.
I have made changes to config.yml and created test resource (owncloud.my.domain). First I have accessed it without rewrite rule with success, then added rewrite rule and got 404. Log anonymized a bit.
@github-actions[bot] commented on GitHub (Dec 9, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
<!-- gh-comment-id:3629635628 -->
@github-actions[bot] commented on GitHub (Dec 9, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Dec 23, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
<!-- gh-comment-id:3684634770 -->
@github-actions[bot] commented on GitHub (Dec 23, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
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 @Lalilalulalam on GitHub (Nov 10, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1842
Describe the Bug
Setting up a new resource works with no issues. Trying to set up a prefix-type rewrite rule results in resource-router to stop functioning properly and returns 404 each time.
Environment
To Reproduce
According Authentik requirements with OwnCloud, a rewrite is needed:
https://owncloud.company/.well-known/openid-configurationtohttps://owncloud.company/index.php/apps/openidconnect/config. Setting up prefix/.well-known/openid-configurationto be rewritten to/index.php/apps/openidconnect/config. Removing those rules and saving doesn't solve the issue. Resource needs to be deleted and set up again for it to work.Expected Behavior
Rewrite to work and not influence router.
@oschwartz10612 commented on GitHub (Nov 22, 2025):
Hi sorry for the delay. Are you able to reproduce this and turn on debug
logs and tail the logs from pangolin and let me know if you see
anything? I suspect there may be something in the config it does not
like for the rewrite.
Edit config/config.yml:
app:
log_level: debug
docker compose logs -f pangolin
@Lalilalulalam commented on GitHub (Nov 23, 2025):
Hi, thanks for the reply.
I have made changes to config.yml and created test resource (owncloud.my.domain). First I have accessed it without rewrite rule with success, then added rewrite rule and got 404. Log anonymized a bit.
@Lalilalulalam commented on GitHub (Nov 24, 2025):
I forgot to mention, Traefik logging is set to append logfile. Content:
Before rewrite rule access.log
After rewrite rule:
@github-actions[bot] commented on GitHub (Dec 9, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Dec 23, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.