Deployment of Azure Functions in Visual Studio Code fails.

Question

I was getting an ENOTFOUND error, so I recreated my storage access key, placed it into the AzureWebJobsStorage entry in my Function app, and now I simply get an error:

Failed to get status of deployment.

I've tried restarting, recreating the project, I've deleted and recreated resources and storages, I cannot seem to deploy.

I have another project (I haven't tested since) that has deployed fine for months. This project is a conversion from an old system (I use PlayFab) that needs Azure Functions and I just keep getting strange errors.

Any help would be sincerely appreciated! Thanks!

-Matt

*Edit - I'm back to getting the ENOTFOUND error when trying to deploy. I just created an app and its resources via web browser and it still fails. Please help!

Answer 1

Hi Matthew,

The ENOTFOUND error typically means that the DNS server is not able to resolve a domain name into an IP address. This can be due to a number of issues. However, let's start with a few possible solutions:

• Network Issue: If you're working on a corporate network, there could be a firewall or network rule that is preventing you from accessing the resources. If that's the case, please check your network settings.
• Invalid Configuration: Make sure your Azure Function App settings are correct, specifically your AzureWebJobsStorage entry. It should be something like: DefaultEndpointsProtocol=https;AccountName=youraccountname;AccountKey=youraccountkey;EndpointSuffix=core.windows.net. Please double-check that all the details are correct.
• Expired Access Key: When you regenerate your storage account keys, you must also update all places where you've used the old key. If you haven't done this, it could be causing the issue. Also, make sure to use the correct key, either key1 or key2.
• DNS Resolution Issue: This could be a DNS resolution problem. Try to flush your DNS cache. The process varies by operating system. For example, on Windows, you can use the command ipconfig /flushdns in your command prompt. If you're using Linux, you can use the command sudo systemd-resolve --flush-caches.
• Azure Service Health: Sometimes, Azure might be experiencing issues in the region where your resources are located. Check the Azure Service Health in your Azure portal to ensure there are no ongoing issues.
• Azure CLI Version: If you're using Azure CLI for deployment, make sure it's updated to the latest version. To update Azure CLI, you can use the command az upgrade.

I hope this helps?