#Console is dead, unable to use

8 messages · Page 1 of 1 (latest)

strong hearthBOT
#

Hi @wispy jolt. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

The error message you are seeing—ErrorStatus(401, "{\"error\":\"Unauthorized: User not in context: ERROR: column \\\"is_eligible_for_reverse_team_trial\\\" does not exist (SQLSTATE 42703)\"}")—indicates an authentication or authorization problem, specifically a 401 Unauthorized error. This is often related to issues with your user session or account context in Warp.

From the knowledge sources, similar 401 Unauthorized errors have been reported when Warp is unable to fetch user settings or team metadata, often after a system event like suspend/resume or due to expired or invalid authentication tokens. For example, logs show repeated failures to fetch user settings and team data with 401 errors, which can leave the console in a non-functional state. These issues can be triggered by:

  • Expired or invalid authentication tokens.
  • Problems with the Warp backend or database schema changes (such as missing columns).
  • Network or connectivity issues, including VPNs, firewalls, or proxies interfering with authentication requests.
  • Account or session corruption after system suspend/resume or other disruptions.

What you can try:

#
  1. Restart Warp and Re-login: Fully close Warp and restart it. If possible, log out and log back in to refresh your authentication token.
  2. Check Network/Proxy/VPN: Ensure that your network allows access to required domains (e.g., app.warp.dev, www.googleapis.com). Disable VPNs or proxies temporarily to see if they are interfering.
  3. Check for Updates: Make sure you are running the latest version of Warp, as backend or schema changes may require a client update.
  4. Clear or Reset Session: If the problem persists, try clearing Warp's local data or cache, or reinstalling the application.
  5. Contact Support: If none of the above resolves the issue, this may be a backend/database issue on Warp's side (e.g., a missing database column). In this case, you should contact Warp support with your logs for further assistance.

Relevant logs and similar issues can be found in the following sources:

If you continue to experience this error, providing logs to Warp support will help them diagnose and resolve the backend issue.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@wispy jolt Kapa.ai is still learning and improving, please let me know how I did by reacting below.

wispy jolt
#

I have treid all of this, how can I contact support?

red zealot
#

If you can, try to physically log out of Warp and Login again to see if that corrects the issue. If it doesn’t we can try to look into the account to see if there’s any other issues but we’d need your account email address to do that (don’t post it publicly, you can send it to me in a Private message and I can forward it to the employee that can check for you)

cloud plover
#

Me too, it’s a wider system issue.

red zealot
#

There currently aren’t any known issues I’m aware of right now, but I’m away from the computer most of today (celebrating my birthday)… I can send a message through to see if I get a response but not sure who’s available. I know some people are currently unavailable for a bit so I’m unsure when I’ll get a response.