Udostępnij przez

Run a self-hosted agent behind a web proxy

Azure DevOps Services | Azure DevOps Server | Azure DevOps Server 2022 | Azure DevOps Server 2020

When your self-hosted agent requires a web proxy, you can inform the agent about the proxy during configuration. This allows your agent to connect to Azure Pipelines or TFS through the proxy. This in turn allows the agent to get sources and download artifacts. Finally, it passes the proxy details through to tasks which also need proxy settings in order to reach the web.

Specify proxy bypass URLs

Create a .proxybypass file in the agent's root directory that specifies regular expressions (in ECMAScript syntax) to match URLs that should bypass the proxy. For example:

github\.com
bitbucket\.com

Enable Basic authentication for proxy setup

The agent configuration may not be compatible with certain corporate proxy setups that use default NTLM authentication, and you may get 407 authentication errors. In such cases, you can enable Basic authentication for the proxy by adding the --usebasicauthforproxy flag during agent configuration, provided the proxy supports fallback to Basic authentication.

For example:

./config.cmd --proxyurl http://proxy.company.com:port --proxyusername <userNamePlaceholder> --proxypassword <passwordPlaceholder> --usebasicauthforproxy
  • Last updated on