Upgrade to node 18 fails for authentication emulator

[LanderBeeuwsaert]

[REQUIRED] Environment info

firebase-tools:
11.16.1

Windows 10

Platform:

[REQUIRED] Test case

Upgrading node from v16.14.2 to the latest 18.12.1 seems to give an issue with programmatically getting to the authentication emulator. We get:

FirebaseAppError: Error while making request: connect ECONNREFUSED ::1:9095. Error code: ECONNREFUSED
at C:\lander\devprojects\acro-companion\e2e-testing\node_modules\firebase-admin\lib\utils\api-request.js:178:19
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at Populator.addUser (file:///C:/lander/devprojects/acro-companion/e2e-testing/utils/populator.ts:1:2302)
at BootPopulator.doPopulate (file:///C:/lander/devprojects/acro-companion/e2e-testing/utils/boot-populator.ts:1:539)
at asyncMain (file:///C:/lander/devprojects/acro-companion/e2e-testing/utils/boot-populator.ts:1:880) {
errorInfo: {
code: 'app/network-error',
message: 'Error while making request: connect ECONNREFUSED ::1:9095. Error code: ECONNREFUSED'
},
codePrefix: 'app'
}

This is when we use a firebase-admin node instance to create test users through the authentication emulator running on port 9095
re-installing v16.14.2 solves the issue

[google-oss-bot]

This issue does not seem to follow the issue template. Make sure you provide all the required information.

[taeold]

Can you describe your setup? How are you connecting to the Auth Emulator (are you manually setting up the environment variable?)

FYI Node 18 changed the way "localhost" gets resolved and will prefer ipv6. Your auth emulator instance may be connecting to ipv4 instead.

[LanderBeeuwsaert]

Hi @taeold , ah that's already interesting about the ipv6, however we just use localhost to connect so I suppose that should work the same?

So when running the emulator, we start a node.js process that does this:

with the databaseURL pointing to our remote firebase test environment.

firebase.json looks like this:

Is there something we need/can configure somewhere to make the auth emulator instance connect to ipv6? (or as a first step can we check somewhere if it's connecting to ipv4 or ipv6?)

[taeold]

@LanderBeeuwsaert IIUC Firebase Emulators will spin up and connect to ipv4 instead.

Can you try replacing localhost with 127.0.0.1 in your process.env variables and let us know if that helps?

[LanderBeeuwsaert]

Hi all, yes this solved it thanks!