Container defender fails to connect to the console when installing it using twistcli with a proxy connection
4574
Created On 02/10/22 22:15 PM - Last Modified 06/15/23 20:42 PM
Symptom
Container defender fails to connect to the console when installing it using twistcli
Environment
- Prisma Cloud Compute SaaS version.
- Prisma Cloud Compute Self-Hosted version 20.12 and above.
- Twistcli configured.
- Any Proxy connection.
Cause
If you have a host or a server with docker runtime installed, and would like to deploy the defender using twistcli instead of the script that is generated from the console, the command would be as the following:
sudo ./twistcli defender install standalone container-linux \
--address https://<CONSOLE> \
--user <USER>
Now, if there is a proxy, you will need to add your proxy address --http-proxy as the following:
sudo ./twistcli --http-proxy <PROXY_ADDRESS> defender install standalone container-linux --address https://<CONSOLE> --user <USER>
This will cause a disconnection between the console and defender as the defender will try to connect to the console address instead of the proxy address.
Resolution
To resolve this issue, one need to also specify the proxy address --proxy-address to the install bundle as shown below:
sudo ./twistcli --http-proxy <PROXY_ADDRESS> defender install standalone container-linux --proxy-address <PROXY_ADDRESS> --address https://<CONSOLE> --user <USER>This will allow the defender to connect to the console with no connectivity issues.