CD
Cloudflare Developers•2mo ago
max

Error: proxy request failed, cannot connect to the specified address

I'm trying to get to the bottom of some intermittent errors I'm seeing. When connecting to postgres (supabase via postgres.js) from a worker, I'm getting occasional errors of the form: Error: proxy request failed, cannot connect to the specified address I'm connecting directly to the supabase PGBouncer, not via Hyperdrive (we saw this happen more often when we used Hyperdrive). It has plenty of available connections. The docs (https://developers.cloudflare.com/workers/runtime-apis/tcp-sockets/#proxy-request-failed-cannot-connect-to-the-specified-address) state: 
Your socket is connecting to an address that was disallowed. Examples of a disallowed address include Cloudflare IPs, localhost, and private network IPs.

If you need to connect to addresses on port 80 or 443 to make HTTP requests, use fetch.
Your socket is connecting to an address that was disallowed. Examples of a disallowed address include Cloudflare IPs, localhost, and private network IPs.

If you need to connect to addresses on port 80 or 443 to make HTTP requests, use fetch.
But if the address were somehow disallowed, I don't understand (may just be me being dumb) why this would only happen some of the time. And the example reasons for being disallowed above don't apply to the AWS IPs supabase uses.
Cloudflare Docs
TCP sockets
Use the connect() API to create outbound TCP connections from Workers.
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?