Change:
This single command will fire up all the services, including the API server and the client applications available for you to work on. > [!NOTE] <del> > Once ready, open a web browser and **visit <http://localhost:8000>**. If the app loads, congratulations – you're all set! You now have a copy of freeCodeCamp's entire learning platform running on your local machine. </del> <ins> > Once ready, open a web browser and **visit <http://localhost:8000>**. If the app loads, sign in. Congratulations – you're all set! You now have a copy of freeCodeCamp's entire learning platform running on your local machine. </ins> > [!TIP] > The API Server serves APIs at `http://localhost:3000`. The Gatsby app serves the client application at `http://localhost:8000` <del> > If you visit <http://localhost:3000/explorer> you should see the available APIs. </del> <ins> > While you are logged in, if you visit <http://localhost:3000/explorer> you should see the available APIs. > [!WARNING] > Clearing your cookies or running `npm run seed:certified-user` will log you out, and you will have to sign in again. </ins> ## Sign in with a local user

Discussion:
<!-- NOTE: If you want to become an author on freeCodeCamp, you can find everything here: --<!-- If you are reporting an issue with an article on our News publication, please follow this link to send an email to our editorial team -- <!-- Add a link to the page with the problem. --<!-- Describe the problem and how to reproduce it. --Do all steps up to and including "Step 4: Start the freeCodeCamp client application and API server." If you go to localhost:8000 at this point you should be signed out. The docs then has a note "If you visit http://localhost:3000/explorer you should see the available APIs." However, if you go to localhost:3000 while signed out, it redirects to localhost:8000 and you get a banner that says "Access token is required for this request." If you sign in then go there, it works. <!-- A clear and concise description of how you want to update it. --Move the note to the bottom of the "Sign in with a local user" section so it works at that point in the doc. <!-- If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box). --<img width="1536" alt="Screen Shot 2022-04-25 at 6 06 06 PM (2)" src="https://user-"<img width="980" alt="Screen Shot 2022-04-25 at 6 12 16 PM" src="https://user-"Related issues: ,
Hello there This should not be the case. If you have correctly seeded the DB, and have started both the server and client, then going to automatically signs you in as the development user.
Hi, thanks for responding to this issue. Are you sure it automatically signs you in? If I clear my cookies, npm run seed, npm run develop, then go to localhost:8000, I am not signed in. Even the doc has saying you have to click the "Sign In" button...
I am quite sure - I do it multiple times per day. If you are not automatically signed in, then you will most likely get some useful output in the server terminal, and possibly something in the DB logs. Would you mind sharing them?

It's true that you stay signed in if you , but the very first time you go to you still need to sign in. Once that's done you'll stay signed in until you either clear your cookies or .
Thank you, for the correction. Why do we not need to sign in for each Gitpod instance, then?
Good question. Turns out it's the same thing: when you log into fcc while it's running on GitPod the cookies get set for the domain. That means the login carries over to the next time you open up GitPod.
Thanks for the confirmation I guess it seemed like we had different experiences because you were already signed in. But the dev following the doc will not be signed in and will not be able to visit the API explorer, so I suggest editing the doc. Should I go ahead and make a quick pull request?
Thanks, a PR to the docs would be helpful.