Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wazuh extension error: connect to the host via ssh: ssh: connect to host 192.168.56.51 port 5985: Connection refused #356

Open
cyberranger001 opened this issue Feb 1, 2025 · 0 comments

Comments

@cyberranger001
Copy link

cyberranger001 commented Feb 1, 2025

System Info:
I am on an Ubuntu 24.04 host (Desktop PC)
Using VMware Workstation 17.5
Doing my lab deployments with Docker

Hi,
I am trying to add the wazuh extension to the GOADv3 lab after successfully provisioning the lab. I have added the Exchange server and the windows 10 machine with no issue but when I try to add wazuh, the provisioning fails with this error:

fatal: [wazuh]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host 192.168.56.51 port 5985: Connection timed out", "unreachable": true}

Image

It looks like for some reason vagrant is trying to ssh to the Ubuntu box over port 5985 instead of 22.

I have gone through all the inventory and vagrant files to try to find out if there is any place where it is set for the ssh connection to be done over 5985 but I cannot find any. I have also gone on the Ubuntu 22 box for wazuh and tried to even manually open and enable 5985 but that did not work.

I also tried to change the Vagrant file to do the ssh auth with username and password but that didn't work as well.

Would really appreciate some help/pointers on how to fix this pls.

There is a message at the start of the provisioning:

**GOAD-WAZUH: Vagrant insecure key detected. Vagrant will automatically replace
GOAD-WAZUH: this with a newly generated keypair for better security.**

Was wondering if this has anything to do with it

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant