jwt should have the "clockTolerance" option setting to avoid unexpected JWT "nbf" issue

[ceekoTanFuqi]

I met with the issue
unexpected JWT "nbf" (not before) claim value, timestamp is > now()    at ib (/app/.next/server/app/api/auth/[...nextauth]/route.js:377:22546)
The reason might be that the "nbf" in jwt is a little larger than now - maybe the "now" is not so accurate on different computers.
Any suggestions? Thanks.