Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Azure App Service Deploy fails behind proxy
See original GitHub issueRequired Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: AzureRmWebAppDeployment
Environment
-
Server - Azure DevOps Server 2019
- If using TFS on-premises, provide the version: 17.143.28621.4 (AzureDevOps2019)
-
Agent - Private:
-
If using private agent, provide the OS of the machine running the agent and the agent version:
-
Windows Server 2016 (version 1607)
-
Agent Version: 2.144.2
-
Issue Description
Task: Azure App Service Deploy. Version: 3.4.16.
When attempting to deploy to Azure app service from behind our corporate proxy, the task fails with the following error:
[error]Error: Failed to fetch App Service '*****' publishing credentials. Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND 8080 8080:80
The private agents I have running have all be configured following this guide https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/proxy?view=azure-devops&tabs=windows and are able to communicate through our proxy and download packages from nuget without issue as part of our build pipelines. It appears that the Azure App Service Deploy task is using node to communicate with Azure but node doesn’t appear to have any knowledge of the proxy config that has been applied to the agent.
Task logs
[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:19 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
As azure-pipeline-tasks uses typed-rest-client, this might give more details: https://github.com/microsoft/typed-rest-client/issues/163
After further investigation we had to remove the agent, then reinstall after adding the VSTS_HTTP_PROXY environment variable hack with the proxy details. The connectivity is then established successfully.
Please close this problem. Thank you for your help.