Skip to main content

Situation:
We had scheduled a policy, but the client device disconnected two minutes before the scheduled scan.

Findings:
Upon analyzing the amagent log, we identified intermittent connection failures between the client system and the Automox WebSocket server (wss://api.automox.com/stomp).

After a few minutes, the connection was re-established, and the server sent an install update notification to the client device.

Question:

  1. What could be the potential causes of these connection failures between the client system and the Automox WebSocket server?
  2. What steps can we take to resolve this issue?

Hi ​@RAHULNATH !

 

Stomp disconnections with the amagent agent typically are caused by something environmental severing its connection to api.automox.com

Generally this is related to something at the network level prohibiting traffic to that URL like firewall, routing, proxy, or VPN. It could also be at the application level where endpoint protection or antivirus is blocking that traffic.

I would recommend reviewing our Firewall Allowlisting Documenting and ensuring that the correct rules are in place for your network appliances.

It would also be beneficial to ensure that the amagent and its components are also trusted within your EPP.

If you’re still having issues after reviewing and implementing the referenced documentation, please open a ticket with our Support team for further assistance.

Reply


Terms & ConditionsCookie settings