Daemon Issues

Troubleshooting issues getting the Scanopy daemon running.

Issues getting the daemon connected and running. For problems that occur during scans, see Scanning Issues.

Daemon Not Connecting to Server

Symptoms: Daemon shows as offline in the UI, or logs show connection errors

Diagnosis:

# Check daemon logs
docker logs scanopy-daemon

# Test connectivity to server
curl https://your-server-url/api/health

Solutions:

Verify server URL: Ensure SCANOPY_SERVER_URL is correct and reachable from the daemon host
Check API key: Verify the API key is valid and not expired in Platform > API Keys
Firewall rules: Ensure outbound HTTPS (port 443) is allowed from the daemon host

Symptoms: "Permission denied" when accessing Docker socket

Solution: Add user to docker group:

sudo usermod -aG docker $USER
newgrp docker

Log out and back in for changes to take effect.

If you're using a Docker socket proxy and getting permission errors, see Securing Docker Discovery with a Socket Proxy — Troubleshooting.

Symptoms: Daemon runs in foreground and stops when SSH session ends

Solution: Install as a systemd service (see Managing Daemons), or run with a process manager like screen or tmux.

If your issue isn't covered here: