Skip to main content

Fixing sign-in issues

Corte requires a signed-in session — when you open app.corte.so, a brief boot splash shows while your session resolves, then either your workspace or the sign-in screen appears. If you're stuck somewhere in that flow, one of the fixes below almost always clears it.

The app is stuck on the boot splash​

The splash only stays up while the app is waiting to hear back from the Corte server. If it never resolves:

  1. Check your connection to the server, not just the internet. In another tab, open https://api.corte.so/v1/health. If that doesn't load, the problem is between your network and Corte — try another network, and see the corporate-network notes below.
  2. Reset your Backend URL. If you've ever changed the server address in Settings → General → Backend, the app keeps using it. A stale or local-development URL (for example http://localhost:8787) leaves the app waiting on a server that isn't there. Set it back to https://api.corte.so and click Save — the status dot next to the field turns green when the server is reachable.
  3. Hard-refresh the tab (⇧⌘R on Mac, Ctrl + Shift + R elsewhere) to rule out a stale cached build.

:::tip Can't reach Settings because you can't sign in? The Backend URL is saved per-browser. Opening the app in a private/incognito window gives you a fresh default configuration — if it works there, resetting the Backend URL in your normal window is the fix. :::

You keep getting signed out, or your session "expired"​

Corte keeps you signed in with a session cookie. Anything that eats cookies ends your session:

  • Blocked or auto-cleared cookies. Allow cookies for app.corte.so and api.corte.so, and exclude them from any "clear cookies on close" rule.
  • Strict tracking-prevention or privacy extensions sometimes strip the session cookie from requests to the API. Try disabling extensions for app.corte.so, or test in a private window with extensions off.
  • Signing in on another device or browser doesn't sign you out elsewhere — if you're being signed out repeatedly on one machine, the cause is local to that browser.

After fixing the cookie situation, sign in again from the sign-in screen (or Settings → Account).

Wrong password or "account not found"​

  • Double-check the email — sign-ins are per-email, and a typo creates a different identity than the one holding your credits.
  • If you originally signed up from the marketing site, use that same email here; the account is the same. See Creating your account.

Corporate networks, VPNs, and firewalls​

Some corporate proxies block WebSocket connections or unfamiliar domains. Ask your IT team to allow:

  • app.corte.so (the editor)
  • api.corte.so (accounts, generation, transcription)
  • media.corte.so (media delivery)

A quick test: if the app works on your phone's hotspot but not the office network, it's a network policy, not your account.

Still locked out?​

Contact us with the email on the account and what you see (splash, sign-in wall, or an error). Account access questions are answered on every plan — see Getting support for what to include.