Sign-in and access
Fix sign-in, passkey, token, team access, and permission problems.
You cannot sign in
| Symptom | Cause |
|---|---|
| Password rejected | Check the password and whether the account is suspended |
| Password forgotten | An instance admin resets it in Settings -> Users; the only admin resets it from the host |
| No identifier accepted | The field accepts an email or username; check which one exists |
| Six-digit code rejected | Correct the phone's clock; TOTP is time-based |
| Code and recovery code rejected | Recovery codes are single-use; an instance admin must reset two-factor |
| Passkey says Not usable here | The panel hostname changed; see Passkeys stopped working |
| Page will not load | Try https://deplo-cb00710a.deplo.site; if disabled, see the panel's own address |
Passkeys stopped working
Passkeys are bound to the hostname where they were registered. Moving the panel invalidates them on the new address.
The way back in
Sign in with the password and register a new passkey on the new address. Everybody on the instance must do this once.
A team is locked until you enroll two-factor
That team requires two-factor authentication and your account has not enrolled. Until you enroll, you cannot access that team in the dashboard or API.
The screen offers to turn it on, switch to another team, or sign out.
A button is missing or greyed out
Check these in order:
- Capability: your role may not include it.
- Folder share: a folder share replaces your team role inside that folder.
- Advanced grant: publishing a port needs Publish ports; anything that reaches the host needs Bind server folders. Find them under Settings -> Users -> the user -> Permissions -> Advanced grants.
- Instance admin: Servers, Users, and Deplo settings are not team capabilities.
- Feature switch: Console needs acknowledgement; cron jobs and previews need their switch enabled.
An API token returns 401
The token is missing, revoked, or expired. Create or rotate it in Settings -> Tokens.
An API token returns 403
| Cause | Fix |
|---|---|
| The token lacks that capability | Edit it in Settings -> Tokens |
| Its creator lost that capability | A token can never do more than its creator can do right now |
| The scope excludes the resource | Naming a project or an app drops every team-wide capability in that team |
| The team requires two-factor and its creator has not enrolled | The token resolves nothing |
An API resource returns 404
It belongs to another team, or it is outside the token's scope. Deplo resolves out-of-scope resources to nothing rather than revealing that they exist.
A deleted app behaves the same way from the moment deletion starts.
You are the owner and locked out
The instance owner cannot be reset by another admin. If that account is lost,
run deplo recover owner <username> on the control-plane host. See
Break-glass recovery.
Somebody left the company
- In Settings -> Members, open them, choose Advanced, and remove them.
- Their tokens immediately lose access from their membership.
- Transfer primary ownership first if they are the owner.
- Check Activity for recent actions.
Next steps
Did this page help you?