HTTP Status 404 error

Owned by Daniel Smith
Last updated: Jul 11, 2019
3 min read

Problem

A user attempts to access Avatar direct via their browser, and instead of the Avatar splash/Start page, they see something similar to the screenshot below:

Solution

While it may seem like the website/application is down, that may not be the case with this specific error – and, in fact, you're more likely to see "Page not available" if the website is actually down. Instead, there could be other issues at play, specifically client side (which means the user's workstation) and possibly with the browser they're using. One possible solution could be to clear/delete cookies and other stored data from their browser – this guide will cover how to do that in Internet Explorer 11 and Google Chrome. 

Please note that clearing/deleting cookies and stored data may delete stored login information (i.e. passwords) for your browser, meaning you will have to save that information again on the websites you visit if you have done so. For Chrome users, if you use your Google account while using Chrome then this information should still autofill but you'll have to deliberately log in. 

Internet Explorer

For IE, you will first have to access the Settings near the top right corner of the browser, then go to Internet Options:

From there, under the General tab, look for the Delete button and click it:

You'll then have options as to what you would like to delete – for the purposes of this article, we checked off the two relevant options:

Google Chrome

For Google Chrome, the process is similar to IE. First, go to the contextual menu near the top right of the browser (looks like 3 dots in a column), then hover your mouse over the More Tools option:

A new menu should pop out, and you'll want to click on Clear Browsing Data:

On the next screen it will give you three options – again, for the purposes of this article, we're displaying the relevant two options in the screenshot below (Cookies and other site data & Cached images and files):

For full browser troubleshooting you may want to also flush your DNS cache, which is covered in this article (support staff only): DNS flush

-END