Connection Errors – Neon Docs

[ad_1]

This topic describes how to resolve connection errors you may encounter while using Neon. Covered errors include:

Endpoint ID is not specified

With older clients and some native PostgreSQL clients, you may get the following error when trying to connect to Neon:

ERROR: Endpoint ID is not specified. Update the PostgreSQL client library (libpq) for SNI support or pass the endpoint ID (the first part of the domain name) as a parameter: ‘&options=endpoint%3D’. See [https://neon.tech/sni](https://neon.tech/sni) for more information.

This error occurs if the client library or application does not support the Server Name Indication (SNI) mechanism in TLS.

Neon uses compute endpoint IDs (the first part of a Neon domain name) to route incoming connections. However, the PostgreSQL wire protocol does not transfer domain name information, so Neon relies on the Server Name Indication (SNI) extension of the TLS protocol to do this.

SNI support was added to libpq (the official PostgreSQL client library) in version 14, which was released in September 2021. Clients using your system’s libpq library should work if your libpq version is >= 14 On Linux and macOS, you can check your libpq version by running pg_config –version. On Windows, check the version of libpq.dll in the bin directory of your PostgreSQL installation. Right click on the file, select Properties > Details.

If updating a library or application doesn’t help, there are several workarounds, described below, to provide the required domain name information when connecting to Neon.

A. Broadcast the endpoint ID as an option

Neon supports a connection option called endpoint, which you can use to identify the compute endpoint you’re connecting to. Specifically, you can add options=endpoint%3Dep-mute-recipe-123456 as a parameter to the connection string, as shown in the following example. %3D is a URL-encoded = sign.

postgres://:@ep-mute-recipe-123456.us-east-2.aws.neon.tech/neondb?options=endpoint%3Dep-mute-recipe-123456 note

The endpoint connection option was previously called project. The project option is deprecated but remains supported for backward compatibility.

The endpoint option works if the application or library allows it to be set. Not all of them do, especially in the case of GUI applications.

B. Use the syntax libpq key=value in the database field

If your application or client is based on libpq but you cannot update the library, such as when the library is compiled into an application, you can take advantage of the fact that libpq allows adding options to the database name. Therefore, in addition to the database name, you can specify the endpoint option, as shown below. Substitute with your computer’s endpoint ID, which you can find in the Neon connection string. It looks like this: ep-mute-recipe-123456.

dbname=neondb options=endpoint=
C. Set up full verification for golang based clients

If your application or service uses Golang PostgreSQL clients such as pgx and lib/pg, you can set sslmode=verify-full, which causes SNI information to be sent when you connect. Most likely, this behavior is not intended but occurs inadvertently due to the design of the golang TLS library API.

D. Specify the ID of the endpoint in the password field

As a last resort, you can try specifying the endpoint ID in the password field. So instead of just specifying your password, provide a string consisting of the endpoint option and the password, as shown. Substitute with your computer’s endpoint ID, which you can find in the Neon connection string. It looks like this: ep-mute-recipe-123456.

final point=;

This approach is the least secure of the recommended workarounds. Causes the authentication method to be downgraded from scram-sha-256 (never transfer a plain text password) to password (transfer a plain text password). However, the connection is still encrypted with TLS, so the level of security is equivalent to that provided by https websites. We intend to deprecate this option when most libraries and applications provide SNI support.

Libraries

Clients in the driver list on the PostgreSQL community wiki that use your system’s libpq library should work if your libpq version is >= 14.

Neon has tested the following drivers for SNI support:

DriverLanguageSNI SupportNotesnpgsqlC#PostgrexElixirRequires ssl_opts with server_name_indicationgithub.com/lib/pqGoSupported with macOS Build 436, Windows Build 202 and Ubuntu 20, 21 and 22pgxGoSNI support merged v5.0.0-beta.3 yetgo-pgGoRequires full test modeJDBCJavanode -postgresJavaScript Requires ssl : {‘sslmode’: ‘require’} optionpostgres.jsJavaScriptRequires ssl: ‘require’ optionasyncpgPythonpg8000PythonRequires scramp >= v1.4.3, which is included in pg8000 v1.29.3 and later PostgresClientKitSwiftPostgresNIOSwiftpostgresql-clientTypeScript Authentic Password tion failed for user

The following error is often the result of incorrectly defined connection information or the driver being used does not support Server Name Indication (SNI).

ERROR: Password authentication failed for user ‘‘ failed to connect to server at ‘ep-billowing-fun-123456.us-west-2.aws.neon.tech’ (12.345.67.89), port 5432: ERROR: connection is not secure (try using `sslmode= require`)

Check your connection to see if it is defined correctly. Your Neon connection string can be obtained from the Connection Details widget on the Neon Dashboard. It looks similar to this:

postgres://daniel:[email protected]/neondb

For clients or applications that require you to specify connection parameters such as user, password, and hostname separately, the values ​​in a Neon connection string are as follows:

User: daniel Password: f74wh99w398H Hostname: ep-white-morning-123456.us-east-2.aws.neon.tech Port number: 5432 (Neon uses the default PostgreSQL port, 5432, and is therefore not included in the connection) Database name: neondb (neondb is the default database created with every Neon project. Your database name may be different.)

If you believe the connection string is defined correctly, see the SNI support instructions described in the previous section: Endpoint ID is not specified.

Unable to reach the database server

This error sometimes occurs when using Prisma Client with Neon.

Error: P1001: Unable to reach database server on `ep-white-thunder-826300.us-east-2.aws.neon.tech`:`5432` Make sure database server is running on `ep-white – thunder-826300.us-east-2.aws.neon.tech`:`5432`.

A compute node in Neon has two main states: active and inactive. Active means that PostgreSQL is currently running. If there are no active queries for 5 minutes, activity monitoring normally puts the compute node into an idle state to conserve power and resources.

When you connect to an idle computer, Neon turns it on automatically. Activation usually occurs within a few seconds. If the above error is reported, it most likely means that the Prisma query engine timed out before your Neon computer was activated. To handle this connection timeout scenario, refer to the connection timeout instructions in our Prisma documentation. Our connection latency and timeout documentation can also help you solve this problem.

Undefined error: database error

This error sometimes occurs when using Prisma Migrate with Neon.

Undefined error: database error Error querying database: db error: ERROR: Prepared statement ‘s0’ already exists

Prisma Migrate requires a direct connection to the database. It does not support a pooled connection with PgBouncer, which is the connection pool used by Neon. Attempting to run Prisma Migrate commands, such as prisma migrate dev, with a pooled connection causes this error. To fix this, refer to our Prisma Migrate with PgBouncer instructions.

I need help?

Send a request to [email protected] or join the Neon community forum.

[ad_2]