HTTP Proxy Configuration

Jenkins connects to the internet for several tasks, like checking the update center, downloading plugins, and installing tools. In some networks, all HTTP and HTTPS traffic to the internet must go through a proxy server. In that case, Jenkins needs to be told which proxy server to use.

If you’re not sure whether your network uses a proxy, check the proxy settings of your web browser or ask your network administrator. If your network only uses NAT to reach the internet, you don’t need a proxy configuration.

This page is about Jenkins making outbound connections through a proxy. If you want to put a proxy in front of Jenkins so users can reach it, see Reverse proxy configuration.

Configuring the proxy

Go to Manage Jenkins > System, find the HTTP Proxy Configuration section, and click Setup.

Field Description

Server

Host name or address of the proxy server, for example proxy.example.com. Leaving this empty means Jenkins connects to the internet directly.

Port

The port the proxy server listens on, for example 8080.

User name

The user name, if the proxy server requires authentication.

Password

The password, if the proxy server requires authentication.

No Proxy Host

Host name patterns that Jenkins should connect to directly, without the proxy. Enter one pattern per line. * is a wildcard, for example *.example.com.

Jenkins connects to the proxy server over HTTP. If the proxy requires authentication, the user name and password could be seen by someone on the same network.

Before Jenkins 2.435, these settings were on the Advanced page of the plugin manager.

Testing the proxy

Under Advanced, enter a URL in Test URL, for example https://updates.jenkins.io, and click Validate Proxy. Jenkins tries to reach that URL using the proxy settings in the form and shows whether it worked.

Builds and tools on agents

The proxy configured in Jenkins is used by Jenkins itself and by plugins that support it. Commands that run in builds, such as git, mvn, or curl, do not use it. Those tools need their own proxy configuration, usually through the http_proxy, https_proxy, and no_proxy environment variables or the tool’s own settings.

The Java runtime running Jenkins can also be configured with the standard Java networking properties, but configuring the proxy in Jenkins is preferred.



Was this page helpful?

Please submit your feedback about this page through this quick form.

Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?

    


See existing feedback here.