Fix login and session problems
Most sign-in problems have one of a few causes. Find the message you see below and follow the steps.
Common sign-in problems and how to fix them
Most likely cause: clock drift. TOTP codes are time-based. If your phone clock is more than 30 seconds off, every code is rejected.
Fix on iPhone: Settings → General → Date & Time → toggle Set Automatically off, then back on.
Fix on Android: Settings → General Management → Date and Time → enable Automatic date and time.
Second possible cause: the code was already used. Each 30-second code can only be accepted once. Wait for the next code to appear (watch the progress ring in your authenticator app) and enter the fresh one immediately.
This is about the API, not about signing in: on the website you sign in with your email address and a passkey or code, without a key. Check that the integration sends the full key (pgp_ followed by 64 characters) in the X-Api-Key header, with no trailing spaces. You find the key on Account under Advanced account key.
For a psk_live_ key for the ParaSign API, check on your account page that it is still active, and make a new one there if needed. A new account key (pgp_) you request at privacy@paramant.app.
A session ends after an hour without activity. While you are working that hour moves along, but after twelve hours every session ends, however active you were. This is deliberate: Paramant handles sensitive files and keeps no lasting sessions. Go back to paramant.app/en/auth/login and sign in again.
If you are often signed out halfway through a task, you could use the API from a script instead of the web dashboard, so an expiring session does not interrupt your work.
This is usually a browser cookie or script issue. Try these in order:
- Hard-refresh the page (Ctrl+Shift+R on Windows/Linux, Cmd+Shift+R on Mac).
- Clear site data for paramant.app: browser settings → Privacy → Site data → search "paramant.app" → delete.
- Disable browser extensions temporarily (ad blockers can interfere with form submissions).
- Try a different browser or a private/incognito window.
Clear cookies for paramant.app entirely. The session cookie may be damaged. After clearing, close and reopen the browser tab before you sign in again.
Your account is never locked, so there is nothing an administrator has to unlock. Instead, sign-ins are limited per internet connection: more than 5 attempts from one IP address within 15 minutes get a 429 (too many requests) response. The counter resets itself once the fifteen minutes are up. Someone else on your network can trigger it; switching to another connection gets you straight back in.
Nobody can shut out your email address with failed attempts. We count failed sign-ins per address, and a successful sign-in clears them. After ten failures within fifteen minutes, the next attempt asks your browser for a second or two of extra work instead of turning you away. So a stranger typing your address can slow your sign-in down for a moment, but can never make it impossible. If you are still refused after the fifteen minutes are up, email privacy@paramant.app with your account email.