Skip to main content
Solved

Adobe Webhook URL Verification Failing With Error 604 For Cribl RAW HTTP Source

  • June 23, 2026
  • 4 replies
  • 0 views
A
This message originated from Cribl Community Slack.
Click here to view the original link.

Hi Team, Do we know if Adobe supports Cribl's RAW HTTP Source for webhook URL? Currently, Adobe's verification of the webhook URL is failing - we're seeing a 604 from Adobe's side although the uri path at the Cribl source is reachable & listening.

Best answer by mario

Hi @user , 604 status code is a request time out from what I have found. Looks like Adobe sends a CRC verification upfront. (Maybe you can confirm that) Cribl's Raw HTTP Source simply listens for incoming HTTP requests and creates events, it has no built-in logic to detect a challenge request and respond with the required CRC hash. Possible workarounds would be:
  • Reverse proxy / middleware — Place something like nginx or an AWS API Gateway + Lambda in front of Cribl that handles the CRC challenge, then forwards actual webhook payloads to the Cribl Raw HTTP Source.
  • External script — Run a lightweight HTTP server (e.g., Python/Flask) that handles the Adobe challenge/response and proxies real events to Cribl's Raw HTTP Source on the appropriate port.

4 replies

M
  • mario
  • Employee
  • Answer
  • June 23, 2026
Hi @user , 604 status code is a request time out from what I have found. Looks like Adobe sends a CRC verification upfront. (Maybe you can confirm that) Cribl's Raw HTTP Source simply listens for incoming HTTP requests and creates events, it has no built-in logic to detect a challenge request and respond with the required CRC hash. Possible workarounds would be:
  • Reverse proxy / middleware — Place something like nginx or an AWS API Gateway + Lambda in front of Cribl that handles the CRC challenge, then forwards actual webhook payloads to the Cribl Raw HTTP Source.
  • External script — Run a lightweight HTTP server (e.g., Python/Flask) that handles the Adobe challenge/response and proxies real events to Cribl's Raw HTTP Source on the appropriate port.
A
@user Thank you for the confirmation & suggestions! AI did suggest using a Cribl pipeline but not sure what the logic was there since there's no workaround for the CRC verification from Cribl.
M
  • mario
  • Employee
  • June 23, 2026
Pipelines apply after a data flow is established, with the failing CRC challenge we are not at this point yet.
A
Makes sense, thanks Mario!
Terms & ConditionsAccessibility statement