Daemon Connectivity Issues

Troubleshoot when the daemon cannot reach the control plane.

Last updated:

Daemon Connectivity Issues

The daemon communicates with the control plane over outbound HTTPS (port 443).

Common Causes

  1. Firewall blocking outbound HTTPS - Ensure the host can reach https://lockwave.io on port 443
  2. Proxy configuration - If behind a proxy, set HTTPS_PROXY in the daemon environment
  3. DNS resolution - Verify lockwave.io resolves correctly from the host
  4. TLS issues - Ensure the system CA certificates are up to date

Diagnosis

# Test connectivity
curl -v https://lockwave.io/up

# Check daemon logs
journalctl -u lockwaved -f

# Check daemon status
systemctl status lockwaved

Still Stuck?

Contact us at support@lockwave.io with your daemon logs.

Back to Troubleshooting Still need help?