Proxy error: Could not proxy request (ENOTFOUND)

Created by: philjoseph

If you are reporting a bug, please fill in below. Otherwise feel free to remove this template entirely.

Can you reproduce the problem with latest npm?

Yes - npm 4.4.1

Many errors, especially related to "missing modules", are due to npm bugs.

If you're using Windows, follow these instructions to update npm.

If you're using OS X or Linux, run this to update npm:

npm install -g npm@latest

cd your_project_directory
rm -rf node_modules
npm install

Then try to reproduce the issue again.

Can you still reproduce it? Yes - it happens around 50% the requests

Description

Running a CRA application in development, using a proxy to my API server hosted in heroku, I am hitting on half of the request the above error. Note that the other half of the requests are going through.

What are you reporting? Proxy DNS resolution issue that I do not succeed to analyse further.

Expected behavior

All request to my web app shall work and all API requests proxied to the heroku server withno problems

Actual behavior

Proxy error.

Environment

Run these commands in the project folder and fill in their results:

npm ls react-scripts (if you haven’t ejected): Did not ejected
node -v: v7.3.0
npm -v: 4.4.1

Then, specify:

Operating system: uname -a: Linux sarah 4.4.0-66-generic #87 (closed)-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Browser and version: 56.0.2924.87 (64-bit)

Reproducible Demo: not yet available...

Please take the time to create a new app that reproduces the issue.

Alternatively, you could copy your app that experiences the problem and start removing things until you’re left with the minimal reproducible demo.

(Accidentally, you might get to the root of your problem during that process.)

Push to GitHub and paste the link here.

By doing this, you're helping the Create React App contributors a big time! Demonstrable issues gets fixed faster.