Does wrangler dev proxy all network requests when using --remote?
I have a split DB interface. When local, my worker will open a connection to locally running Postgres (host: 127.0.0.1). When deployed, it uses a hosted DB. Everything works until I want to use proxied cloudflare services using with
wrangler dev --remote. My Postgres connection locally fails to connect with the error: message: proxy request failed, cannot connect to the specified address. As soon as I turn off --remote, things work again (but I obviously can't hit any remote cloudflare worker services).
Is this intended/intentional? How could I avoid this, if at all possible?1 Reply
Ah, well that explains it. I thought it was just the bound services specified inside wrangler.toml.