Troubleshooting

Signing in on the website

What you see	What it means	What to do
That email is already registered through a different sign-in method (`OAuthAccountNotLinked`)	You signed up with one provider and are now using another with the same email.	Sign in with the provider you used the first time.
Sign-in was refused (`AccessDenied`)	The account is suspended, or Google reports the email as unverified.	Verify your email with Google, or contact support if you think your account was suspended by mistake.
Sign-in isn't configured correctly (`Configuration`)	The site's sign-in provider settings are incomplete (relevant if you're running your own copy).	Check the Google and Discord credentials in the environment — see the project README.
A provider button says (not set up)	That provider isn't configured on this server.	Use the other provider, or configure it.

Problem	Try this
Sign-in page says the link isn't valid	Start again from the app — see Connect the desktop app.
App says my plan is Free after upgrading	Close and reopen the app, or sign out and in again. The app reads your plan from your account on start-up.
An overlay shows a lock	Its plan requirement isn't met on your current plan. The lock tells you which plan unlocks it.
"Inventory is full"	You reached your plan's inventory limit. Remove items you don't use, or upgrade.
Can't create an overlay	Creating your own overlays needs Pro or Ultimate.

Status / code	Meaning	Fix
`401 invalid_token`	The key is wrong, revoked or expired.	Check you copied the whole key; create a new one on your account page.
`403 insufficient_scope`	The key doesn't have the scope this endpoint needs.	Create a key with the right scope — scopes can't be edited after creation.
`403 plan_required`	Your plan doesn't include this action (for example creating an overlay on Free).	Upgrade, or use a different action.
`403 limit_reached`	You hit a plan limit (custom overlays, inventory size or active keys).	Delete something or upgrade.
`409 conflict`	The overlay was changed elsewhere since you read it.	Fetch it again, apply your change, resend with the new `baseRev`.
`429 rate_limited`	More than 10 requests in a minute on your account.	Wait for `Retry-After` seconds; see Rate limits.