Neon "The Endpoint ID Is Not Specified" / Password Authentication Failed
Workaround available psql, libpq apps, Go Updated November 14, 2026Based on 2 user reportsHow we research
Quick answer
Your client does not send SNI. Upgrade libpq to 14 or newer, or add options=endpoint%3D<endpoint-id> to the connection string.
Most likely fix: Re-copy the connection details
How to fix it
Try these in order — the most common fix is first.
1. Re-copy the connection details
- Compare user, password, host and database with the Connect modal
Did this fix it?2. Pass the endpoint ID
- Add options=endpoint%3D<endpoint-id> to the connection string
- Or upgrade libpq / psql to version 14+
Did this fix it?3. Go drivers
- Set sslmode=verify-full for pgx or lib/pq
Did this fix it?
Symptoms
'The endpoint ID is not specified' or 'password authentication failed for user' even though the password is right.
Why it happens
- Old libpq (below 14) or driver without SNI support
- Wrong user, password, host or database copied
This guide also covers
- neon endpoint id is not specified
- neon password authentication failed
- neon sni
Still not working?
If Neon keeps failing, you're not alone. See every Neon problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usOther Neon errors
- Neon Connection Timeout After Scale to Zero (Cold Start)
- Neon "Remaining Connection Slots Are Reserved" (Too Many Connections)
- Neon Compute Time Quota Exceeded (Free Plan Limit Reached)
- Neon Free Plan Storage Limit Reached (Writes Blocked)
- Neon Cannot Create Branch: Branch Limit Reached
- Neon Prisma or Drizzle Migration Fails (Pooled Connection)
- Neon SSL Required Error (Connection Is Insecure)
- Neon "Active Endpoints Limit Exceeded" / Compute Suspended