> For the complete documentation index, see [llms.txt](https://docs.defguard.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.defguard.net/2.1/support.md).

# Getting help

## Troubleshooting guide

We developed a comprehensive [troubleshooting guide](/2.1/support-1/troubleshooting.md) to help resolve your issue. We’ve put significant effort into ensuring it’s current and thorough.

## Community support (for all plans)

Having trouble with Defguard deployment or configuration? Reach out to our community for help.

Support is provided both by the community and by us (the Defguard authors) using GitHub Discussions. Create a new discussion using this [form](https://github.com/DefGuard/defguard/discussions/new/choose).

## Support portal (for active licenses with Basic/Direct support plans)

If you have an active license with **Basic** or **Direct** support plans, you can reach Defguard's support team using a dedicated Support Portal. It's **the most efficient way** to get help from the support team.

The easiest way to create a ticket in the support portal is by going to the Support page in you Defguard instance and clicking the *Open a Support Ticket* button.

Detailed instructions on using the Support Portal can be found in [this guide](/2.1/support-1/using-the-support-portal.md).

## Found a bug? Need a feature?

* Here you can submit [a bug report](https://github.com/DefGuard/defguard/issues/new?assignees=\&labels=bug\&projects=\&template=bug_report.md\&title=)
* And here you can submit [a feature request](https://github.com/DefGuard/defguard/issues/new?assignees=\&labels=feature\&projects=\&template=feature_request.md\&title=)

## Solved an issue yourself?

Please share your solution with the community so others can benefit from it. Leave a short description of the observed behaviour, expected behaviour, and the solution in our [Show and Tell section](https://github.com/DefGuard/defguard/discussions/categories/show-and-tell) on GitHub Discussions.

## Reporting a security vulnerability

{% hint style="danger" %}
Please do not report security vulnerabilities via GitHub issues. Dedicated reporting channels are listed below.
{% endhint %}

To report a security vulnerability open a [security advisory](https://github.com/defguard/defguard/security/advisories/new).

You can also send us an encrypted email message according to instructions in our [Vulnerability Disclosure Policy](https://defguard.net/security/#VDP-title).


---

# 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.defguard.net/2.1/support.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.