Just Learn Code

Troubleshooting getaddrinfo ENOTFOUND: Common Causes and Solutions

Troubleshooting the “getaddrinfo ENOTFOUND” Error

Have you ever encountered the “getaddrinfo ENOTFOUND” error while making an HTTP request? This error can be frustrating, especially when you’re trying to build or test a web application.

This error typically means that the DNS server cannot resolve the requested hostname, which can have several possible reasons. In this article, we will cover some of the common reasons for this error and how to troubleshoot them.

Reasons for the Error

The “getaddrinfo ENOTFOUND” error can occur for several reasons, including:

Incorrect URL: One of the most common reasons for this error is an incorrect URL. It can be caused due to misspelling the URL or including a special character in the URL.

Don’t specify protocol in host property: When using the `http.get()` or `https.get()` method in Node.js, make sure you don’t specify the protocol (HTTP or HTTPS) in the host property. Server accessibility: When the server is down or inaccessible, it can cause the “getaddrinfo ENOTFOUND” error.

To check whether the server is accessible, you can try to ping the server from the command line. Resolve environment variables in URL: If you’re using environment variables in the URL, make sure to resolve these variables before making an HTTP request.

This can be done using tools like Postman. Ensure correct protocol: Check whether the URL is requesting the correct protocol scheme.

For example, if the server is using a secure protocol, make sure to request the HTTPS protocol. Configure /etc/hosts file: If you’re working with a local host, make sure to configure the `/etc/hosts` file properly.

The `/etc/hosts` file maps domain names to IP addresses and can sometimes cause the “getaddrinfo ENOTFOUND” error when configured incorrectly. Troubleshooting MongoDB connection errors: When working with MongoDB, connection errors can be caused due to issues with the hostname, connection string, or even DNS propagation.

Make sure to double-check these settings before making any HTTP requests. Remove or configure proxy settings: If you’re using a proxy, it may be causing the “getaddrinfo ENOTFOUND” error.

Make sure to remove or configure the proxy settings accordingly, especially when using a tool like NPM install.

Additional Resources

There are numerous tutorials and resources available online to help you with troubleshooting the “getaddrinfo ENOTFOUND” error. A quick internet search will yield multiple results that can help you delve deeper into this error and its possible solutions.

Red Hat has a troubleshooting guide for “Name resolution errors including `getaddrinfo ENOTFOUND`” that can be a valuable resource in troubleshooting this error.


The “getaddrinfo ENOTFOUND” error can be frustrating, but with the numerous reasons and solutions available online, it is possible to troubleshoot it. By following the steps listed above, you can hopefully get your web application up and running without any issues.

In conclusion, the “getaddrinfo ENOTFOUND” error can be a headache when building or testing web applications. In this article, we discussed some common reasons for the error, including an incorrect URL, wrong protocol, and issues with the server’s accessibility.

We also provided some tips on troubleshooting the error, such as configuring the `/etc/hosts` file and removing proxy settings. In summary, it’s crucial to double-check your settings and take the necessary steps to troubleshoot this error to ensure the smooth functioning of your web application.

Popular Posts