Troubleshooting

This guide helps users understand and resolve common LDAP (Lightweight Directory Access Protocol) connection or authentication errors encountered when integrating with Active Directory (AD) or other directory services. Each section provides a simplified, Message error message, its meaning, possible causes, and clear remediation steps.

Container exits immediately

docker logs zluri-partner-ldap-connector-v1.0.0

Common causes:

MYSQL_PASSWORD not set and no TTY available for the interactive prompt — pass it as an environment variable.
MySQL failed to start — check logs for [init] Waiting for MySQL.

"Connection refused" or "SSL handshake failed"

Confirm the container is running: docker ps
Confirm the port matches: docker port zluri-partner-ldap-connector-v1.0.0
Use -k with curl to bypass self-signed cert verification: curl -k https://HOST:PORT/api/health

Agent not connecting to Zluri

Verify the Installation Token hasn't expired (valid for 30 minutes).
Ensure outbound HTTPS is allowed from the Docker host to Zluri's servers.
Check the Logs section in the connector's Web UI sidebar for error details.

Directory Connection test fails

Verify the AD server hostname/IP is reachable from the Docker host: ping <AD_HOST>
Confirm the port is correct (389 for LDAP, 636 for LDAPS).
If using SSL/TLS, ensure the uploaded .pem certificate is valid and matches the AD server.
Double-check the Bind DN and password.

Reset everything and start fresh

docker compose down -v    # removes containers AND volumes
docker compose up -d      # starts fresh

Problems connecting? Feel free to submit a ticket or contact us directly at [email protected].

Updated about 2 hours ago