Originally created by @hermetic-charm on GitHub (Sep 27, 2025).
I recently setup a catchall router in traefik which detects any errors (e.g. 404) and redirects to a custom error page.
I noticed whenever my Komodo session timed out and I logged back in, if the original page had any path (e.g. komodo.example.com/stacks/blahblahblah) other than just domain (e.g. komodo.example.com) I would get a 404. Refreshing would produce the same. But removing the path in the URL back to just the domain (e.g. komod.example.com) would reload home page correctly, then I could manually navigate back to the path through UI clicks.
I opened dev tools in browser and was in fact seeing 404s whenever this happened. So, I disabled my new error catching router in traefik and checked again. Indeed, after a logout a 404 occurs after logging back in but without the traefik router the page correctly loads after that 404. Additionally, I noticed that I get a 404 every time I try to refresh a page with any path (even when logged in), but the page correctly loads after the 404.
Is this expected behavior?
Originally created by @hermetic-charm on GitHub (Sep 27, 2025).
I recently setup a catchall router in traefik which detects any errors (e.g. 404) and redirects to a custom error page.
I noticed whenever my Komodo session timed out and I logged back in, if the original page had any path (e.g. komodo.example.com/stacks/blahblahblah) other than just domain (e.g. komodo.example.com) I would get a 404. Refreshing would produce the same. But removing the path in the URL back to just the domain (e.g. komod.example.com) would reload home page correctly, then I could manually navigate back to the path through UI clicks.
I opened dev tools in browser and was in fact seeing 404s whenever this happened. So, I disabled my new error catching router in traefik and checked again. Indeed, after a logout a 404 occurs after logging back in but without the traefik router the page correctly loads after that 404. Additionally, I noticed that I get a 404 every time I try to refresh a page with any path (even when logged in), but the page correctly loads after the 404.
Is this expected behavior?
Additionally, I noticed that I get a 404 every time I try to refresh a page with any path (even when logged in), but the page correctly loads after the 404.
Same issue here (404 for every path expect of root) with Komodo running behind Pangolin (SSO disabled), which is also Traefik based.
Not sure if this is Traefik related or also happens with Caddy and NGINX proxies in front of Komodo.
@elcajon commented on GitHub (Oct 23, 2025):
> Additionally, I noticed that I get a 404 every time I try to refresh a page with any path (even when logged in), but the page correctly loads after the 404.
Same issue here (404 for every path expect of root) with Komodo running behind [Pangolin](https://github.com/fosrl/pangolin) (SSO disabled), which is also Traefik based.
Not sure if this is Traefik related or also happens with Caddy and NGINX proxies in front of Komodo.
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 @hermetic-charm on GitHub (Sep 27, 2025).
I recently setup a catchall router in traefik which detects any errors (e.g. 404) and redirects to a custom error page.
I noticed whenever my Komodo session timed out and I logged back in, if the original page had any path (e.g. komodo.example.com/stacks/blahblahblah) other than just domain (e.g. komodo.example.com) I would get a 404. Refreshing would produce the same. But removing the path in the URL back to just the domain (e.g. komod.example.com) would reload home page correctly, then I could manually navigate back to the path through UI clicks.
I opened dev tools in browser and was in fact seeing 404s whenever this happened. So, I disabled my new error catching router in traefik and checked again. Indeed, after a logout a 404 occurs after logging back in but without the traefik router the page correctly loads after that 404. Additionally, I noticed that I get a 404 every time I try to refresh a page with any path (even when logged in), but the page correctly loads after the 404.
Is this expected behavior?
@elcajon commented on GitHub (Oct 23, 2025):
Same issue here (404 for every path expect of root) with Komodo running behind Pangolin (SSO disabled), which is also Traefik based.
Not sure if this is Traefik related or also happens with Caddy and NGINX proxies in front of Komodo.