Login redirects to infinite loading — redirect: false response, no navigation after auth

[Rama054]

To Reproduce

Steps to reproduce

1. Navigate to Dokploy login page
2. Enter valid credentials and submit
3. POST /api/auth/sign-in/email returns 200 OK
4. UI stays on login page, infinite loading spinner
5. Manually reload → logged in successfully

Current vs. Expected behavior

Problem

After submitting the login form, the UI gets stuck on infinite loading. No redirect occurs. If I manually reload the page (F5), I'm already logged in — the session was created correctly.

This happens 100% of the time, on every login attempt.

Also reproducible accessing directly via ip:3000, so it's not a Cloudflare/proxy issue.

Expected behavior

After successful authentication, the frontend should navigate to /dashboard (or equivalent).

Provide environment information

### Environment

- `BETTER_AUTH_URL` is set correctly to the HTTPS domain
- `BETTER_AUTH_SECRET_FILE` uses Docker Secrets (value confirmed present and valid)
- Sessions are created correctly in the DB (`expires_at` is in the future)
- No errors in `docker service logs dokploy` related to auth or postgres at login time
- NTP synchronized: yes

**Dokploy version:** v0.29.5
**OS:** Ubuntu
**Access method:** Custom domain with HTTPS (Cloudflare DNS + Traefik + Let's Encrypt)
**Deployment type:** Single server, Docker Swarm

Which area(s) are affected? (Select all that apply)

Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

Network tab (DevTools)

Only one request is made after clicking login:

POST /api/auth/sign-in/email
Status: 200 OK

Response body:

{
  "redirect": false,
  "token": "...",
  "user": { ... }
}

No subsequent requests are made. The frontend receives redirect: false and does not navigate anywhere.

Additional notes

This appears related to PR #4335 ("fix: use temporary redirects for auth checks in getServerSideProps") introduced in v0.29.3, but the issue persists in v0.29.5.

The better-auth client returns redirect: false by default when called from the browser without an explicit redirectTo parameter. The frontend needs to handle this case and perform a manual router.push() after receiving a successful auth response.

Will you send a PR to fix it?

No

[dosubot]

Hi @Rama054! I'm Dosu and I’m helping the dokploy team.

This is a duplicate of #4220, which reports the exact same symptoms: login succeeds (session created), but no redirect to the dashboard occurs until a manual page refresh.

The root cause is stale tRPC/React Query cache persisting across login/logout cycles [1]. The logout handler in UserNav calls authClient.signOut() and router.push("/") without invalidating the client-side cache [2]. On the next login, even though router.push("/dashboard/home") is called after successful auth [3], the stale cached data prevents the dashboard from rendering properly.

PR #4335 addressed a different aspect — changing auth redirects in getServerSideProps from HTTP 301 (permanent, browser-cached) to 302 (temporary) [4]. That fix prevents the browser from caching server-side redirects, but doesn't resolve the client-side tRPC cache staleness issue you're seeing.

Workaround: Adding await utils.invalidate() (from api.useUtils()) before the router.push("/") in the logout handler (apps/dokploy/components/layouts/user-nav.tsx) should resolve it on subsequent logins [1]. This pattern is already used elsewhere in the codebase [5].

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[mtalhazulf]

i have done alot of testing on this part. re-installed the dokploy 0.29.5 in a fresh state. this didnt happened.

[mtalhazulf]

Please Clear your cache or Check in incognito

[watercubz]

@Rama054 It may be due to an error in your cache; try deleting it, as well as everything in localstorage and cookies, and then try starting again.

[ivankprod]

@Rama054 It may be due to an error in your cache; try deleting it, as well as everything in localstorage and cookies, and then try starting again.

This didn't help. Sign in request stacking on waiting.

[watercubz]

@Rama054 It may be due to an error in your cache; try deleting it, as well as everything in localstorage and cookies, and then try starting again.

This didn't help. Sign in request stacking on waiting.

Did you try using a newer version?

[ivankprod]

@watercubz yes, updated to latest, but didn't help too. Reloaded machine too. Can't access dokploy control panel anymore :(