Unable to debug azure nodejs function locally about azure-functions-nodejs-worker HOT 4 CLOSED

Today I found that the local debugging feature has returned to normal. However, the cause of the problem is still unclear. Anyway, thank you all for your assistance.

from azure-functions-nodejs-worker.

The error "Value cannot be null. (Parameter 'provider')" is usually related to your local.settings.json. Can you double check everything in that file? For example, make sure the connection string for AzureWebJobsStorage is valid.

from azure-functions-nodejs-worker.

I noticed that recently, extensions like VSCode Azure Account, Azure Functions, and Azure Resources have all been updated. I've also updated the .NET updates from Windows Update. Additionally, I've upgraded Visual Studio 2022 to the latest version. Following the previous steps: I created a new project, pressed F5, and connected to a real Azure Storage account. However, I still couldn't start local debugging, and the symptoms are the same.

Here is the content of the local.settings.json file. I logged into https://portal.azure.com and verified the name and key of the storage account, both of which are correct.

{
  "IsEncrypted": false,
  "Values": {
    "AzureWebJobsStorage": "DefaultEndpointsProtocol=https;AccountName=<Account-Name-Is-Correct>;AccountKey=<Account-Key-Is-Correct>;EndpointSuffix=core.windows.net",
    "FUNCTIONS_WORKER_RUNTIME": "node",
    "AzureWebJobsFeatureFlags": "EnableWorkerIndexing"
  }
}

from azure-functions-nodejs-worker.

Are you by chance behind a company proxy or have anything else unique affecting the internet on you machine? I found this issue with a related error message: Azure/azure-functions-host#8774. In that case they had a firewall causing them problems.

from azure-functions-nodejs-worker.