Dialing with this option {secureTransport: "starttls", allowHalfOpen: true}, and I'm sure the hostname is reachable around the world (maybe except China).
Local testing (wrangler 3.1.0 on macOS) is always successful, able to send and to receive the response, but the deployed CF Worker always respond with 500 without explicit error message.
To debug, I enable the log streaming from the remote server, and I can see the data sent from the worker (both local wrangler and alive worker), and I can confirm the data is processed successfully.
Anyone could exlpain the difference between wrangler worker and deployed worker in TCP connect behavior? How to solve this issue?