When Proton Pass cannot complete a sign-in, it shows a message that most users skim and dismiss without reading. That is a pity: the text of the message points to the layer that failed — your input, the account, the second factor, the browser or the network. Understanding this logic turns chaotic attempts into calm diagnostics.
The first rule: do not repeat the sign-in dozens of times in a row. Some protections react to repeated failures by temporarily locking the account, and the messages may change from attempt to attempt, confusing you further. Note the exact text of the error, take a short pause and compare it with the sections below — each type of message has its own checklist.
How to classify Proton Pass sign-in errors
All Proton Pass login failures fall into four broad groups. Input errors appear instantly after you press the sign-in button — the email address or password is mistyped. Authentication errors appear after a short pause — the app reached the server, but the credentials were rejected. Second-factor problems happen after a correct password, when the one-time code is missing or wrong. Session and browser errors occur when the sign-in technically succeeds but the vault cannot stay unlocked or load.
Identifying the group immediately eliminates half of the unnecessary checks. For example, with a two-factor problem there is no point retyping the password, and with an instant input error there is no point blaming the network.
"Incorrect password" and other input errors
The simplest cause is also the most frequent: Caps Lock, a keyboard layout that is not what you expect, autocorrect on a phone or a space that snuck in while copying. Type the password manually into a text field and compare it character by character with what you saved. Watch out for lookalike characters — the digit zero and the letter O, the digit one and a lowercase L.
If you changed your Proton Account password recently, use the new one. Old credentials saved in a browser's built-in password store will no longer work, and browsers are surprisingly stubborn about offering outdated values.
A forgotten master password
A master password cannot be reset in the usual sense — that is the price of end-to-end encryption, and it is a feature rather than a bug. What you can do is use the account recovery options you set up in advance, such as a recovery phrase or a recovery email. If none of them exist, the encrypted vault content cannot be decrypted by anyone, including Proton.
This sounds harsh, but it is exactly why every password manager recommends an emergency kit: recovery codes printed on paper, stored somewhere safe. If you have not created one yet, do it today — while everything works and the task feels boring.
Two-factor codes and two-password mode
If the app asks for a code after accepting your password, the account is protected by two-factor authentication. Common failures here: the authenticator app is on another device that is not at hand, the code is entered just as it expires, or the device's clock has drifted and generates codes that the server rejects. Check the time settings first — it is the least obvious and most frequent culprit.
Some accounts additionally use a two-password mode, where the login password and the vault password are different. If the app accepts one and then asks for another, this is not an error: enter the second password. Write down which is which, so that a future sign-in does not turn into a puzzle.
Expired sessions and constant sign-outs
An expired session looks like a random logout: everything worked a minute ago, and now the vault is locked. This is normal behavior after a period of inactivity, after a device restart or after the app was updated. Sign in again and review the auto-lock timer — if it is set to a very short interval, the vault will keep locking itself, which can feel like a bug but is actually the security model working as intended.
If sign-outs happen on every device at the same time and without updates, check for security notifications in your account: an unexpected session termination can be a sign that someone else tried to access the account, and the service protected you by ending all sessions.
Browser problems that look like login errors
Extensions sometimes interfere with the sign-in page itself. An aggressive ad blocker, a privacy extension or a script blocker can prevent the page from loading the scripts it needs, and the result looks like a broken login form. Try an incognito window with extensions disabled: if the sign-in works there, disable extensions one by one to find the culprit.
Cleared cookies, strict tracking protection and outdated browser versions cause similar symptoms. Updating the browser and allowing the site's essential cookies usually solves the whole group of these issues at once.
When to contact official support
If every check above passes, the credentials are certainly correct and the problem repeats on different devices and networks, the cause may be on the account or service side. At that point, stop experimenting: gather facts for support — the exact error text, the time of the attempt, the device and browser — and contact Proton through its official channels.
And if you simply want to understand the whole picture before your next attempt, start with the main page of this portal: it collects everything about Proton Pass login, from the first sign-in to account recovery. Ten minutes of reading there will save you hours of guessing later.