Postgres error in NodeJS: Cannot resolve address - ENOTFOUND

Question

Postgres error in NodeJS: Cannot resolve address - ENOTFOUND

My connection string for accessing my AWS database is

pg://user:pass@localhost:port/table

. It works perfectly fine when connecting to localhost, but as soon as I attempt to connect to the AWS server, everything falls apart.

Even a simple connection code results in an error message. The name of the database is 'people' and it's running on port 8080, but despite declaring the correct port number in the conString, the error message shows 5432 instead.

Error: getaddrinfo ENOTFOUND people people:5432 at errnoException (dns.js:26:10) at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:77:26)

Below is the code snippet I've been using:

var pg = require("pg");

var conString = "pg://someuser:pass@db-endpoint:8080/postgres";
var client = new pg.Client(conString);
client.connect();

javascript postgresql express

Answer 1

Answer №1

If you are confident that your connection string is properly formatted as described by gnerkus, the final thing to investigate is your password. If it contains non-alphanumeric characters, that could be the source of the problem. It appears that either Node.js or the inner workings of JavaScript itself may be causing this issue (although I cannot confirm this as pg-admin connects fine using my original password).

My password contained special characters such as '+' and '/' (generated by creating a lengthy JSON filled with random text and then hashing it to produce a base64 string). When I removed these characters from both my connection string and database password, the issue was resolved.

Interestingly, the character '=' was actually acceptable. The problem seemed to stem from the URL decoding process on the database side. Sending '+' likely caused it to be replaced with a space, leading to an incorrect password. Meanwhile, the presence of '/' resulted in a malformed URL, triggering the "not found" error. Consider the following scenario:

postgres://username:sdkadady88da8+8ahdajd/ashdi==@localhost/database

The surplus '/' here causes the URL to break down incorrectly. As a result,

protocol:// user:pass@host / database

transforms into

protocol:// [malformed user:pass@host] / [malformed database name] / [some gibberish]

. This can be traced back to the additional '/'.

If your colleague accessing it via JSF has the ability to adjust their connection string, I recommend updating the password to one that satisfies both systems. Otherwise, consider setting up another user/account with identical permissions but a different password suitable for use with Node.js.

EDIT: Furthermore, based on suggestions from this discussion, attempting to encode the password section of your connection string might resolve the issue. Although I did not personally test this method after changing my own password, given that you continue experiencing difficulties, it would be wise to explore this solution prior to adopting one of the aforementioned approaches.

Answer 2

If you are confident that your connection string is properly formatted as described by gnerkus, the final thing to investigate is your password. If it contains non-alphanumeric characters, that could be the source of the problem. It appears that either Node.js or the inner workings of JavaScript itself may be causing this issue (although I cannot confirm this as pg-admin connects fine using my original password).

My password contained special characters such as '+' and '/' (generated by creating a lengthy JSON filled with random text and then hashing it to produce a base64 string). When I removed these characters from both my connection string and database password, the issue was resolved.

Interestingly, the character '=' was actually acceptable. The problem seemed to stem from the URL decoding process on the database side. Sending '+' likely caused it to be replaced with a space, leading to an incorrect password. Meanwhile, the presence of '/' resulted in a malformed URL, triggering the "not found" error. Consider the following scenario:

postgres://username:sdkadady88da8+8ahdajd/ashdi==@localhost/database

The surplus '/' here causes the URL to break down incorrectly. As a result,

protocol:// user:pass@host / database

transforms into

protocol:// [malformed user:pass@host] / [malformed database name] / [some gibberish]

. This can be traced back to the additional '/'.

If your colleague accessing it via JSF has the ability to adjust their connection string, I recommend updating the password to one that satisfies both systems. Otherwise, consider setting up another user/account with identical permissions but a different password suitable for use with Node.js.

EDIT: Furthermore, based on suggestions from this discussion, attempting to encode the password section of your connection string might resolve the issue. Although I did not personally test this method after changing my own password, given that you continue experiencing difficulties, it would be wise to explore this solution prior to adopting one of the aforementioned approaches.

Answer 3

Answer №2

During my recent project, I encountered an issue while trying to establish a database connection within a docker container. The problem stemmed from using the incorrect DB_HOST value - I mistakenly entered the docker service name instead of 'localhost'.

Fortunately, once I corrected the DB_HOST setting, the issue was quickly resolved.

Erroneous .env configuration: DB_HOST=postgres

Corrected .env configuration: DB_HOST=localhost

Answer 4

During my recent project, I encountered an issue while trying to establish a database connection within a docker container. The problem stemmed from using the incorrect DB_HOST value - I mistakenly entered the docker service name instead of 'localhost'.

Fortunately, once I corrected the DB_HOST setting, the issue was quickly resolved.

Erroneous .env configuration: DB_HOST=postgres

Corrected .env configuration: DB_HOST=localhost

Answer 5

Answer №3

Encrypting your password for security.

let encryptedPassword = `${encodeURIComponent(database.dbPassword)}@`;

Answer 6

Encrypting your password for security.

let encryptedPassword = `${encodeURIComponent(database.dbPassword)}@`;

Answer 7

Answer №4

By default, the port used for connecting to a Postgres database is usually 5432. This means that the Postgres database running on AWS is most likely using this port as well. When creating your connection string, make sure it follows this structure:

var conString = "postgres://username:password@localhost/database";

This format is outlined in the node-postgres documentation. Therefore, you must modify your connection string to the following:

var conString = "postgres://someuser:pass@db-endpoint:5432/people";

Answer 8

By default, the port used for connecting to a Postgres database is usually 5432. This means that the Postgres database running on AWS is most likely using this port as well. When creating your connection string, make sure it follows this structure:

var conString = "postgres://username:password@localhost/database";

This format is outlined in the node-postgres documentation. Therefore, you must modify your connection string to the following:

var conString = "postgres://someuser:pass@db-endpoint:5432/people";

Answer 9

Answer №5

If anyone encounters this problem, I'll leave it here for reference

My mistake was using 127.0.0.1:5432 instead of just 127.0.0.1

Answer 10

If anyone encounters this problem, I'll leave it here for reference

My mistake was using 127.0.0.1:5432 instead of just 127.0.0.1

Answer 11

Answer №6

Ensure that your URL does not include the prefix http://

Answer 12

Ensure that your URL does not include the prefix http://

Answer 13

Answer №7

I recently discovered that my password was not accepting the dollar sign. After removing it, everything worked perfectly.

Answer 14

I recently discovered that my password was not accepting the dollar sign. After removing it, everything worked perfectly.

Answer 15

Answer №8

When providing the host to the pool class, ensure you write it as "address string" and not as "@address string." This small detail can make a big difference in how your code functions.

Answer 16

When providing the host to the pool class, ensure you write it as "address string" and not as "@address string." This small detail can make a big difference in how your code functions.

Answer 17

Answer №9

In my experience, I encountered an issue while trying to establish a connection to a PostgreSQL database hosted on AWS from an API deployed on Heroku using the pg npm package. The solution was to modify the PGHOST environmental variable by removing the 'https://' prefix from the URL link in order to connect successfully.

Answer 18

In my experience, I encountered an issue while trying to establish a connection to a PostgreSQL database hosted on AWS from an API deployed on Heroku using the pg npm package. The solution was to modify the PGHOST environmental variable by removing the 'https://' prefix from the URL link in order to connect successfully.

Answer 19

Answer №10

Most of the time, the issue lies with the password. It's best to use a straightforward combination of letters and numbers for security.

Answer 20

Most of the time, the issue lies with the password. It's best to use a straightforward combination of letters and numbers for security.

Answer 21

Answer №11

In a unique and unusual turn of events, I encountered an issue where my DATABASE_URL was set as an environment variable with double quotes around it in a .env file. The original line looked something like this: DATABASE_URL="pg://someuser:pass@db-endpoint:8080/postgres"

While this setup worked perfectly fine during local testing, it caused problems on my deployment platform (Netlify). The solution? Simply removing the double quotes from the DATABASE_URL in my Netlify environment variables: DATABASE_URL=pg://someuser:pass@db-endpoint:8080/postgres

The reason for the double quotes in the first place was that I copied this format directly from my cloud-hosted database at Cockroach Labs.

Answer 22

In a unique and unusual turn of events, I encountered an issue where my DATABASE_URL was set as an environment variable with double quotes around it in a .env file. The original line looked something like this: DATABASE_URL="pg://someuser:pass@db-endpoint:8080/postgres"

While this setup worked perfectly fine during local testing, it caused problems on my deployment platform (Netlify). The solution? Simply removing the double quotes from the DATABASE_URL in my Netlify environment variables: DATABASE_URL=pg://someuser:pass@db-endpoint:8080/postgres

The reason for the double quotes in the first place was that I copied this format directly from my cloud-hosted database at Cockroach Labs.

Postgres error in NodeJS: Cannot resolve address - ENOTFOUND

Answer №1

Answer №2

Answer №3

Answer №4

Answer №5

Answer №6

Answer №7

Answer №8

Answer №9

Answer №10

Answer №11

Similar questions

Tips for utilizing the node package dotenv to interact with environment variables in a Red Hat OpenShift application during local development

What causes useEffect to trigger twice when an extra condition is included?

Developing a system mode called "night mode"

What is the reason behind the inconsistency of express session in creating cookies?

Tips for concealing navigation buttons during certain stages in react stepzilla

Choosing a particular 2D array based on another variable in jQuery and JavaScript

Looking for guidelines on Node, Express, and Jade styling?

Error: The function stripHtml cannot be found

A step-by-step guide on initializing and setting a cookie value with expiration

The function $(...) does not recognize tablesorter

AJAX allows developers to declare variables within their code to

Vue.js - Resetting child components upon array re-indexing

Changing the color of HTML text based on a variable in Vue JS can be achieved by altering the CSS styles dynamically

Performing multiple asynchronous operations on a set of data using node.js

my combination of express and socket.io run on separate ports

What causes the return of undefined when accessing an item from an object?

Retrieve the value of a CSS class property regardless of whether it is actively being utilized

Error: jQuery is unable to access the property 'xxx' because it is undefined

Deleting a row from a table in AngularJS can be accomplished by following these steps

When incorporating axios within an express route, it is causing the data field to display unusual characters instead of JSON