Connection refused after new version released

[pablogdnd]

Hi there!
After you released the latest version (with node v18 changes), both the pipeline and our local code, started to fail with many
System.Net.Sockets.SocketException : Connection refused

SLS version
Framework Core: 3.35.2 (local) 3.35.2 (global)
Plugin: 7.0.5
SDK: 4.4.0

Node v18.18.0
npm 9.8.1

serverless-s3-local 0.8.1
serverless-offline 8.8.1

i can also see your package references serverless-offline v13, which also removed old node versions

I tried updating everything but im still getting those connection refused...
Tks

[pablogdnd]

I found the problem, node v18 uses curl rather than node-fetch, and our local s3 setup was using the IP and not localhost.
If you execute curl localhost:8001 -v, works fine, but failed with curl 127.0.0.1:8001

[ar90n]

Hi @pablogdnd !
Thanks for your report and workaround.
The priority of the name resolution method causes this problem.
Node v18 tries to translate the hostname into the ipv6 address at first.
So 'localhost' is translated into "::1" in your situation.

I think your workaround is good and enough to work.
In my opinion, using -dns-result-order=ipv4first as an argument of the node as follows may help you.

$ node -e "const dns = require('dns'); dns.lookup('localhost', (err, addresses) => {console.log(addresses)});"
::1

$ node --dns-result-order=ipv4first -e "const dns = require('dns'); dns.lookup('localhost', (err, addresses) => {console.log(addresses)});"
127.0.0.1