Alerts of « Connection refused » related to the doorman backend are being output frequently by Elements Linux Protection

Issue:

Alerts of "Connection refused" related to the doorman backend are being output frequently by Elements Linux Protection.

Example:
doormand: Failed to send request to Doorman: generic:111 = Connection refused

Resolution:

Make sure that the connections to the following Security Cloud domains are allowed on your Firewall and proxy.

Business Suite 16 onwards

• corp-reg.fsapi.com This server is used by Policy Manager for license registration. Blocking this server will prevent license validation.
  guts2.fsapi.com (also TCP/80) This server is used to deliver updates for scanning engines and detection rules, and for some products updates to the software itself. Blocking this server will completely stop security updates.
• a.karma.sc2.fsapi.com
• restmc.mind.sc2.fsapi.com
• mind-failover.sc2.fsapi.com
• api.doorman.fsapi.com Backend services needed for Security Cloud functionality
• api.prd.glb.us-prd.fsapi.com Used to control updates for Linux Security 64
• download.fsapi.com Used for the hotfix update mechanism for Linux Security 64

If you have allowed the connections, you could check the connectivity status to the domains by accessing to the following URLs from any affected server.

https://baseguard.doorman.fsapi.com/doorman/v1/healthcheck
https://doorman.sc.fsapi.com/doorman/v1/healthcheck
https://a.karma.sc2.fsapi.com/healthcheck

If you are using a proxy, check the connectivity status from your Linux server to the proxy server and make sure that it could be done successfully.