[BUG] 2FA setup not working

[sebiweise]

Issue Summary

I´m not able to setup 2FA for my account and therefor not able to access the admin settings.

RangeError: Invalid key length
    at Cipheriv.createCipherBase (node:internal/crypto/cipher:122:19)
    at Cipheriv.createCipherWithIV (node:internal/crypto/cipher:141:3)
    at new Cipheriv (node:internal/crypto/cipher:249:3)
    at Object.createCipheriv (node:crypto:141:10)
    at symmetricEncrypt (/var/task/apps/web/.next/server/chunks/69559.js:1:278)
    at handler (/var/task/apps/web/.next/server/pages/api/auth/two-factor/totp/setup.js:1:3199) {
  code: 'ERR_CRYPTO_INVALID_KEYLEN'
}

Steps to Reproduce

1. Setup cal.com on Vercel
2. Try to setup 2FA
3. Look into the logs

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?

Actual Results

• 2FA setup is not working

Expected Results

• 2FA setup is working and I´m able to use the admin settings

Technical details

• Browser Chrome
• Node.js version 18.x
• Hosted on Vercel
• DB neon.tech

[tyrelwar]

I receive the same thing. but additionally it also applies to when i attempted to add a caldav calendar

@calcom/web:start: RangeError: Invalid key length
@calcom/web:start: at Cipheriv.createCipherBase (node:internal/crypto/cipher:122:19)
@calcom/web:start: at Cipheriv.createCipherWithIV (node:internal/crypto/cipher:141:3)
@calcom/web:start: at new Cipheriv (node:internal/crypto/cipher:249:3)
@calcom/web:start: at Object.createCipheriv (node:crypto:141:10)
@calcom/web:start: at symmetricEncrypt (/calcom/apps/web/.next/server/chunks/69559.js:1:278)
@calcom/web:start: at handler (/calcom/apps/web/.next/server/chunks/48015.js:1:405)
@calcom/web:start: at async handler (/calcom/apps/web/.next/server/pages/api/integrations/[...args].js:1:5858) {
@calcom/web:start: code: 'ERR_CRYPTO_INVALID_KEYLEN'

[tyrelwar]

@sebiweise i found the issue with mine when i set the encryption key in the docker variables i included the *- after the key that was created. i dont know if it will work for you but it resolved my issue doing it that way

[sebiweise]

@sebiweise i found the issue with mine when i set the encryption key in the docker variables i included the *- after the key that was created. i dont know if it will work for you but it resolved my issue doing it that way

So when I run the openssl (openssl rand -base64 32) command I´m getting somthing like this:
KTPdDrXkegeC1hphG97EUEHniUullNU+BKwdTDdINLk=

So you mean that I should add *- at the end or what´s the solution?

[tyrelwar]

these are the variable i had to set and the instructions i followed to get it working

[sebiweise]

Ah ok, this is weird. The .env.example file tells you to use a 32 character key, but in local-development you should use 24 characters and then it works fine entering your passwort. I've used this command: openssl rand -base64 24.
I had to delete my current database/user(s), but after re-registering I was able to set up 2FA.

But now I got this error:

The code I´ve entered is the fresh 2FA code (I removed it for the screenshot)

Logs showing some bad 400 requests

[tyrelwar]

So a lot of times that is a time mismatch is this a 2fa app you use alot and it works for other apps or is this a new one?

If it's a new one in the settings there should be option to sync time

[sebiweise]

So a lot of times that is a time mismatch is this a 2fa app you use alot and it works for other apps or is this a new one?

If it's a new one in the settings there should be option to sync time

I don´t know why but after a restart of my pc it is working fine. Could be the time issue that was fixed with the restart.
Thanks for your help.