Replies: 4 comments 1 reply
-
Removing maxAge: Number(process.env.JWT_TIMEOUT!) fixed the issue for now. |
Beta Was this translation helpful? Give feedback.
-
I found out a workaround hardcoding the maxAge number doing this:
instead of
if its of any help. |
Beta Was this translation helpful? Give feedback.
-
Okay, I just did some checking and logging. Turns out that's something wrong in the NEXTAUTH_JWT_TIMEOUT=86400 # for 1 day - 86400 = 1* 24 * 60 * 60 process.env.NEXTAUTH_JWT_TIMEOUT // "86400 # for 1 day - 86400 = 1* 24 * 60 * 60" So, I just need to put the comment above the declaration. # for 1 day - 86400 = 1* 24 * 60 * 60
NEXTAUTH_JWT_TIMEOUT=86400 |
Beta Was this translation helpful? Give feedback.
-
It's also a possibility that your postgresql database uses |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Question 💬
I am deploying a Nextjs app using Next-Auth to AWS App Runner. I am using the Cognito Provider.
In the logs I can see the following error:
I have tried everything to get rid of this. This issue does not occur on localhost.
How to reproduce ☕️
This is my [...nextauth].ts file
Contributing 🙌🏽
Yes, I am willing to help answer this question in a PR
Beta Was this translation helpful? Give feedback.
All reactions