# Troubleshooting

- [Troubleshooting](https://docs.openappsec.io/troubleshooting/troubleshooting.md)
- [Troubleshooting Guides](https://docs.openappsec.io/troubleshooting/troubleshooting-guides.md)
- [Configuration contains ingress/asset with URL which already has asset attached to it in your tenant](https://docs.openappsec.io/troubleshooting/troubleshooting-guides/configuration-contains-ingress-asset-with-url-which-already-has-asset-attached-to-it-in-your-tenant.md)
- [HTTP Request to Port 80 Not Returning as Expected](https://docs.openappsec.io/troubleshooting/troubleshooting-guides/http-request-to-port-80-not-returning-as-expected.md): Guide for Handling NGINX Port 80 HTTP Requests in Linux
- [Agent Fails to Recognize HTTP Transactions with NGINX](https://docs.openappsec.io/troubleshooting/troubleshooting-guides/agent-fails-to-recognize-http-transactions-with-nginx.md): If you're experiencing issues with your WAF agent not recognizing traffic, follow these steps to troubleshoot and resolve the problem
- [Agent Not Recognizing Initial HTTP Requests](https://docs.openappsec.io/troubleshooting/troubleshooting-guides/agent-not-recognizing-initial-http-requests.md)
- [Handling Large Requests (413 Responses)](https://docs.openappsec.io/troubleshooting/troubleshooting-guides/handling-large-requests-413-responses.md)
- [open-appsec on Docker HTTP Transaction Handler Is Set To Ready](https://docs.openappsec.io/troubleshooting/troubleshooting-guides/open-appsec-on-docker-http-transaction-handler-is-set-to-ready.md)
- [Traffic Recognition Issue on Single-Core Machine/Connection Timed Out](https://docs.openappsec.io/troubleshooting/troubleshooting-guides/traffic-recognition-issue-on-single-core-machine-connection-timed-out.md)
- [Installing open-appsec on CentOS 7](https://docs.openappsec.io/troubleshooting/troubleshooting-guides/installing-open-appsec-on-centos-7.md): If you encounter issues during the installation of the agent on CentOS 7, follow these troubleshooting steps to ensure a successful setup.
- [SELinux: checking status and disabling](https://docs.openappsec.io/troubleshooting/troubleshooting-guides/selinux-checking-status-and-disabling.md)
- [Deploy open-appsec directly on the web server hosting the application to protect](https://docs.openappsec.io/troubleshooting/troubleshooting-guides/deploy-open-appsec-directly-on-the-web-server-hosting-the-application-to-protect.md)
- [object is locked or remote, and therefore cannot be modified](https://docs.openappsec.io/troubleshooting/troubleshooting-guides/object-is-locked-or-remote-and-therefore-cannot-be-modified.md)
- [Policy Load Status: Error / Failed to Register to Fog](https://docs.openappsec.io/troubleshooting/troubleshooting-guides/policy-load-status-error-failed-to-register-to-fog.md)
- [Failed to set sitePolicy for asset... using the original signatures](https://docs.openappsec.io/troubleshooting/troubleshooting-guides/failed-to-set-sitepolicy-for-asset...-using-the-original-signatures.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.openappsec.io/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.