New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clerk: Clock skew detected #86
Comments
I get this error all the time, I usually speed up the timer and stop this error but I think it is something clerk is trying to fix |
I have the same problem when I try to login with Clerk authentication. |
In my case I'm running WSL2 with Ubuntu in my Windows 11 machine. When I checked the time in the ubuntu terminal (where the nextjs app is running) it was out of sync with Windows so I had to update it manually with the following command sudo hwclock -s. After that the problem was solved. I read that it's a common problem when the computer go to sleep, the Ubuntu clock gets out of sync with Windows. |
Encountered the same Problem on WSL2, computer was also put to sleep before . |
` To resolve this issue, make sure your system's clock is set to the correct time (e.g. turn off and on automatic time synchronization). JWT cannot be used prior to not before date claim (nbf). Not before date: Sat, 07 Oct 2023 17:50:14 GMT; Current date: Sat, 07 Oct 2023 17:50:07 GMT; (reason=token-not-active-yet, token-carrier=cookie) This error happened while generating the page. Any console logs will be displayed in the terminal window. |
I dont have wsl setup in my computer still getting this problem |
If you are using Windows 11 and encountering an error, you can attempt to resolve it by following these steps:
This fixed my issue, You can give it a try. |
I've just tried that, including restarting the system. This error just started happening suddenly, the app was opening normally and I didn't change any date and time settings. I also checked my project on Clerk and everything seems fine on there. What else could it be? |
I've tried that but unfortunately it's still happening. I didn't mess with my date and time settings, the project was opening normally and that issue just suddenly started happening! This is so odd. What else could that be? |
I've tried fixing the time on settings but unfortunately it's still happening. I didn't mess with my date and time settings, the project was opening normally and that issue just suddenly started happening! This is so odd. What else could that be? |
this work, thanks |
Well i fix it but i dont rly know how.
One ot this steps fix my issue in sync time. |
Resolved my isssue clearly. |
thanks a tonn manhh |
You should go to 'Date and time' settings on windows and there 'Sync now'
If this doesn't work then , try turning off/on the 'set automatic time' and
'select automatic timezone' for both try turning off/on and try also with
sync now :))
…On Thu, 30 Nov, 2023, 1:39 pm PhucHung2k1, ***@***.***> wrote:
i can'f fix it. help me pls..
image.png (view on web)
<https://github.com/adrianhajdin/threads/assets/124114709/4c96636b-81a6-4260-9d96-02e54e82d4fd>
—
Reply to this email directly, view it on GitHub
<#86 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWZGTS5Y5T62AATOHBWQ4D3YHA5NFAVCNFSM6AAAAAA5KONN2SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZTGI4DKMRYGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Again try with sync now and also try different combinations of those above
2 options like set auto for both time and zones it worked fomme
…On Thu, 30 Nov, 2023, 1:48 pm PhucHung2k1, ***@***.***> wrote:
You should go to 'Date and time' settings on windows and there 'Sync now'
If this doesn't work then , try turning off/on the 'set automatic time' and
'select automatic timezone' for both try turning off/on and try also with
sync now :))
… <#m_1441043557748212991_>
On Thu, 30 Nov, 2023, 1:39 pm PhucHung2k1, *@*.*> wrote: i can'f fix it.
help me pls.. image.png (view on web)
https://github.com/adrianhajdin/threads/assets/124114709/4c96636b-81a6-4260-9d96-02e54e82d4fd
<https://github.com/adrianhajdin/threads/assets/124114709/4c96636b-81a6-4260-9d96-02e54e82d4fd>
— Reply to this email directly, view it on GitHub <#86 (comment)
<#86 (comment)>>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWZGTS5Y5T62AATOHBWQ4D3YHA5NFAVCNFSM6AAAAAA5KONN2SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZTGI4DKMRYGU
<https://github.com/notifications/unsubscribe-auth/AWZGTS5Y5T62AATOHBWQ4D3YHA5NFAVCNFSM6AAAAAA5KONN2SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZTGI4DKMRYGU>
. You are receiving this because you commented.Message ID: @.*>
image.png (view on web)
<https://github.com/adrianhajdin/threads/assets/124114709/d3a786a4-7db3-4007-b449-7d8f37e64a26>
it take long time and doesn't work again :((
—
Reply to this email directly, view it on GitHub
<#86 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWZGTS5PJWLI32MDFVNB7GTYHA6N7AVCNFSM6AAAAAA5KONN2SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZTGI4TMMZSGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
@FredDaFed sudo apt install ntpupdate && sudo ntpdate pool.ntp.org |
I am using Mac and facing this error what steps would work ? |
Please refer my above instructions , prolly a mismatch btw time in ur system and time in server |
I change my localhost:3000 to another option such as localhost3001 and it worked. |
If you are mac, you can go to your date and time settings and then check the box for "set date and time automatically" if its and unchecked and uncheck if its checked. This fixed it for me |
Found the issue with my system. Now, I'm browing net/using ChatGPT to fix the time clock of WSL on my Windows system |
My issue resolved. Removed systemd-timesyncd and installed ntp. That synced my WSL time with the correct network time and I got rid of the error. |
Does anyone know how to handle this error accurately on the application level? Does it appear in production? |
Under the mac OS. I tried this command to force to sync my machine time.
Then issued fixed, for my case. |
this actually fixed it for me |
Update your system time like here https://time.is/, I updated and fixed the error |
WORKING SOLUTION FOR WINDOWS : Go To Services -> Windows Time -> Right click -> Start After that Go to Settings -> Date and Time -> Sync |
it's work! thank |
turning the "Set time Automatically" off worked for me :) |
I have this issue on Vercel... I deleted a user in Clerk auth, it was stored in the cookie and tried to use the cookie for logging in. |
hey @MatthewAraujo , could you please tell what do you mean by "speed up the timer"? |
thank you very much, It works for me! 💖 |
Error: Clerk: Clock skew detected. This usually means that your system clock is inaccurate. Clerk will continuously try to issue new tokens, as the existing ones will be treated as "expired" due to clock skew.
To resolve this issue, make sure your system's clock is set to the correct time (e.g. turn off and on automatic time synchronization).
JWT cannot be used prior to not before date claim (nbf). Not before date: Thu, 28 Sep 2023 06:35:34 GMT; Current date: Thu, 28 Sep 2023 06:35:04 GMT; (reason=token-not-active-yet, token-carrier=cookie)
The text was updated successfully, but these errors were encountered: