ERR_SOCKET_NOT_CONNECTED when trying to connect to wazuh dashboard

494 views
Skip to first unread message

Daan Fleuren

unread,
Nov 14, 2022, 9:19:54 AM11/14/22
to Wazuh mailing list
Hello,

I am currently trying to test Wazuh in our corporate environment. This was going reasonably well and smoothly. Until this problem arose, rendering wazuh (as good as) unusable.

The problem is that when I try to open the wazuh dashboard with google chrome I get the message "ERR_SOCKET_NOT_CONNECTED" This applies to all devices within the corporate network. On my phone it is possible to access the wazuh dashboard though.

So it seems to be a problem within the network settings. I can ping all the wazuh components though. And port 443 seems not to be blocked by any firewall.

Would you guys have any suggestions with steps I can take to solve this problem?

thanks in advance,
Daan

Federico Pacher

unread,
Nov 14, 2022, 10:34:13 AM11/14/22
to Wazuh mailing list
Hi there,

Could you please give me more details about your environment:
- What OS are you using for your Wazuh element.
- What kind of deployment did you implement.
- Is this problem recurrent with Firefox?

Checking this error "ERR_SOCKET_NOT_CONNECTED" on the internet, here,  you can find some solutions to your issue.

Regards

Daan Fleuren

unread,
Nov 15, 2022, 2:26:37 AM11/15/22
to Wazuh mailing list
Hello,
  • I am using Rocky linux 9 minimal on both servers
  • I am using a distributed environment, with one server running wazuh-manager, and one serverv where both wazuh-indexer and wazuh-dashboard are running
  • This problem also occurs on firefox
I have also been researching this problem on the Internet and have come up with the same steps. All these steps do not seem to work, and since this problem occurs on all managed laptops so this does not seem to be a google chrome problem either.

Thanks for your thoughts,
Daan
Op maandag 14 november 2022 om 16:34:13 UTC+1 schreef Federico Pacher:

Federico Pacher

unread,
Nov 16, 2022, 2:49:46 PM11/16/22
to Wazuh mailing list
Hi there,

Sorry for my delay.
Unfortunately, I could not reproduce your issue in my environment because it is probably a DNS issue.
If you could not solve it yet I encourage you to write again in the google group or use the slack channel, (here is the link), so that others can help you.

Regards 
Reply all
Reply to author
Forward
0 new messages