Dealing with Proxies

Prev Next

While Cisco Provider Connectivity Assurance will soon add support for proxy specification via the UI when configuring your connector/Sensor Collector, here's a workaround to add the right Docker environment variables to make it work.

You can either set the HTTPS_PROXY environment variable in your system environment before you run Sensor Collector, or you can add it to Sensor Collector's .env file. The .env file can be found at /opt/roadrunner/if the above instruction set was followed.

In both cases, your HTTPS_PROXY environment variable definition should look something like this:

HTTPS_PROXY=username:password@IP_Address_or_URL_of_proxy-server


Notes:
1. You need to replace username:password and IPAddressofproxyserverorURL of proxy server with valid credentials/values provided by customer prior to running run.sh script.
2. In case you use URL reference for the proxy, please make sure you have a valid DNS set for the docker container instance prior to running the run.sh script.
3. If you're specifying a URL, please DO NOT include the protocol. example:

GOOD: 
HTTPS_PROXY=someProxyURL.com
BAD: 
HTTPS_PROXY=https://someProxyURL.com


© 2025 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 tradmarks