# How-to troubleshoot the service issues
If you are experiencing any issues in the normal functioning or full denial of the on-premises version of the WebSpellChecker package, here are the steps that will help you to define the root cause of the problem. Also, the same findings will be useful if you eventually decide to contact the technical support. The required information is marked with TODO status.
### Server-side components
1\. Check the logs recorded by AppServer. The logs folder is located in the /WebSpellChecker installation directory/AppSever/Logs/. Are there any errors?
TODO Archive a folder with **/Logs into a \*.zip archive** and send it to the support team.
3\. Check the AppServer status and version. What responses do you get?
* [CheckAppServerVersion](https://docs.wproofreader.com/v6.12.0/troubleshooting/server-side-backend/pages/IA2KNQLXDh85TwDivL4y#mainappservercommands-3.checkappserverversion)
* [CheckAppServerStatus](https://docs.wproofreader.com/v6.12.0/troubleshooting/server-side-backend/pages/IA2KNQLXDh85TwDivL4y#mainappservercommands-4.checkappserverstatus)
TODO Make screenshots or copy/paste the responses that you get when checking the **status** and **version** and provide it to the support team at ****.
4\. Check the browser console and network tabs to see if there are any errors or failed requests to WebSpellChecker. Are there any errors? Are there any requests to WebSpellChecker at all?
Don't know how to access your browser tab or check requests in the network tab? No problem, please check [How to access the browser console errors and failed requests in the network tab](broken://pages/arbpHD8aMMjRHJJ3MtNA).
TODO Make screenshots of the **console errors** and **failed requests**. For the failed requests, it is recommended to export a HAR file with the failed requests. HAR files contains full information about the request.
5\. Also, the support team may ask to provide /**AppServer/AppServerX.xml** file to validate the used settings for your installation.
6\. Check your Firewall restrictions; whether the necessary ports are opened; user permissions (for Linux); validity of the SSL certificate files.
7\. If you run WebSpellChecker on Docker, TODOspecify whether you use [default Docker image](https://hub.docker.com/r/webspellchecker/wproofreader) or created a [custom](https://github.com/WebSpellChecker/wproofreader-docker) one. Did you make any modifications in the Dockerfile before its using?
### Client-side components
1\. What type of the product do you use (WProofreader, SCAYT for CKEditor 4, Web API, ect.)?
2\. Where the spelling/grammar checking feature is integrated?
* Is this a rich text editor or plain HTML control?
* What is the version of your rich text editor? Is it up to date?
Also, might be useful:
* [Common errors while configuring on-premise WebSpellChecker version](/v6.12.0/troubleshooting/server-side-backend/common-errors-while-configuring-on-premise-webspellchecker-version.md)
* [Common license errors](/v6.12.0/deployment/licensing/common-license-errors.md)
---
# Agent Instructions: 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.12.0/troubleshooting/server-side-backend/how-to-troubleshoot-the-service-issues.md?ask=
```
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.