Cannot connect to vercel postgres database from wsl

[glaucusec]

Summary

I was learning nextjs through the official documentation. At this section on the tutorial, when I tried to run npm run seed it throws me the following error. I tried running the same command by copying the files to windows C:\Users\abhis\Documents and from this folder the command runs fine and no issues. what is wrong with running this on wsl?

node:events:496
      throw er; // Unhandled 'error' event
      ^

AggregateError [ETIMEDOUT]: 
    at internalConnectMultiple (node:net:1116:18)
    at internalConnectMultiple (node:net:1184:5)
    at Timeout.internalConnectMultipleTimeout (node:net:1710:5)
    at listOnTimeout (node:internal/timers:575:11)
    at process.processTimers (node:internal/timers:514:7)
Emitted 'error' event on WebSocket instance at:
    at emitErrorAndClose (/home/abishek/nextjs-dashboard/node_modules/ws/lib/websocket.js:1016:13)
    at ClientRequest.<anonymous> (/home/abishek/nextjs-dashboard/node_modules/ws/lib/websocket.js:864:5)
    at ClientRequest.emit (node:events:518:28)
    at TLSSocket.socketErrorListener (node:_http_client:500:9)
    at TLSSocket.emit (node:events:518:28)
    at emitErrorNT (node:internal/streams/destroy:169:8)
    at emitErrorCloseNT (node:internal/streams/destroy:128:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'ETIMEDOUT',
  [errors]: [
    Error: connect ETIMEDOUT 34.194.100.28:443
        at createConnectionError (node:net:1646:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1705:38)
        at listOnTimeout (node:internal/timers:575:11)
        at process.processTimers (node:internal/timers:514:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '34.194.100.28',
      port: 443
    },
    Error: connect ENETUNREACH 2600:1f18:240c:5421:acd1:6284:5a8a:d6e9:443 - Local (:::0)
        at internalConnectMultiple (node:net:1180:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1710:5)
        at listOnTimeout (node:internal/timers:575:11)
        at process.processTimers (node:internal/timers:514:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2600:1f18:240c:5421:acd1:6284:5a8a:d6e9',
      port: 443
    },
    Error: connect ETIMEDOUT 44.207.148.149:443
        at createConnectionError (node:net:1646:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1705:38)
        at listOnTimeout (node:internal/timers:575:11)
        at process.processTimers (node:internal/timers:514:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '44.207.148.149',
      port: 443
    },
    Error: connect ENETUNREACH 2600:1f18:240c:5454:82a4:8209:20f8:a5c1:443 - Local (:::0)
        at internalConnectMultiple (node:net:1180:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1710:5)
        at listOnTimeout (node:internal/timers:575:11)
        at process.processTimers (node:internal/timers:514:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2600:1f18:240c:5454:82a4:8209:20f8:a5c1',
      port: 443
    },
    Error: connect ETIMEDOUT 23.23.229.9:443
        at createConnectionError (node:net:1646:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1705:38)
        at listOnTimeout (node:internal/timers:575:11)
        at process.processTimers (node:internal/timers:514:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '23.23.229.9',
      port: 443
    },
    Error: connect ENETUNREACH 2600:1f18:240c:543b:a8aa:14fb:d008:11fe:443 - Local (:::0)
        at internalConnectMultiple (node:net:1180:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1710:5)
        at listOnTimeout (node:internal/timers:575:11)
        at process.processTimers (node:internal/timers:514:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2600:1f18:240c:543b:a8aa:14fb:d008:11fe',
      port: 443
    },
    Error: connect ETIMEDOUT 100.26.116.133:443
        at createConnectionError (node:net:1646:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1705:38)
        at listOnTimeout (node:internal/timers:575:11)
        at process.processTimers (node:internal/timers:514:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '100.26.116.133',
      port: 443
    },
    Error: connect ENETUNREACH 2600:1f18:240c:544d:621b:957c:81:5e5b:443 - Local (:::0)
        at internalConnectMultiple (node:net:1180:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1710:5)
        at listOnTimeout (node:internal/timers:575:11)
        at process.processTimers (node:internal/timers:514:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2600:1f18:240c:544d:621b:957c:81:5e5b',
      port: 443
    },
    Error: connect ETIMEDOUT 44.199.59.172:443
        at createConnectionError (node:net:1646:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1705:38)
        at listOnTimeout (node:internal/timers:575:11)
        at process.processTimers (node:internal/timers:514:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '44.199.59.172',
      port: 443
    },
    Error: connect ENETUNREACH 2600:1f18:240c:5419:4ecf:2a7c:cf52:31ae:443 - Local (:::0)
        at internalConnectMultiple (node:net:1180:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1710:5)
        at listOnTimeout (node:internal/timers:575:11)
        at process.processTimers (node:internal/timers:514:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2600:1f18:240c:5419:4ecf:2a7c:cf52:31ae',
      port: 443
    },
    Error: connect ETIMEDOUT 52.20.107.131:443
        at createConnectionError (node:net:1646:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1705:38)
        at listOnTimeout (node:internal/timers:575:11)
        at process.processTimers (node:internal/timers:514:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '52.20.107.131',
      port: 443
    },
    Error: connect ENETUNREACH 2600:1f18:240c:540b:c14a:4d57:1251:234d:443 - Local (:::0)
        at internalConnectMultiple (node:net:1180:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1710:5)
        at listOnTimeout (node:internal/timers:575:11)
        at process.processTimers (node:internal/timers:514:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2600:1f18:240c:540b:c14a:4d57:1251:234d',
      port: 443
    }
  ]
}

Additional information

No response

Example

No response

[glaucusec]

I just converted wsl 2 to wsl 1 and the issue is now solved. It's weird. idk what really happened there. but for some reason wsl 1 do no have any issues.

[shengcaii]

Hi @glaucusec , I'm facing the same error like that one on my Debian, linux machine. May I ask you about how to troubleshoot on my machine?

[glaucusec]

Hi @glaucusec , I'm facing the same error like that one on my Debian, linux machine. May I ask you about how to troubleshoot on my machine?

I haven't found a proper reason or "how to fix" guide for this problem. but while reading some of the posts on the reddit, I noticed that many developers still use wsl 1 instead of wsl 2. they have their own reason for that. since I haven't found a proper solution, I just converted my ubuntu from wsl 1 to 2. and it's working totally fine now. If you are asking for a proper solution, this conversion might work. you can find how to convert on the official microsoft website.

[glaucusec]

One more thing to note is that. I have 2 ubuntu distros installed. one is running on wsl 1 and another one is running on wsl 2. on the distro running on wsl 1 it works for the node version 20.12.2. On the distro running on wsl 2, it shows the error if I am using node v20.12.2. If I switch node version to 18.20.2 and run the command npm run seed it works fine.

[shengcaii]

Thank you @glaucusec , I appreciate your help in resolving this issue. It works on v18.20.2. (Edited)

[neeraj1bh]

WSL2 is a pain but as @shengcaii mentioned the issue is resolved using node v18 I was previously getting an ETIMEDOUT and ENETUNREACH with Vercel Postgres instance using node v20

[dakshika]

I'm getting same error on macOs 12.7.4 :(

[bpinazmul18]

I'm getting the same error. Ubuntu 22.04 and nodejs 21.
How can I fix:
uninstall nodejs 21
install nodejs 19

[dakshika]

I'm getting the same error. Ubuntu 22.04 and nodejs 21. How can I fix: uninstall nodejs 21 install nodejs 19

Try to change the node version to 18.12.1, then this will work

[bpinazmul18]

It's working

[sebastiannjose]

Switched back to node v18 and that fixed the seeding problem, thank you

[iamkd]

Just in case someone's looking, what fixed it for me is setting the WSL2's networkingMode to mirrored. You can do that either manually in .wslconfig or there's a UI option in the "WSL Settings" app.