4.9.13 user cannot log in after upgrade to 5.4.17

[charleslcso]

Loops back to Welcome back. Password is sure correct. Email address is sure correct.

What to check?

[dosubot[bot]]

A login loop after upgrading often points to issues with authentication, session handling, or database state. Here are the most important things to check:

• Make sure you ran the correct database migration command for your environment: for production, use yarn workspace @calcom/prisma db-deploy; for development, use yarn workspace @calcom/prisma db-migrate—using the wrong one can break authentication after an upgrade [source].
• Review your environment variables and authentication/session configuration. There have been significant changes and refactoring in authentication logic (including a move to a repository pattern and updates to the authentication adapter) between these versions, so old configs may not work [source] [source].
• Check server logs for errors during login attempts—these can reveal missing migrations, misconfigurations, or adapter issues.
• Inspect browser cookies and session storage for anomalies. The authentication handler now uses NextAuth and expects certain cookies (like dub_id or dclid) to be present [source].
• If you have any custom authentication adapters or middleware, make sure they are compatible with the new version.

Manual testing is especially important after this upgrade, as recent authentication changes are high risk and automated tests may not catch all edge cases [source].

If you can share any error messages from your logs, I can help dig deeper.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[charleslcso]

@dosubot Error message that MIGHT be helpful:

@calcom/web:start: 16:31:31:158 [WARN] orgDomains.ts Derived slug ended up having dots, so not considering it an org domain {
@calcom/web:start:   slug: '192.168.1.127:3000'
@calcom/web:start: }

I am not using Vercel. Just self hosting.

nodejs 22
yarn 4.3.1

[dosubot[bot]]

That warning is the root cause of your login loop. Cal.com’s recent versions require a valid organization context, which is determined by parsing the hostname into a slug. If you access the app via an IP address (like 192.168.1.127:3000), the derived slug contains dots, so Cal.com refuses to treat it as an org domain—this disables org context and breaks authentication, resulting in the login loop you’re seeing (source).

To fix this, either use a real domain or subdomain (even locally, you can add a line to your hosts file and use something like cal.localhost), or set the SINGLE_ORG_SLUG environment variable for single-tenant/local setups. This will bypass the org domain check and restore login functionality.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[charleslcso]

That warning is the root cause of your login loop. Cal.com’s recent versions require a valid organization context, which is determined by parsing the hostname into a slug. If you access the app via an IP address (like 192.168.1.127:3000), the derived slug contains dots, so Cal.com refuses to treat it as an org domain—this disables org context and breaks authentication, resulting in the login loop you’re seeing (source).

To fix this, either use a real domain or subdomain (even locally, you can add a line to your hosts file and use something like cal.localhost), or set the SINGLE_ORG_SLUG environment variable for single-tenant/local setups. This will bypass the org domain check and restore login functionality.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

In .env, which variable to set to use a real domain or subdomain?

Also, what to set in SINGLE_ORG_SLUG?