TypeError: The "key" argument must be of type string or an instance of Buffer, TypedArray, DataView, or KeyObject. Received undefined

[theindianappguy]

I see this as soon as i download and run with

yarn
yarn dev

[leerob]

Hmmm, what version of Node.js are you using?

[fizerkhan]

Same error. Node version - v14.15.3

[haafidz-jp]

same problem node - v14.15.3

[leerob]

Do you only see this when using next dev? Or is it with next build too?

[haafidz-jp]

im using yarn dev. and local .env

[3rg1s]

Do we have any fix for this issue yet? I tried to resolve it but didn't manage to get it fixed.

I had the project running by removing the googleapis package on the package.json file. But the home page is giving an error:

451 – Unavailable For Legal Reasons

[jeremycos]

Hello. I had the same problem.

It comes from the @lib/google with the crypto library. So I removed the entire @lib/google and all references (with youtube) in index.js. And now it works fine.

[omaralsoudanii]

@leerob not sure if this helps or not, but i think the cypher is generated through OpenSSL and between v.14.15.3 to the current LTS version there is a lot of changes in this area ( due to patched OpenSSL vulnerability ).

So maybe it doesn't work because you have the newer version with the patched OpenSSL stuff and the others don't.

Check the changelogs

[Deep-Codes]

Hello. I had the same problem.

It comes from the @lib/google with the crypto library. So I removed the entire @lib/google and all references (with youtube) in index.js. And now it works fine.

This works tho a lot of work 😅

[NickCrews]

I'm pretty sure the problem is that people haven't fully followed the instructions, and they haven't copied .env.example into .env.local and actually filled in values for GOOGLE_ENCRYPTION_KEY and GOOGLE_ENCRYPTION_IV. I had this issue, and then filled in these values with 1234. Then at least the error changed to the thing below, which I assume is "You're not using a valid encryption key, you doofus," which makes sense since. @leerob I bet you could reproduce this if you deleted those entries in your .env.local?

I'd imagine the workaround is either

1. Add valid GOOGLE_ENCRYPTION_* variables
2. Remove all the offending code as @jeremycos suggests
3. Make things fail more gracefully, so if you don't have valid keys then your youtube API calls etc should return some empty placeholders. I'm trying to do this and plan to submit a PR here.