This post was most recently updated on September 7th, 2021.2 min read.
This article explains a quick solution to a pretty common problem with Azure DevOps. Namely – random and annoying 404 (or sometimes 401) errors when trying to access your dear team projects.
I forgot to take screenshots of the errors and couldn’t figure out how to reproduce them, but hey, the fix is the main point, right? 😀 If you’ve ended up on this page, you’ve probably encountered the issue already, so why would you care about the screenshots anyway.
Ok, so this is a pretty easy one. Below, you’ve got 2 options: either a super-simple 1-step solution or a standard-simple 5-step solution.
Time needed: 5 minutes.
How to (usually) fix 404 or 401 errors in Azure DevOps?
- (Optional shortcut) Just forget about the rest of the steps and use a different browser
Yeah. That’ll do the trick.
It won’t fix your primary default browser, though – so if you want to have that back, follow the rest of the steps!
- Navigate to the Project home
You probably have that in your browser “bookmarks” or “recents” or something. You should just open up the page and get that sweet, sweet 404 error. Don’t fret, though – we’ll fix it (probably)!
- Select the “lock”-icon
This works very similarly in most Chromium-based browsers – but the icon should look somewhat like this:
- Select “Cookies”
Clickety-click it open, and you should get a nice dialog showing you the active cookies for the site.
- Clear all cookies for “dev.azure.com”
Select the dev.azure.com domain and hit “Remove”.
Don’t worry – you’ll get them back.
- Refresh the page
Hit F5 and you should be good!
Did it work? Let me know in the comments -section below!
- How to fix a 403.18 in a virtual application? - September 20, 2021
- GitHub Action fails with “The GITHUB_TOKEN environment variable was not set” - September 15, 2021
- How to download audio files from Vidyard - September 7, 2021