pgAdmin account locked: identify which login failed
Where does the login fail? If you can’t get into pgAdmin, check the application account. If pgAdmin opens but the database won’t connect, check the PostgreSQL login. Those are separate accounts, so start with the one that actually failed.
Find the login that failed
If the error appears before you reach the pgAdmin workspace, investigate the application login. If you can open pgAdmin but a saved server connection fails, investigate that PostgreSQL role or its authentication configuration. A cloud provider’s control-panel login is a third identity.
Save the exact error, time and pgAdmin version before trying more passwords. A browser password manager may be supplying an old application password even when the database password is correct.
Recover a pgAdmin application account
For a pgAdmin server deployment using its internal users, an authorized administrator can manage accounts through User Management. The official documentation describes the Locked control for unlocking a locked account. Follow the recovery procedure for your deployment and verify the user’s identity first.
If the deployment uses an external identity provider, involve the administrator responsible for that provider. An application-side change may not resolve a disabled identity or an organization access policy. Do not delete the configuration database or disable authentication as a shortcut.
If the database login failed
Confirm the saved host, username and database, then ask the database owner to check the role’s status and authentication method. For a Supabase password error, use the endpoint and credential checklist. For network failures, start with the connection diagnostic guide.
After access is restored
Update stale saved credentials through approved channels and test only the intended connection. Review unexpected lockouts with the administrator. A desktop PostgreSQL client such as plainDB uses database credentials; it does not unlock pgAdmin accounts or bypass PostgreSQL authentication. The useful next step is a verified connection, not another sequence of password guesses.