Error Code 1003 (HTTP status 403) with HTTP Service Bindings API calls including db connection
We're experiencing frequent
- 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.
NeonDbError: Server error (HTTP status 403): error code: 1003- 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.
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Similar Threads
Was this page helpful?
