I am going through an official interactive course on https://nextjs.org/learn/dashboard-app . I was away for a few weeks, and now I am getting a 404 error while trying to sign in. I want to continue learning and keep my progress, but I cannot sign in. Anyone having the same issue?
There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.
https://community.vercel.com/t/debugging-404-errors/437
A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
It works for me! Are you using this same account you used to sign in with Vercel community?
I have the same issue. Just was trying to resume my learning process, and now upon entering my username I'm presented with https://nextjs.org/auth/error with no explanation - just text in the middle of the screen "404. This page could not be found.". Clearing cookies does not help - the problem persists both in Opera and Edge. To be exact, upon entering my registered email during login process I'm sent a one-time code which I'm entering on Vercel registration page and here we go - site tries to start my authorized session but fails and sends me "404. This page could not be found." When I clear cookies and move right to the start page of the tutorial, App Router | Next.js I get the following message in the browser developer tools: Access to fetch at ' https://vercel.com/oauth/authorize?client_id=cl_vgU5gcm9u05rNEMZCphYCZXg4oUb0QsF&redirect_uri=https%3A%2F%2Fnextjs.org%2Fapi%2Fauth%2Fcallback&state=fVAulFdz3mXCtuxAw3J1m2qfZRpFq6PYp_HfZDf10LA.dashboard-app&nonce=YIn7I4XR33Is568v7nJJjEScC25LLHKOaLH7lUGsO1Y&code_challenge=n-aGbullH1aVJJhx7eAANfN1-NloQni76RgHAsjME-s&code_challenge_method=S256&response_type=code&scope=openid+offline_access ' (redirected from ' https://nextjs.org/api/auth/authorize?slug=dashboard-app&_rsc=EwBViB_kMfvFPeRv ') from origin 'https://nextjs.org' has been blocked by CORS policy: Request header field rsc is not allowed by Access-Control-Allow-Headers in preflight response. At the same time on each attempt I see some tokens registered on the page: https://vercel.com/account/settings/tokens with description similar to "Next.js Learn from Vercel/Qmc52npNy86S8VV4Mt8a8dP1LEkRNbgosW3pBCQytkcgf2'
