> For the complete documentation index, see [llms.txt](https://docs.wproofreader.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/client-side/how-to-access-the-browser-console-errors-and-failed-requests-in-the-network-tab.md).

# How to access the browser console errors and failed requests in the network tab?

This guide will help you to extract helpful information about errors from the browser console and network tabs. In this guide, we will use the Chrome browser. You can do the same steps using your browser.

1\. Open your web app or website which integrates the functionality of WebSpellChecker.

2\. Open the Chrome **DevTools**. Refer to the official guide [here](https://developers.google.com/web/tools/chrome-devtools/open).

3\. Select Console tab.&#x20;

4\. Select Network tab and filter by requests to WebSpellChecker. Depending on the deployment option you selected, there might be different entry points to WebSpellChecker: SSRV component (ssrv.cgi) or AppServer.

* ssrv.cgi –> Headers

![](/files/nP1OChTO5zWbHIz9To7H)

* ssrv.cgi –> Response

![](/files/JKUY6Q79M1z5xyfP8qCt)

#### How to extract the HAR file <a href="#draft-howtoaccessthebrowserconsoleerrorsandfailedrequestsinthenetworktab-howtoextracttheharfile" id="draft-howtoaccessthebrowserconsoleerrorsandfailedrequestsinthenetworktab-howtoextracttheharfile"></a>

To provide the support team with the full info about the failed request from your network tab, export it as a HAR file.&#x20;

* Select a failed request
* Click on Export HAR file
* Save the HAR file

![](/files/FxmtZKX2FM8uFHeFje9w)

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.wproofreader.com/v6.10.0.0/troubleshooting/client-side/how-to-access-the-browser-console-errors-and-failed-requests-in-the-network-tab.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
