JavaScript Load Error
Asked by Omar Almanza:

I had a client clear her cache in Chrome and when she tried to log back in it came back with a "JavaScript load error" She is not able to log in.![JavaScript Load Error.png](https://community.atlassian.com/t5/image/serverpage/image-id/79880i653694B5ECD1647A/image-size/large?v=v2&px=999 "JavaScript Load Error.png")


Answers:
author: Nayeemuddin Khan
body: In Chrome, allow JavaScript from Atlassian:

1. Open Chrome settings
2. Click on Advanced
3. Click on Privacy and Security
4. Click on Site Settings
5. Click on JavaScript
6. Make sure JavaScript is set to allowed
7. Next to Allow, click Add
8. Paste the URL from the error message in and click Add

Let us know if that resolve your clients issue.

comments: author: rachel gomez
body: Fix JavaScript errors

<br />

The first experience you have with the Console is likely to be errors in scripts.

Demo page: JavaScript error reported in the Console tool  
Open the demo webpage JavaScript error reported in the Console tool in a new window or tab.

Right-click anywhere in the webpage and then select Inspect. Or, press F12. DevTools opens next to the webpage.

In the top right of DevTools, the Open Console to view errors button displays an error about the webpage.

Click the Open Console to view errors button on the top right. In DevTools, the Console gives you more information about the error:

DevTools gives detailed information about the error in the Console.

Many error messages in the Console have a Search for this message on the Web button, shown as a magnifying glass. This feature was introduced in Microsoft Edge version 94. (For more information, see Search the web for a Console error message string.)

The information in this error message suggests that the error is on line 16 of the error.html file.

Click the error.html:16 link on the right of the error message in the Console. The Sources tool opens and highlights the line of code with the error:

The Sources tool highlights the line of code that causes the error.

The script tries to get the first h2 element in the document and paint a red border around it. But no h2 element exists, so the script fails.

Find and debug network issues  
The Console also reports network errors.

Demo page: Network error reported in Console  
Open the demo webpage Network error reported in Console in a new window or tab.

Right-click anywhere in the webpage and then select Inspect.

Console displays a Network and a JavaScript error.

The table displays loading, but nothing changes on the webpage, because the data is never retrieved. In the Console, the following two errors occurred:

A network error that starts with GET HTTP method followed by a URI.

An Uncaught (in promise) TypeError: data.forEach is not a function error.

Click the link to the webpage and line of code where the error occurs, to open the Sources tool. That is, click the network-error.html:40 link in the Console:

Select the link to the webpage and line of code where the error occurs, to open the Sources tool.

The Sources tool opens. The problematic line of code is highlighted and followed by an error (x) button.

Click the error (x) button. The message Failed to load resource: the server responded with a status of 404 () appears.

To find the error in JavaScript, use the Sources tool.

This error informs you that the requested URL isn't found.

Open the Network tool, as follows: open the Console, and then click the URI that's associated with the error.

The Console displays an HTTP status code of the error after a resource isn't loaded:

The Console displays an HTTP status code of the error after a resource isn't loaded.

The Network tool displays more information about the failed request:

The Network tool displays more information about the failed request.

Inspect the headers in the Network tool to get more insight:

Inspecting the headers in the Network tool may give more insight.

What was the problem? Two slash characters (//) occur in the requested URI after the word repos.

Open the Sources tool and inspect line 26. A trailing slash character (/) occurs at the end of the base URI.

Regards,

Rachel Gomez


author: Experieco_Build
body: Did the same as mentioned, still getting same error.


Tags: feedback-forum