> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/jet-bridge-deployment/on-premise/service-health-check.md).

# Service Health Check

{% hint style="info" %}
**Note:** Replace placeholders such as `COMMON_BACKEND_URL`, `COMMON_BACKEND_NODE_URL`, etc., with the actual URLs specific to your environment.
{% endhint %}

* In case of any errors or unexpected responses, look at the service logs for further troubleshooting steps.
  1. **Backend Service:**
     * URL: `COMMON_BACKEND_URL/api/check_health/`
  2. **Backend Node Service:**
     * URL: `COMMON_BACKEND_NODE_URL/check_health/`
  3. **Data Sync Service:**
     * URL: `COMMON_DATA_SYNC_URL/check_health/`
  4. **Workflows Service:**
     * URL: `COMMON_WORKFLOWS_URL/check_health/`
  5. **Data Sources API:**
     * URL: `COMMON_DATA_SOURCES_API_URL/check_health/`
  6. **Jet Bridge Cloud Service:**\
     Please note that JetBridge health check does not have a specific method. When accessing the service, it will redirect, and the output will resemble the information shown in the screenshot.

     * URL: `COMMON_JET_BRIDGE_CLOUD_URL/api/`

     <div data-full-width="true"><figure><img src="/files/lmOFJvhkL220VfWHlXMi" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
URLs should be similar to the URLs in your .env file. You can access the .env file by navigating to the "jet-onpremise" directory and opening it with the Nano text editor using the following commands:

```bash
cd jet-onpremise
nano .env
```

{% endhint %}

A successful response typically indicates details (healthy true/false, version) in the response body.


---

# 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.jetadmin.io/jet-bridge-deployment/on-premise/service-health-check.md?ask=<question>&goal=<endgoal>
```

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