# Common Problems

### Requests to API are being rejected by not using HTTPS <a href="#https-issue" id="https-issue"></a>

Currently there is no built-it **SSL** support in on-premise package, so you should add an **NGINX or other web server** with **SSL** in front of **Docker** instance which will proxy requests to Docker instance. This is planned to be added in future as a built-it functionality.

### Forbidden error when connecting to self-hosted Jet Bridge <a href="#https-issue" id="https-issue"></a>

**Jet Bridge** package include **JWT\_VERIFY\_TOKEN** inside it to verify requests from the frontend. By default it uses our Cloud **JWT\_VERIFY\_TOKEN**, but for on-premise you have different JWT key pair (randomly generated on install) so you need to change it. You should make it equals to the **JWT\_VERIFY\_KEY** value in your on-premise package config.

```
# Jet Bridge setting
JWT_VERIFY_KEY=-----BEGIN PUBLIC KEY-----\nMIICIjANBgkqhkiG9w0BAQEFAAOC...

# If using Jet Bridge for Django
JET_JWT_VERIFY_KEY=-----BEGIN PUBLIC KEY-----\nMIICIjANBgkqhkiG9w0BAQEFAAOC...
```

{% hint style="info" %}
You you can learn more about Jet Bridge configuration [here](/jet-bridge-deployment/jet-admin/configuration.md)
{% endhint %}


---

# 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.jetadmin.io/jet-bridge-deployment/on-premise/common-problems.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.