[BUG] Unable to authenticate with 2FA about runtipi HOT 16 CLOSED

If it’s still happening, you can go through the reset password process to disable 2FA manually

from runtipi.

May I ask you to re-enable 2FA and tell me if this error keeps happening?

After resetting my password I've updated Tipi to version 2.5.0. Then I've re-enabled 2FA, logged out and now everything seems to work correctly, the login process with new 2FA is ok.

from runtipi.

Stack Trace from tipi-dashboard:

Error from server Error: Unsupported state or unable to authenticate data
    at o (/app/.next/server/chunks/5162.js:1:31638)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/.next/server/chunks/8545.js:278:100171
    at async /app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:406
    at async rm (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:15:5703)
    at async rD (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:22546)
    at async doRender (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1391:30)
    at async cacheEntry.responseCache.get.routeKind (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1552:28)
    at async NextNodeServer.renderToResponseWithComponentsImpl (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1460:28)
    at async NextNodeServer.renderPageComponent (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1843:24)

from runtipi.

I am having the same issue

from runtipi.

Does it happen after a full stop and start of runtipi?

from runtipi.

@meienberger yes, restarted tipi, restarted the server and nothing changed.
Finally did a password reset and it is working again.

from runtipi.

After some investigation, I still cannot find the root cause of this issue. However, I was able to reproduce the issue by changing my env var JWT_SECRET to a new value. @JigSawFr @malaiCo is it possible that you did something like that? Or removed .env file? The secret is generated deterministically based on state/seed so this might happen during a migration aswell if the seed file was not transferred over

from runtipi.

Completely removed state folder on my side ... 👯

from runtipi.

I have the same problem. I've also tryed the password reset but nothing has changed. I did it after a full stop of Tipi + complete reboot of the machine.

from runtipi.

I have the same problem. I've also tryed the password reset but nothing has changed. I did it after a full stop of Tipi + complete reboot of the machine.

What do you mean nothing changed? Were you able to reset your password?

from runtipi.

What do you mean nothing changed? Were you able to reset your password?

No, basically I'm locked out from the dashboard. I've done "runtipi-cli reset-password" that gave me "Password reset request created. Head back to the dashboard to set a new password", but when I go back to the dashboard I'm stuck with the same situation as screenshotted in the first post.

from runtipi.

It is not possible that after a successful password reset you get prompted for 2FA. You didn't complete the process. Go to /login, click on forgot password and follow the instructions on screen

from runtipi.

click on forgot password and follow the instructions on screen

You are right I've missed the quoted part. Now I'm in, thanks.

from runtipi.

click on forgot password and follow the instructions on screen

You are right I've missed the quoted part. Now I'm in, thanks.

No problem, glad you are unstuck now. May I ask you to re-enable 2FA and tell me if this error keeps happening? This would help me understand if it's something related to a recent update or specific to some user configs

from runtipi.

For me this happened after I have updated to 2.5 (coming from 2.1 or 2.2 - don't remember exactly). Does this change something in the env or on the secret?

from runtipi.

This issue is stale because it has been open for 30 days with no activity.

from runtipi.