Functions won't start after upgrading to node 22

[JoostLambregts]

We have a some Azure Functions running Node 18 or 20. When we upgrade to node 22, either through the portal or using Terraform, we get the following error and the functon won't start:

Microsoft.Azure.WebJobs.Script: Error building configuration in an external startup class. System.Net.Http: The SSL connection could not be established, see inner exception. System.Net.Security: Received an unexpected EOF or 0 bytes from the transport stream.

I'm guessing that the function runtime is trying to make some outbound call to an IP that is getting blocked by our firewall. Is that indeed the case? Is there a list of IPs or hostnames that we need to whitelist?

[swapnil-nagar]

Using the information in the Azure Functions Host Wiki on Sharing Your Function App Name Privately, could you please provide us with the invocation ID to further investigate the issue?

https://github.com/Azure/azure-functions-host/wiki/Sharing-Your-Function-App-name-privately

[JoostLambregts]

Here is an invocation, from before we upgraded to node 22 of course.

execution timesstamp: 2025-05-21T11:18:16.0094737+00:00',
invocation id; 13583993-6e60-485e-97de-c54f17ad7df2
Location: West Europe

[JoostLambregts]

I got an update from a colleague that the issue might be fixed after upgrading the extension bundle version from 3.x to 4.x. I didn't get conformation from him yet though and I'm not working today, so I'll check on monday and report back.