Error: connect ECONNREFUSED ::1:1197

[Flixbox]

Hey! About a few seconds after executing the command npx bundle-wizard reddit.com, I receive the following error message:

PS C:\Windows\System32> npx bundle-wizard reddit.com

🧙‍  Welcome to bundle-wizard

🤖  Loading https://reddit.com ...


⚠️  Unable to fetch website data

Error: connect ECONNREFUSED ::1:1197
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1300:16) {
  errno: -4078,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '::1',
  port: 1197
}

Am I doing something wrong? I'm getting the same result with all other URLs.

PS C:\Windows\System32> node -v
v18.8.0

[kevinpastor]

I have the same issue on Node.js@17.2.0 and npm@8.1.4. I've tried with pnpm@7.9.3 and it's the same.

[firatgh]

npx bundle-wizard localhost:3000

Output:

🧙‍  Welcome to bundle-wizard

🤖  Loading http://localhost:3000 ...


⚠️  Unable to fetch website data

Error: connect ECONNREFUSED ::1:51226
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1300:16) {
  errno: -61,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '::1',
  port: 51226
}

[akaltar]

Digging around looks like this is an issue in chrome-launcher + Node 17+
A fix for this has been merged, so fixing bundle-wizard should be updating to chrome-launcher 0.14.2+ and adjusting to any breaking behaviour in that release.
Alternatively downgrading to Node 16 might also work for the time being

[unleashit]

Same issue.

⚠️  Unable to fetch website data

Error: connect ECONNREFUSED 127.0.0.1:34217
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1571:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 34217
}

Without looking too deeply it might be a WSL issue, since WSL sometimes has issues with 127.0.0.1. An option to set the local server hostname could let a WSL user change it to localhost.

[JamieMason]

PR created at #44 which hopefully does the job.

[prantlf]

I get ECONNREFUSED right away with a http://locvalhost website. Using --interactive works. It'd be worth upgrading the ancient dependencies, which #44 aims for