-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Description
Hello everyone, I can't connect my agent properly because it seems like it doesn't encode the IP I manually wrote:
2025/11/20 23:35:36 wazuh-agent: CRITICAL: (1237): Invalid ip address: '192,‘6Ð.1,–5'.
I tried to manually change the ossec.conf file (without copy/pasting the IP, and it's written right in there), restarting, reeboting, reinstalling and so on but it still doesn't work. The IP it appaers is still '192,‘6Ð.1,–5' instead of the proper numbers.
Do you have any idea on how to make it done please?
As you can see the IP for the manager appaers to be 192,‘6Ð.1,–5
ossec.log:
2025/11/21 11:52:13 wazuh-agent: INFO: (1410): Reading authentication keys file.
2025/11/21 11:52:13 wazuh-agent: CRITICAL: (1237): Invalid ip address: '192,‘6Ð.1,–5'.
2025/11/21 11:52:13 wazuh-agent: INFO: Received exit signal. Starting exit process.
2025/11/21 11:52:13 wazuh-agent: INFO: Set pending exit signal.
ossec.conf:
<ossec_config>
<client>
<server>
<address>192.168.1.56</address>
<port>1514</port>
<protocol>tcp</protocol>
</server>
<config-profile>windows, windows10</config-profile>
<crypto_method>aes</crypto_method>
<notify_time>20</notify_time>
<time-reconnect>60</time-reconnect>
<auto_restart>yes</auto_restart>
</client>