> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/gateway/knowledge-base.md). # Knowledge base The Knowledge base brings together task-oriented and reference content that goes beyond the core product documentation, organized into these three sections: * [How-to articles](https://docs.devolutions.net/gateway/knowledge-base/how-to-articles) walk through specific configuration scenarios and integrations, such as launching RDP or SSH sessions in a web client, deploying Gateway quickly, or setting it up behind a reverse proxy or an external browser. * [Knowledge base articles](https://docs.devolutions.net/gateway/knowledge-base/knowledge-base-articles) cover reference material on tunnel connection types and recording paths. * [Troubleshooting articles](https://docs.devolutions.net/gateway/knowledge-base/troubleshooting-articles) document known issues and their resolutions, including installation problems, certificate errors, session recording issues, and RDP web client display problems. --- # 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.devolutions.net/gateway/knowledge-base.md?ask=&goal= ``` `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.