Error Code 1003 (HTTP status 403) with HTTP Service Bindings API calls including db connection

We're experiencing frequent NeonDbError: Server error (HTTP status 403): error code: 1003 errors. - Error message shows "NeonDbError" but we suspect this is actually Cloudflare's error code 1003, not a Neon-originated error - Neon Support confirmed: Database was operating normally during error timestamps, no 403 errors logged at database layer
- Error code 1003 is documented by Cloudflare as "Direct IP Access Not Allowed" https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1003/ - Errors occur primarily during OpenNext cache revalidation processes - Same error occurs whether using Cloudflare RPC or HTTP Service Bindings for API communication Technical architecture: - Frontend: Next.js app deployed via OpenNext on Cloudflare Workers - Backend: Hono API running on Cloudflare Workers - Database: Neon serverless driver (drizzle-orm/neon-http) - Communication: Frontend → Backend API calls use HTTP Service Bindings - Note: We are NOT using Hyperdrive Based on the 1003 error, could it be that when Cloudflare Workers communicate with Neon, the fetch requests get optimized by Cloudflare and end up using direct IP addresses instead of domain names? Or are there other potential causes? Any troubleshooting tips would be greatly appreciated.
Cloudflare Docs
Error 1003
This error indicates that direct access to a Cloudflare IP address is not allowed.
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?