Trying to test an existing and new cloud workers in the new workers dashboard, as we recently started receiving 522 Timeouts when deployed on a route.
Edits were done both ways – locally tested and deployed to workers.dev subdomains using wrangler CLI, as well as directly from the dashboard (https://dash.cloudflare.com/)
Waited 1+ hour relying on wrangler documentation referral to the initial wait time .
pushing a new workers.dev Worker project you may initially see 523 errors. Do not fear! The DNS is
propagating and can take a few seconds. It should work after a minute or so.
After about an hour of 523 Origin was still unreachable with the error switching to 522 Timeout
Error 522 Ray ID: 536a640d42c9cf04 • 2019-11-16 15:10:23 UTC
Some new/additional info:
The workers are fully functional when tested on the dashboard (https://dash.cloudflare.com/), timeout (after 20 mins) occurs when tested externally via curl/Postman, and only in cases where the POST request contains data:
Error 1105 Ray ID: 537436e24bc1cedc • 2019-11-17 20:07:14 UTC
You’ve requested a page on a website (our_domain) that is on the Cloudflare network. The page could not be rendered due to a temporary fault.
Cloudflare Ray ID: 537436e24bc1cedc • Your IP: xxx.xxx.xxx.xxx• Performance & security by Cloudflare
Any help/recommendation/tip will be greatly appreciated!