What could cause "connect ETIMEDOUT" error when the URL is working in browser?

Question

I train myslef with NodeJS and tried a simple GET call. Here is my code:

var http = require('http');

var options = {
    host: 'www.boardgamegeek.com',
    path: '/xmlapi/boardgame/1?stats=1',
    method: 'GET'
}

var request = http.request(options, function (response) {
    var str = ""
    response.on('data', function (data) {
        str += data;
    });
    response.on('end', function () {
        console.log(str);
    });
});

request.on('error', function (e) {
    console.log('Problem with request: ' + e.message);
});

request.end();

The URL called seems to work in my browser https://www.boardgamegeek.com/xmlapi/boardgame/1?stats=1

Anyway, I've got Problem with request: connect ETIMEDOUT when I run the code and I have no idea how to fix it.

What could cause this error ? Is it my code or is it a network/proxy issue?

Yeah indeed, I've got a corporate proxy! – Alex Oct 26 '15 at 16:54 — Alex, Oct 26 '15 at 16:54

score 21 · Accepted Answer · edited Oct 27 '15 at 09:00

21

When behind a proxy you need to make the following modifications (as explained in this answer):

put the proxy host in the host parameter
put the proxy port in the port parameter
put the full destination URL in the path parameter :

Which gives:

var options = {
    host: '<PROXY_HOST>',
    port: '<PROXY_PORT>',
    path: 'http://www.boardgamegeek.com/xmlapi/boardgame/1?stats=1',
    method: 'GET',
    headers: {
        Host: 'www.boardgamegeek.com'
    }
}

edited Oct 27 '15 at 09:00

Alex

2,927
8
37
56

answered Oct 26 '15 at 16:58

sdabet

18,360
11
89
158

Thanks! It works. I had to add http in the path and an host header but not it's working trough the proxy. – Alex Oct 27 '15 at 08:40
I have an username and a password on my proxy, how can I implement this? – Agustín Clemente Jan 15 '19 at 18:23
What about if the code comes from a 3pp and we cannot modify it? how to bypass the proxy? – Alejandro González Aug 03 '21 at 09:06

score 4 · Answer 2 · answered Nov 06 '20 at 13:15

4

In my case it was because of http but not https as required

answered Nov 06 '20 at 13:15

cane

892
1
10
16

Seunara · Answer 3 · 2022-05-24T11:53:04.813

3

If this error occurs while using POSTMAN.

So, when you call a request in Postman and the API requires your VPN to be up before you can make a successful call. You will need to connect or reconnect your VPN.

In my case, I was working on a company's laptop. I found out it was the VPN that was down.

edited May 24 '22 at 11:53

answered Mar 24 '22 at 16:50

Seunara

157
1
1
9

score 1 · Answer 4 · answered Aug 27 '18 at 15:10

I was facing this issue on Ubuntu Server while maintaining a node instance on PM2. Basically after restarting the instance after taking the pull I was getting the same error on initial connection of mySQL inside the code.

Error: connect ETIMEDOUT
at Connection._handleConnectTimeout (/home/deam_server/node_modules/mysql/lib/Connection.js:419:13)
at Object.onceWrapper (events.js:275:13)
at Socket.emit (events.js:182:13)
at Socket.EventEmitter.emit (domain.js:442:20)
at Socket._onTimeout (net.js:447:8)
at ontimeout (timers.js:427:11)
at tryOnTimeout (timers.js:289:5)
at listOnTimeout (timers.js:252:5)
at Timer.processTimers (timers.js:212:10)

Though the same code was running perfectly on my local machine. After that I used "df" command which helped me to realise that my root directory was 100% occupied. I allotted some memory to the root directory and the restarted the node instance and then it started working fine.

score 1 · Answer 5 · answered Mar 12 '19 at 21:37

The following change with the request worked for me:

 var options = {
         proxy:'PROXY URL', 
         uri: 'API URL',
         method: 'GET' 
         }
 request(options, function (err, response, body) {
     if(err){
        console.log('error:', err);
       } else {
     console.log('body:', body);
      }
   });

score 1 · Answer 6 · answered Nov 15 '19 at 04:11

1

In my case it was a misconfigured subnet. Only one of the 2 subnets in the ELB worked. But my client kept trying to connect to the misconfigured one.

answered Nov 15 '19 at 04:11

M.Vanderlee

2,847
2
19
16

score 1 · Answer 7 · answered Sep 13 '20 at 09:03

1

if you have URL like :

  URL: 'localhost:3030/integration',

The URL above cause some issues because HTTP does not exist at the beginning of URL so Just change it to it should work.

URL: 'http://localhost:3030/integration',

answered Sep 13 '20 at 09:03

Yazan Najjar

1,830
16
10

Deepak · Answer 8 · 2023-01-03T11:22:05.783

1

In my case, I was getting this error because the request body of my post api was very large.

edited Jan 03 '23 at 11:22

answered Jun 16 '22 at 08:00

Deepak

3,134
2
24
24

score 1 · Answer 9 · answered Feb 14 '23 at 18:54

1

Sometimes it can simply be because your internet is down.

answered Feb 14 '23 at 18:54

Mansvini

11
3

What could cause "connect ETIMEDOUT" error when the URL is working in browser?

9 Answers9

Linked