Outgoing Proxies

Overview

Workbench has several features that require the server to make outgoing connections to the internet, such as:

If your environment requires an outbound proxy server to access the internet to use these features, set the appropriate proxy environment variables for Workbench’s server process to use the proxy when making these requests.

The variables can be added to env-vars:

/etc/rstudio/env-vars
http_proxy=http://192.168.1.1:8080
https_proxy=http://192.168.1.1:8080
no_proxy=localhost,192.168.1.10
Note

These variables are also forwarded to Workbench Job Launcher sessions.

Supported proxy variables

  • http_proxy: The proxy server to use for HTTP requests. HTTP_PROXY is also supported.
  • https_proxy: The proxy server to use for HTTPS requests. HTTPS_PROXY is also supported.
  • no_proxy: A comma-separated list of hostnames, IP addresses, CIDR ranges, or domain names that should not be accessed through the proxy. NO_PROXY is also supported.

No proxy configuration

Set the no_proxy environment variable to ignore the proxy for all local addresses. This is important for internal server communications, such as allowing Workbench to proxy communications to Job Launcher sessions and sessions to call back to the Workbench server.

The no_proxy variable supports:

  • Hostnames (port optional): localhost, myserver.example.com, example.com:443
  • IP addresses: 172.168.1.1
  • Domains: .example.com (matches all subdomains of example.com)
  • CIDR ranges: 172.4.0.0/16
  • Wildcard: * effectively disables the proxy for all requests
Back to top