Infinite Login Redirect Loop

[lucidfoxes]

Description

I'm using Pangolin as a reverse proxy, and have been facing a login redirect loop after a recent update to Solidtime. The Solidtime app itself is definitely working, as when I don't use a reverse proxy and instead access it as 'private' resource in Pangolin everything works fine.

From a bit of debuging with the help of AI, I think this might be the cause and potential solution -

Symptoms:
Login POST returns 409 Conflict
Response includes X-Inertia-Location: /dashboard (login succeeded but Inertia intercepts)
Client sends X-Inertia-Version: header
Infinite redirect loop back to login

Health-check confirms:
is_trusted_proxy: true
secure: true
app_force_https: true
All proxy headers correct (x-forwarded-proto: https, etc.)

Required fix:
HandleInertiaRequests.php middleware needs to respect INERTIA_VERSION=null or allow disabling automatic Vite-based versioning. Currently returns version hash from public/build/manifest.json regardless of environment setting.

Reference: Inertia.js docs state "return a fixed value from the version method... to disable automatic asset versioning" — but solidtime doesn't check INERTIA_VERSION env.
has anyone else faced login redirect loops using pangolin/traefik as the reverse proxy? i'm not sure if the above fix is what's needed, but it seems possible as nothing else has worked for me.

Steps To Reproduce

...

Self-hosted or Cloud?

None

Version of solidtime: (for self-hosted)

No response

solidtime self-hosting guide: (for self-hosted)

No response

[Onatcer]

Can you check whats in your server logs and also what the status code of the response in the browser (network tab) actually is?

My understanding is that if it is actually a 409 it should resolve after a full (no cache) page reload / should not happen in a different browser.

Also what version / docker tag are you running?

[lucidfoxes]

I'm using the 'main' docker tag and the currently running version is Version v0.12.0 (Build 8cbc983).

The status code in the browser is "409 Conflict".

Here are the network logs for the error for a user login attempt. The response is the same for when 2fa is enabled or not. I've attempted to login in multiple browsers, clear cached, used incognito mode etc.

solidtime-409-error.txt

There are no errors in the container logs, even though I've enabled debugging.

solidtime-logs.txt

[Onatcer]

thanks for the info. I honestly don't really know what could have caused that regression, we did (kind of recently) update to Intertia v2 so it could be related to that. I might have to set up a Pangolin environment to check if i can reproduce it at some point and also to check if the fix you suggested would actually work.

Just to confirm this happens not only if you try to access the /admin route initially but also when you just log in regularly or try to access /dashboard, right? Because those use different technologies (Livewire for admin and inertia in the app itself).

If anyone else is facing this issue feel free to add info to this thread.

[lucidfoxes]

Pangolin uses Traefik under the hood, so I'd imagine the issue would affect more users. The issue happens when trying to acces both the /dashboard and /admin. Trying to access /admin just redirects me to /login.

My workaround for the moment is to use Solidtime as a private resource on Pangolin, which bypasses the reverse proxy altogether and the authetication flow and app work fine like this.

[Onatcer]

fwiw: we have some traefik instances running with the latest images as well, and they do not show that behaviour.