ERROR couldn't connect to tcp socket

View thread

tariotics

Hi All,

We would like to check what could be the cause when getting the below error message in nxlog.log when using port 514?

ERROR couldn't connect to tcp socket on logs-01.loggly.com:514; A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. 

INFO connecting to 192.168.1.1:514

INFO reconnecting in 2 seconds

We are from SolarWinds Loggly and helping a customer to identify the cause as to why they are getting the above error message. From our documentation, we already advised them in editing the configuration file as "Administrator", this means that you should actually open up text editor as Administrator, but the issue still persists. Reference: https://documentation.solarwinds.com/en/success_center/loggly/content/admin/troubleshooting-nxlog.htm#Check-Connection

 

The customer is using a latest version of NXLog Community Edition (nxlog-ce-3.2.2329). Is this a bug?