DrandConnectionFailure
Error v216 → current 26.2The offchain worker failed to connect to the Drand beacon API.
Why This Error Exists
Offchain workers fetch Drand pulses from external HTTP APIs. If the connection fails, no new randomness can be submitted. This is a network/infrastructure issue, not a cryptographic or logic error.
Deep Dive
The offchain worker makes HTTP requests to Drand endpoints (like api.drand.sh). Connection failures can be timeouts, DNS failures, TLS issues, or network outages. The error prevents pulse submission until connectivity is restored.
Debugging Example
Offchain worker logs show 'DrandConnectionFailure'. Try from the server: curl -v https://api.drand.sh/public/latest. If that fails, it's a network issue. Check firewall, DNS, and network routes.
Prevention Tips
- Monitor network connectivity to Drand endpoints
- Set up alerts for failed pulse submissions
- Consider multiple Drand endpoint fallbacks
- Run a local Drand relay for lower latency and better reliability
From Chain Metadata
failed to connect to the
What This Means
The offchain worker failed to connect to the Drand beacon API.
Common Causes
- Network connectivity issues to Drand endpoints
- Drand beacon API is down or unreachable
- Firewall or DNS issues blocking outbound HTTP
- HTTP timeout exceeded (check HttpFetchTimeout constant)
How to Fix
- Check network connectivity from the validator node
- Verify Drand endpoints are accessible: curl https://api.drand.sh/public/latest
- Check if firewall rules allow outbound HTTPS
- Consider running a local Drand relay for better reliability
Runtime Info
- Pallet Index
- 26
- Error Index
- 2
- Error Code
- 26.2
- Runtime Version
- v393