Odd behavior: 404 on refresh or session timeout #606

New Issue

GiteaMirror · 2025-10-31T15:16:17-05:00

GiteaMirror commented

2025-10-31 15:16:17 -05:00

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?

GiteaMirror commented

2025-10-31 15:16:18 -05:00

@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 (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.

GiteaMirror referenced this issue

2026-04-11 10:14:14 -05:00

[GH-ISSUE #606] failed to install default rustls CryptoProvider: CryptoProvider #2307

GiteaMirror referenced this issue

2026-04-13 15:00:55 -05:00

[GH-ISSUE #606] failed to install default rustls CryptoProvider: CryptoProvider #3452

GiteaMirror referenced this issue

2026-04-22 00:13:13 -05:00

[GH-ISSUE #606] failed to install default rustls CryptoProvider: CryptoProvider #5026

GiteaMirror referenced this issue

2026-04-24 19:18:40 -05:00

[GH-ISSUE #606] failed to install default rustls CryptoProvider: CryptoProvider #6197