Connectivity Troubleshooting for Agent , Elasticsearch and the MC

Troubleshooting connectivity

Network troubleshooting between the Waratek Secure agent and the management console, as well as elasticsearch can be a complex task, as there are many factors that can impact the connection. To troubleshoot this issue, you should first check the network settings on the Waratek Secure agent and the managment console server, as well as elasticsearch to ensure that they are correct. This includes verifying that the IP address, FQDN's , and your port ranges are all correct. If you are unsure about any of these settings, you may need to consult your network administrator for assistance.

Firewall settings can often block incoming connections, so you will need to ensure that the appropriate ports are open on both devices. You may also need to configure your firewall to allow traffic through specific ports or protocols.

Below we will discuss the additional debug flags you could put in your file on the agent side to get additional logging.

You can safely enable the following parameter all the time as that will print out the start parameters for every application start.


It is useful for seeing all the configuration parameters for an application in the application logfile


For connectivity troubleshooting between Waratek Secure agent and MC , and elasticsearch the following can be enabled for troubleshooting purposes. You should disable these config parameters once connectivity is established.

com.waratek.debug.transport.file=<new log file>

These will print out debug messages into specified logfiles, the rules.log, and the mc.log.


Also setting the following


will enable additional more verbose during the showstart of the application in the application logs.