Skip to main content
This page contains fixes for some of the known installation and usage errors encountered when using Convoy across different platforms.
This can happen in older versions of Convoy and is a result of a bug where we register workers on a process that doesn’t also register the handler. What you can do is to update Convoy to a more recent version and run the retry command
terminal
# if you are using the binary
convoy retry --status="Scheduled" --time="1h"

# if you are using docker
docker run -d -p 5009:5009 --name retry -v `pwd`/convoy.json:/convoy.json your-convoy-image:tag retry --status="Processing" --time="1h"
Ensure that your Redis connection string is in the correct format and that you can connect to the instance using redis-cli from the same machine.
When creating or updating an endpoint, Convoy may call the URL to validate it (ping). If your server only accepts authenticated requests, returns 404 for GET, or is behind TLS that fails validation, the check can fail with errors such as endpoint validation failed: endpoint returned a non-2xx response.For controlled environments you can disable ping validation by setting CONVOY_DISPATCHER_SKIP_PING_VALIDATION=true (or the equivalent skip_ping_validation field in configuration). Prefer fixing the destination (e.g. health route, correct method) when possible; skipping validation reduces confidence that the URL is reachable as Convoy will call it during delivery.See Endpoint verification and outbound connections for how ping differs from TLS settings and the full dispatcher reference.
If you’re having any other issues, please reach out to us on Slack.