Session and login issues.
Most Paramant login failures have a small set of root causes. Find your error message below and follow the steps.
Common issues
Most likely cause: clock drift. TOTP codes are time-based. If your phone clock is more than 30 seconds off from real time, every code will be 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 possibility: 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.
Check that you copied the full 64-character key with no trailing spaces. In password managers, use the copy button rather than selecting manually. If you recently regenerated your key, make sure you saved the new one before closing the dashboard.
If the key was revoked: generate a new one in Dashboard → API keys.
Sessions last 1 hour from the time of login. This is by design — Paramant handles sensitive files and does not support persistent sessions. Return to paramant.app/auth/login and authenticate again.
If you are frequently logged out mid-task, consider using the API directly from a script rather than the web dashboard, so work is not interrupted by session expiry.
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 corrupt. After clearing, close and reopen the browser tab before attempting login again.
There is no account lock, so there is nothing an administrator has to unlock. Sign-ins are rate limited per internet connection instead: more than 5 attempts from one IP address inside 15 minutes are answered with a 429, and that counter clears itself once the fifteen minutes are up. Somebody else on your network can set it off; using another connection gets you straight back in.
Your email address cannot be rate limited shut. Failed sign-ins are counted against the address, but only failures count, a successful sign-in clears them, and past ten inside fifteen minutes the next attempt asks your browser for a second or two of work rather than turning you away. So a stranger typing your address can make signing in slower for a moment and can never make it impossible. If you are still refused after the fifteen minutes are up, email privacy@paramant.app with your account email.