> 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.md).

# Troubleshooting

- [Client-side](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/client-side.md)
- [How to access the browser console errors and failed requests in the network tab?](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)
- [Overview of HTTP response status codes](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/client-side/overview-of-http-response-status-codes.md)
- [CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/client-side/cors-policy-no-access-control-allow-origin-header-is-present-on-the-requested-resource.md)
- [Error in console: The product 'scayt2\_wsc\_dialog' is not available or enabled for your subscription](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/client-side/error-in-console-the-product-scayt2_wsc_dialog-is-not-available-or-enabled-for-your-subscription.md)
- [Spell Checker "WSC" dialog plugin for CKEditor 4 stopped working: incessant loading spinner](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/client-side/spell-checker-wsc-dialog-plugin-for-ckeditor-4-stopped-working-incessant-loading-spinner.md)
- [WProofreader or SCAYT icons are broken on the product interface](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/client-side/wproofreader-or-scayt-icons-are-broken-on-the-product-interface.md)
- [Often issues while configuring Cloud services](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/client-side/often-issues-while-configuring-cloud-services.md)
- [Plugin for CKEditor 5: 'WEBSPELLCHECKER' is not defined](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/client-side/plugin-for-ckeditor-5-webspellchecker-is-not-defined.md)
- [WProofreader autocorrect not working in CKEditor 5 v.35](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/client-side/wproofreader-autocorrect-not-working-in-ckeditor-5-v.35.md)
- [Server-side/backend](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/server-side-backend.md)
- ['Exception: Java heap space' record in the Logs files](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/server-side-backend/exception-java-heap-space-record-in-the-logs-files.md)
- [How-to troubleshoot the service issues](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/server-side-backend/how-to-troubleshoot-the-service-issues.md)
- [Common errors while configuring on-premise WebSpellChecker version](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/server-side-backend/common-errors-while-configuring-on-premise-webspellchecker-version.md)
- [CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/server-side-backend/cors-policy-no-access-control-allow-origin-header-is-present-on-the-requested-resource.md)
- [IIS web server option is grayed out during the installation](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/server-side-backend/iis-web-server-option-is-grayed-out-during-the-installation.md)
- [Cannot parse ini file "...\AppServer\AppServerX.xml". Reason: XmlDomParser. Invalid token \[..\]](https://docs.wproofreader.com/v6.10.0.0/troubleshooting/server-side-backend/cannot-parse-ini-file-...-appserver-appserverx.xml-.-reason-xmldomparser.-invalid-token-...md)


---

# 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:

```
GET https://docs.wproofreader.com/v6.10.0.0/troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.