# 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="https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FF8C1SPh5vjszYc8ARO5a%2FScreenshot%202024-03-25%20at%2018.55.00.png?alt=media&#x26;token=6c590a07-2bde-4c8d-b399-1270cc801861" 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.