---
title: "Helpful Tips & Troubleshooting"
slug: "helpful-tips-troubleshooting"
updated: 2026-05-13T17:59:33Z
published: 2026-05-13T17:59:33Z
canonical: "help.claritysecurity.com/helpful-tips-troubleshooting"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.claritysecurity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Helpful Tips & Troubleshooting

Use this guide to manage your Clarity Connect environment, perform connectivity tests, and resolve common container issues.

**Container Stack Definitions**

- **clarityconnectmain:** The primary appliance container.
- **clarityconnectoracle:** Oracle-compatible version of the appliance.
- **redis:** Internal transaction and state database.
- **watchtower:** Automated update manager for the Clarity stack.

### Common Docker Management

Always run these commands from the directory containing your configuration file to ensure the correct stack is targeted.

```plaintext
# View running containers and health status
docker ps
```

```plaintext
# Stop the entire stack
docker-compose down
```

```plaintext
# Force a recreate/update of all containers
docker-compose up -d --force-recreate
```

### Network & Firewall Whitelisting

If you encounter **ECR** or **Network Timeout** errors, ensure your firewall permits outbound traffic to the following endpoints on port 443:

- https://your-tenant.claritysecurity.io
- https://auth.docker.io
- https://public.ecr.aws/d7a3o6p2
- https://production.cloudflare.docker.com/

### Advanced Connectivity Troubleshooting

When the host OS has connectivity but the application fails to sync, you must test from within the container environment.

#### Testing LDAP/AD Connectivity

```plaintext
# Enter the container shell
docker exec -it clarityconnectmain /bin/sh

# Install LDAP tools inside the container
apk add openldap-clients

# Run a search test (Replace values with your server info)
ldapsearch -x -H ldap://[SERVER-IP] -D "[BIND-DN]" -W -b "[SEARCH-BASE]"
```

#### Testing Port Access (Telnet)

Use this to verify if ports like 389, 636, or 1433 are being blocked by an internal firewall.

```plaintext
# Install telnet tools
apk add busybox-extras

# Attempt connection to server on port 389, 636, or 1433
busybox-extras telnet [IP-ADDRESS] [PORT]
```

> [!WARNING]
> **NOTE:** If the connection closes immediately after the telnet command, the remote server or an intermediate firewall is actively rejecting the request.

### Internal Diagnostics (Tinker)

The **Tinker** shell allows you to run internal application logic to verify configuration credentials.

```plaintext
# Open the internal shell
docker-compose exec clarityconnectmain php artisan tinker

# Inside tinker, test connection logic for a specific App ID
ADService::getConnection(YOUR_APP_ID)
```

### Log Inspection

If you are working with Clarity Support, you may be asked to provide a tail of the application logs to see detailed error stack traces. Check the Laravel logs for detailed error stack traces regarding connection attempts to Clarity Security.

```plaintext
# View live application logs
tail -f storage/logs/laravel-$(date +%Y-%m-%d).log
```