Troubleshooting

These checks assume Pailot is already installed. If the platform is not running, contact the vendor — do not follow public install guides for other products.

Database connection failed

docker compose ps db
docker compose exec db psql -U postgres -c "SELECT 1"

Confirm DATABASE_URL is postgresql://user:pass@host:5432/database and matches the delivery.

Ollama models not showing

Inside Docker, localhost is the container, not the host.

# Ollama on the Docker host
OLLAMA_URL=http://host.docker.internal:11434
# Linux host — use the real address
OLLAMA_URL=http://192.168.1.x:11434

WebSocket / realtime not working

1. NEXT_PUBLIC_SOCKET_URL must match the public hostname
2. Confirm the realtime service is up (docker compose ps or kubectl get pods)
3. The reverse proxy must pass WebSocket upgrades — see Docker

502 Bad Gateway

docker compose ps
docker compose logs

Common causes: the app container is restarting, the database is not ready, or the host is out of memory. Service names are in the delivery compose file.

Migration errors

docker compose logs migrations

Do not invent a migrate command. Use the one in the runbook (the application image and working directory are delivery-specific).

pgvector not found

Postgres must be an image that includes pgvector (for example pgvector/pgvector:pg17), not a stock postgres:17 without the extension.

Certificate errors

If outbound HTTPS to a provider fails with an expired CA bundle, update CA certificates inside the application container using the package manager the image ships, or ask the vendor to rebuild the image. Do not set NODE_TLS_REJECT_UNAUTHORIZED=0 in production.

Blank page after login

1. Browser console for mixed-content or WebSocket errors
2. NEXT_PUBLIC_APP_URL must match the URL you open
3. Clear site cookies and local storage
4. Confirm every service in the compose file is running

Windows operator notes

If you build or run tooling on Windows, prefer WSL2. Line endings should stay LF (core.autocrlf=input) so scripts from the delivery do not break.

Logs

docker compose logs -f

Follow a single service by the name in the delivery file, not by a name copied from a public tutorial.

Getting help

Contact the vendor: pailot.ru (access form) or the engineer named in your delivery. There is no public issue tracker for the product.