Cannot Connect to NeonDB from Docker/Prisma (ARM64, SNI, All Best Practices Followed)
Hello Neon Support,
I am unable to connect to my NeonDB instance from a Dockerized Python/Prisma application, despite following all best practices and Neon documentation for SNI and ARM64 support.
Details:
NeonDB Endpoint:
ep-royal-wave-a2w289mf-pooler.eu-central-1.aws.neon.tech:5432
Connection String:
postgresql://aisaaslp_owner:***@ep-royal-wave-a2w289mf-pooler.eu-central-1.aws.neon.tech/aisaaslp?sslmode=require&options=endpoint%3Dep-royal-wave-a2w289mf
Error:
Can't reach database server at
Prisma connect attempt 1 failed: Could not connect to the query engine
All Prisma connect attempts failed.
Prisma Error Code:
P1001: Can't reach database server
Environment:
Docker container running on Apple Silicon (M1/M2, ARM64)
Prisma Python client with binaryTargets = ["native", "debian-openssl-3.0.x", "linux-musl-openssl-3.0.x", "linux-arm64-openssl-3.0.x"]
CA certificates present in the container
Outbound internet access confirmed
SNI endpoint option present in connection string
Prisma client regenerated after updating binary targets
What I’ve Tried:
Verified SNI option in connection string per Neon Docs
Added ARM64 support to Prisma binary targets and regenerated the client
Confirmed CA certificates and outbound internet in the container
No custom Docker network/firewall restrictions
Checked Neon status page for incidents
Retried connection after waking up compute in the Neon dashboard
Request:
Can you confirm if there are any Neon-side restrictions (IP allowlist, firewall, etc.) that could block this connection?
Is there any known issue with ARM64 Docker/Prisma clients and NeonDB?
Is my endpoint or project in a suspended or restricted state?
Any additional diagnostics you recommend?
Thank you for your help!
I am unable to connect to my NeonDB instance from a Dockerized Python/Prisma application, despite following all best practices and Neon documentation for SNI and ARM64 support.
Details:
NeonDB Endpoint:
ep-royal-wave-a2w289mf-pooler.eu-central-1.aws.neon.tech:5432
Connection String:
postgresql://aisaaslp_owner:***@ep-royal-wave-a2w289mf-pooler.eu-central-1.aws.neon.tech/aisaaslp?sslmode=require&options=endpoint%3Dep-royal-wave-a2w289mf
Error:
Can't reach database server at
ep-royal-wave-a2w289mf-pooler.eu-central-1.aws.neon.tech:5432Prisma connect attempt 1 failed: Could not connect to the query engine
All Prisma connect attempts failed.
Prisma Error Code:
P1001: Can't reach database server
Environment:
Docker container running on Apple Silicon (M1/M2, ARM64)
Prisma Python client with binaryTargets = ["native", "debian-openssl-3.0.x", "linux-musl-openssl-3.0.x", "linux-arm64-openssl-3.0.x"]
CA certificates present in the container
Outbound internet access confirmed
SNI endpoint option present in connection string
Prisma client regenerated after updating binary targets
What I’ve Tried:
Verified SNI option in connection string per Neon Docs
Added ARM64 support to Prisma binary targets and regenerated the client
Confirmed CA certificates and outbound internet in the container
No custom Docker network/firewall restrictions
Checked Neon status page for incidents
Retried connection after waking up compute in the Neon dashboard
Request:
Can you confirm if there are any Neon-side restrictions (IP allowlist, firewall, etc.) that could block this connection?
Is there any known issue with ARM64 Docker/Prisma clients and NeonDB?
Is my endpoint or project in a suspended or restricted state?
Any additional diagnostics you recommend?
Thank you for your help!
