Whole team locked out of baserow.io – login fails with "unknown error", status page shows all green

Technical Help
1

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

SaaS

What are the exact steps to reproduce this issue?

We are on baserow.io (SaaS, Premium plan). Since this morning (17 July 2026), nobody on our team can log in.

Steps to reproduce:

  1. Open baserow.io → the error page “User session expired” appears, saying an error occurred while loading the page.
  2. Click “Back to login”, enter credentials, submit → “Action not completed. The action could not be completed because an unknown error occurred.”

On mobile the behaviour is different: after submitting, the login form simply reloads empty. No error message at all.

At no point do we get an “invalid credentials” response, so this doesn’t look like a password problem.

No recent changes were made to our configuration.

What we have already tried:

  • Multiple user accounts – every single account in our organisation is affected, not just one
  • Multiple machines
  • Chrome and Safari
  • Cleared cookies, localStorage and sessionStorage for baserow.io
  • Private/incognito windows
  • Hard reload
  • Mobile devices over cellular (LTE) – different network, d

Attach screenshots, videos, or logs that demonstrate the issue.

tempImagedwUFkY.jpg
tempImagedwUFkY.jpg3024×4032 988 KB
tempImageEm4uzJ.jpg
tempImageEm4uzJ.jpg3024×4032 2.53 MB

2

Hey @glueckundglanz, the team is looking into the issue right now. :folded_hands:

3

A short update: Login problems for some acc... | Baserow @glueckundglanz

4

Thanks @olgatrykush – and thanks to Bram, who replied to our support email very quickly.

For anyone landing here with the same symptoms, a short summary of what it actually is:

It’s location-based. Bram confirmed it works for him in the Netherlands, but reproduces via a VPN in Poland. We’re in Cologne, Germany – also affected.

The error message is misleading. The frontend shows “User session expired” and then “unknown error”, but the real API response from token-auth is:

{“password”:[“This field is required.”]}

The password field gets dropped somewhere on the way. It reproduces with plain curl, no browser involved – so clearing cookies, switching browsers or resetting your password won’t help. We spent a few hours on exactly that before we found it.

Workaround that works for us right now: connect through a VPN with an exit node in the Netherlands. Login works normally again immediately.

Following the official thread for the fix.

5

Hey @glueckundglanz, the issue was fixed :raising_hands: