# Getting help

## Troubleshooting guide

We developed a comprehensive [troubleshooting guide](https://docs.defguard.net/support-1/troubleshooting) 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.&#x20;

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

## Email Support (for paid plans only)

If you have bought a [Business or Enterprise license](https://defguard.net/pricing/), you can reach us at our support email <support@defguard.net>.

{% hint style="warning" %}
Please remember to send your support request from the same domain used when purchasing the license. If you contact us from a different domain, your request will be redirected to our community support.
{% endhint %}

## Found a bug? Need a feature?

{% hint style="warning" %}
Please remember to create an issue only if you're sure that you found a bug or you're missing a feature. If you are unsure whether something is a bug or a missing feature, start with a [GitHub Discussion first](https://github.com/DefGuard/defguard/discussions/new/choose).
{% endhint %}

Create an issue in our [main repository](https://github.com/DefGuard/defguard/issues).

In order for your issue to be processed efficiently, make sure it's well described. Please read [our guide on how to submit issues](https://docs.defguard.net/support-1/how-to-submit-an-issue).

Please use our issue templates for [bugs](https://github.com/DefGuard/defguard/issues/new?assignees=\&labels=bug\&projects=\&template=bug_report.md\&title=) and [features](https://github.com/DefGuard/defguard/issues/new?assignees=\&labels=feature\&projects=\&template=feature_request.md\&title=). Try to fill as much information as possible.

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