---
title: Troubleshooting
url: https://www.tines.com/docs/self-hosted/troubleshooting/
updated: 2026-07-16T15:36:17+00:00
---

*[tines.com](https://www.tines.com/llms.txt) › [Docs](https://www.tines.com/docs/llms.txt) › [Self-Hosted](https://www.tines.com/llm/docs/self-hosted.md)*

# Troubleshooting

*[View on tines.com](https://www.tines.com/docs/self-hosted/troubleshooting/)*

Use this page to find the right diagnostic steps for your self-hosted Tines deployment. Start with the in-app tools that work on every deployed platform, then follow the guide for how you deployed Tines to collect logs and configuration details.

## Before you contact support

Include as much of the following as you can in your support request:

- **What is happening** — symptoms, error messages, and when the issue started
- **What changed recently** — upgrades, configuration changes, network or infrastructure changes
- **Tines version** — application version; for Kubernetes, also include the Helm chart version
- **Deployment platform** — for example Docker Compose on a VM, Amazon EKS, Google Kubernetes Engine (GKE), or AWS Fargate.
- **Deployment Architecture** 
  
  - **Container Instances:** How many instances of each Tines container are currently running in the deployment?
  - **Database Architecture:** Is the database hosted externally, or does it run internally within your deployment platform?
  - **Resource Allocation:** What are the specific CPU and memory allocations designated for your containers?
- **HAR file **— ** **HTTP requests from your web browser. [See Generate a HAR file for troubleshooting](https://explained.tines.com/en/articles/8397915-generate-a-har-file-for-troubleshooting)
- **Steps you already tried** — restarts, health checks, and any diagnostic output you collected

Review all output before you share it. Logs and diagnostic bundles can contain passwords, tokens, or other sensitive data.

## Start here: in-app diagnostics

These tools work regardless of how you host Tines.

### System diagnostics

If you are on Tines v41.1 or later, open **Settings → Self-hosted → System diagnostics** to run health checks and debug tools from inside the application. 

See [System diagnostics](https://www.tines.com/docs/self-hosted/troubleshooting/system-diagnostics/) for full instructions.

### Tenant health dashboard

Admins can open **Tenant health** in the main navigation for a live view of container versions, database and Redis health, and background job queues. Use this to spot version mismatches, connectivity problems, or stuck jobs before you dig into logs.

See [Tenant health dashboard](https://www.tines.com/docs/self-hosted/monitoring-tines/tenant-health-dashboard/).

## Collect diagnostics by platform

Choose the guide that matches how you deployed Tines.

### Docker Compose

Use this path if you installed Tines with Docker Compose on a virtual machine or bare-metal host.

See [Troubleshooting Docker Compose](https://www.tines.com/docs/self-hosted/troubleshooting/troubleshooting-tines-on-docker-compose/) for troubleshooting scripts, restart steps, log collection, and what to send support.

### Kubernetes

Use this path if you deployed Tines with Helm on a Kubernetes cluster (for example EKS, GKE, AKS, or OpenShift).

See [Troubleshooting Kubernetes](https://www.tines.com/docs/self-hosted/troubleshooting/troubleshooting-kubernetes/) for the diagnostics collector, what is collected, and manual collection commands.

### AWS Fargate

Use this path if you deployed Tines on Amazon ECS with Fargate.

See [Troubleshooting AWS Fargate](https://www.tines.com/docs/self-hosted/troubleshooting/troubleshooting-aws-fargate-deployments/) for networking checks, common symptoms, and links to [log collection](https://www.tines.com/docs/self-hosted/troubleshooting/troubleshooting-aws-fargate-deployments/log-collection-on-aws-fargate/) and [restarting services](https://www.tines.com/docs/self-hosted/troubleshooting/troubleshooting-aws-fargate-deployments/restarting-tines-on-aws-fargate/).

### Other container platforms

1. Run **System diagnostics** and review the **Tenant health** dashboard.
2. Collect logs from your application and worker containers using your orchestrator's standard log tools.
3. Include your Tines version, platform name, and a description of the issue when you contact support.

See [Before you begin](https://www.tines.com/docs/self-hosted/) for compatible environments.