Common symptoms
Diagnosing in detail
My signature check always fails
My signature check always fails
In order of likelihood:
- You are hashing the wrong bytes. JSON middleware parses and discards the raw body. Hash the raw bytes exactly as received, before anything parses them.
- Your secret is stale. Rotating invalidates the previous secret immediately, with no overlap. Copy the current value from the settings page.
- You are hashing the
Timestampheader too. It is not part of the signature. - Encoding mismatch. The signature is lowercase hex, not base64.
Deliveries fail with no HTTP status
Deliveries fail with no HTTP status
No status code means Edplay never got a response. Check that:
- the URL is publicly reachable, not
localhostor a private IP range; - the TLS certificate is valid, unexpired, and publicly trusted, since self-signed certificates fail;
- your firewall is not blocking Edplay’s servers;
- your endpoint responds within 3 seconds.
I am missing events
I am missing events
Events are dropped, not queued, in these cases:
- Deliveries active was off when the event happened.
- All three delivery attempts failed. Edplay does not redeliver afterwards.
- The event type is not selected under Events.
I receive the same event more than once
I receive the same event more than once
This is expected. A retry can deliver an event you already processed, for example when you returned
200 just after the 3-second limit. course.progress_updated also fires repeatedly by design.Deduplicate on user.id plus course.id plus occurred_at, or make your write naturally idempotent.