While Cisco Provider Connectivity Assurance will soon add support for proxy specification via the UI when configuring your connector/Sensor Collector, the following workaround explains how to configure proxy settings using Docker environment variables.
You can configure proxy settings by setting the HTTPS_PROXY and HTTP_PROXY environment variables in either of the following ways:
- Set the environment variables in your system environment before running Sensor Collector, or
- Add the variables directly to the Sensor Collector
.envfile
The.envfile can be found at:/opt/roadrunner/
When running Sensor Collector version 0.652.0 or later behind a proxy, you must configure both HTTPS_PROXY and HTTP_PROXY.
Sensor Collector performs certificate validation checks that require outbound HTTP access (for example, certificate revocation list checks). If only HTTPS_PROXY is set, these checks may fail and prevent the connector from establishing a meta connection.
Example configuration:
HTTPS_PROXY=username:password@IP_Address_or_URL_of_proxy-server
HTTP_PROXY=username:password@IP_Address_or_URL_of_proxy-server
Notes:
- Replace
username:passwordandIP_Address_or_URL_of_proxy-serverwith valid credentials and values provided by the customer before running therun.shscript. - If you use a URL reference for the proxy, ensure that valid DNS is configured for the Docker container before running the
run.shscript. - If you are specifying a URL, do NOT include the protocol.
GOOD:
HTTPS_PROXY=someProxyURL.com
HTTP_PROXY=someProxyURL.com
BAD:
HTTPS_PROXY=https://someProxyURL.com
HTTP_PROXY=http://someProxyURL.com
© 2026 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and trademarks