You may encounter an issue with agent activation for endpoint using a proxy. The following error may appear in the logs:
2017-05-18 12:43:51.418030: [dsa.Heartbeat/5] | Attempting contact with DSM at URL https://xx.com:443/ | .\dsa\Heartbeat.lua:170:ConnectToUrl | 2470:11F8:ActivateThread 2017-05-18 12:43:58.000000: [Error/1] | getaddrinfo: (error 11004: the requested name is valid, but no data of the requested type was found.) | .\common\NetUtil.cpp:1116:DsaCore::NetResolveAddr | 2470:11F8:ActivateThread 2017-05-18 12:43:58.634030: [dsa.Heartbeat/5] | Unable to reach a manager. | .\dsa\Heartbeat.lua:148:(null) | 2470:11F8:ActivateThread
Based on the log, the Deep Security Agent has an issue reaching the Deep Security Manager.
To resolve the issue:
- Add the parameter "--max-dsm-retries=1 --dsm-retry-interval=1" during the Agent-Initiated Activation (AIA).
- If the activation still fails, check the communication port requirement stated in this article: Communication ports used by Deep Security.