ERROR: Cannot connect to Wazuh dashboard.

[Nash Hen]

Hi all, i'm installing Wazuh 4.14.1 on 4 vmware vm's with Ubuntu 24.04.3 LTS.

twazma01, as master, server, dashboard

twazwn01, as worker 1, indexer

twazwn02, as worker 2, indexer

twazwn03, as worker 3, indexer

Indexer cluster installed and tested sucessfully

Wazuh-server installed on twazma01installed.

wazuh-dashboard cannot connect after install

excerpt from wazuh-install.log
11/12/2025 14:55:54 DEBUG: Retrying Wazuh dashboard connection...
11/12/2025 14:55:54 ERROR: Cannot connect to Wazuh dashboard.

What can I do to successfully install the dashboard?

cheers

Nash

[Nash Hen]

Hi all, I'm installing Wazuh 4.14.1, the indexer as a multi-node cluster, and the manager and dashboard on a separate node.
Vmware vm's, Ubuntu 24.04.3 LTS 
twazma01, server dashboard
twazwn01, indexer
twazwn02, indexer
twazwn03, indexer
The indexer installation, including cluster formation and testing, was successful.
The installation of the wazuh server on twazma01 was successful, but the installation of the dashboard was not.

Excerpt from wazuh-install.log

11/12/2025 14:55:54 DEBUG: Retrying Wazuh dashboard connection...
11/12/2025 14:55:54 ERROR: Cannot connect to Wazuh dashboard.

What can I do to successfully install the dashboard?

Cheers Nash

[Stuti Gupta]

Hi Nash,

Could you please confirm whether you have run the Wazuh indexer cluster initialization command on the indexer node?
bash wazuh-install.sh --start-cluster
This command loads the new certificate information and starts the cluster.

Also, please verify that ports 443 and 9200 are open and not blocked by the firewall. on wazuh-dashboard

If everything is running smoothly, we can proceed with reinstalling the Wazuh Dashboard. First, you need to completely remove the existing dashboard by running:
apt-get remove --purge wazuh-dashboard -y

After that, reinstall the Wazuh Dashboard. Make sure to use the same dashboard node name that you specified in the certificate configuration (config.yml):
bash wazuh-install.sh --wazuh-dashboard <dashboard_node_name>

If you encounter the same error again during installation, do not exit the process. Let it continue, and in the meantime, open a browser and try accessing the Wazuh Dashboard at:
https://<wazuh-dashboard_ip>

Check whether the process restarts automatically or if the same error persists. If there is any error, please share it here.

[Nash Hen]

Addendum: Port 443 is now open...

The website https://10.0.3.152/ is now working. 
It displays the login page for the Wazuh dashboard :-)

Thanks for helping Gupta

Regards

Nash

[Nash Hen]

Hi Gupta,

btw: root[@]twazma01 defanged

Yes i've startet the indexer custer initialization successfully
Checked the cluster:
root[@]twazwn01:/home/tuser# curl -k -u admin https://10.0.3.159:9200/_cat/nodes?v
Enter host password for user 'admin':
ip         heap.percent ram.percent cpu load_1m load_5m load_15m node.role node.roles                               cluster_manager name
10.0.3.161           53          48   0    0.02    0.01     0.00 dimr      data,ingest,master,remote_cluster_client -               twazwn03
10.0.3.159           34          48   0    0.00    0.00     0.00 dimr      data,ingest,master,remote_cluster_client -               twazwn01
10.0.3.160           42          37   0    0.03    0.03     0.00 dimr      data,ingest,master,remote_cluster_client *               twazwn02

Port 443 / 9200 should be open, but I'll check it again.

removed with apt-get remove --purge wazuh-dashboard -y

dashboard name in config.yml - twazma01
installed with  bash wazuh-install.sh --wazuh-dashboard twazma01 -v

//
root[@]twazma01:/home/tuser# bash wazuh-install.sh --wazuh-dashboard twazma01 -v
15/12/2025 12:10:58 DEBUG: Checking root permissions.
15/12/2025 12:10:58 DEBUG: Checking sudo package.
15/12/2025 12:10:58 INFO: Starting Wazuh installation assistant. Wazuh version: 4.14.1
15/12/2025 12:10:58 INFO: Verbose logging redirected to /var/log/wazuh-install.log
15/12/2025 12:10:58 DEBUG: APT package manager will be used.
15/12/2025 12:10:58 DEBUG: Checking system distribution.
15/12/2025 12:10:58 DEBUG: Detected distribution name: ubuntu
15/12/2025 12:10:58 DEBUG: Detected distribution version: 24
15/12/2025 12:10:58 DEBUG: Installing check dependencies.
OK:1 http://archive.ubuntu.com/ubuntu noble InRelease
OK:2 http://archive.ubuntu.com/ubuntu noble-updates InRelease
OK:3 http://archive.ubuntu.com/ubuntu noble-backports InRelease
OK:4 http://security.ubuntu.com/ubuntu noble-security InRelease
Paketlisten werden gelesen…
15/12/2025 12:11:03 DEBUG: Checking Wazuh installation.
15/12/2025 12:11:03 DEBUG: There are Wazuh remaining files.
15/12/2025 12:11:04 DEBUG: There are Filebeat remaining files.
15/12/2025 12:11:04 DEBUG: Checking system architecture.
15/12/2025 12:11:04 DEBUG: System architecture: x86_64
15/12/2025 12:11:04 INFO: Verifying that your system meets the recommended minimum hardware requirements.
15/12/2025 12:11:04 DEBUG: CPU cores detected: 4
15/12/2025 12:11:04 DEBUG: Free RAM memory detected: 7940
15/12/2025 12:11:04 DEBUG: Checking previous certificate existence.
15/12/2025 12:11:05 INFO: Wazuh web interface port will be 443.
15/12/2025 12:11:05 DEBUG: Checking ports availability.
OK:1 http://security.ubuntu.com/ubuntu noble-security InRelease
OK:2 http://archive.ubuntu.com/ubuntu noble InRelease
OK:3 http://archive.ubuntu.com/ubuntu noble-updates InRelease
OK:4 http://archive.ubuntu.com/ubuntu noble-backports InRelease
Paketlisten werden gelesen…
15/12/2025 12:11:07 DEBUG: Installing prerequisites dependencies.
15/12/2025 12:11:09 DEBUG: Checking curl tool version.
15/12/2025 12:11:09 DEBUG: Adding the Wazuh repository.
gpg: keyring '/usr/share/keyrings/wazuh.gpg' created
gpg: key 96B3EE5F29111145: public key "Wazuh.com (Wazuh Signing Key) <sup...@wazuh.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1
deb [signed-by=/usr/share/keyrings/wazuh.gpg] https://packages.wazuh.com/4.x/apt/ stable main
Holen:1 https://packages.wazuh.com/4.x/apt stable InRelease [17,3 kB]
OK:2 http://archive.ubuntu.com/ubuntu noble InRelease
OK:3 http://security.ubuntu.com/ubuntu noble-security InRelease
Holen:4 https://packages.wazuh.com/4.x/apt stable/main amd64 Packages [49,4 kB]
OK:5 http://archive.ubuntu.com/ubuntu noble-updates InRelease
OK:6 http://archive.ubuntu.com/ubuntu noble-backports InRelease
Es wurden 66,6 kB in 0 s geholt (178 kB/s).
Paketlisten werden gelesen…
15/12/2025 12:11:11 INFO: Wazuh repository added.
15/12/2025 12:11:11 DEBUG: Extracting Wazuh configuration.
15/12/2025 12:11:11 DEBUG: Reading configuration file.
15/12/2025 12:11:11 DEBUG: Checking if 10.0.3.159 is private.
15/12/2025 12:11:11 DEBUG: Checking if 10.0.3.160 is private.
15/12/2025 12:11:11 DEBUG: Checking if 10.0.3.161 is private.
15/12/2025 12:11:11 DEBUG: Checking if 10.0.3.152 is private.
15/12/2025 12:11:11 DEBUG: Checking if 10.0.3.159 is private.
15/12/2025 12:11:11 DEBUG: Checking if 10.0.3.160 is private.
15/12/2025 12:11:11 DEBUG: Checking if 10.0.3.161 is private.
15/12/2025 12:11:11 DEBUG: Checking if 10.0.3.152 is private.
15/12/2025 12:11:12 DEBUG: Checking node names in the configuration file.
15/12/2025 12:11:12 INFO: --- Wazuh dashboard ----
15/12/2025 12:11:12 INFO: Starting Wazuh dashboard installation.
Paketlisten werden gelesen… Abhängigkeitsbaum wird aufgebaut… Statusinformationen werden eingelesen… Die folgenden NEUEN Pakete werden installiert: wazuh-dashboard 0 aktualisiert, 1 neu installiert, 0 zu entfernen und 3 nicht aktualisiert. Es müssen 193 MB an Archiven heruntergeladen werden. Nach dieser Operation werden 1.036 MB Plattenplatz zusätzlich benutzt. Ign:1 https://packages.wazuh.com/4.x/apt stable/main amd64 wazuh-dashboard amd64 4.14.1-1 Ign:1 https://packages.wazuh.com/4.x/apt stable/main amd64 wazuh-dashboard amd64 4.14.1-1 Holen:1 https://packages.wazuh.com/4.x/apt stable/main amd64 wazuh-dashboard amd64 4.14.1-1 [193 MB] Es wurden 193 MB in 5 s geholt (37,4 MB Running kernel seems to be up-to-date. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host.
15/12/2025 12:11:43 DEBUG: Checking Wazuh installation.
15/12/2025 12:11:43 DEBUG: There are Wazuh remaining files.
15/12/2025 12:11:44 DEBUG: There are Filebeat remaining files.
15/12/2025 12:11:45 DEBUG: There are Wazuh dashboard remaining files.
15/12/2025 12:11:45 INFO: Wazuh dashboard installation finished.
15/12/2025 12:11:45 DEBUG: Configuring Wazuh dashboard.
15/12/2025 12:11:45 DEBUG: Copying Wazuh dashboard certificates.
15/12/2025 12:11:45 DEBUG: Wazuh dashboard certificate setup finished.
15/12/2025 12:11:45 INFO: Wazuh dashboard post-install configuration finished.
15/12/2025 12:11:45 INFO: Starting service wazuh-dashboard.
Created symlink /etc/systemd/system/multi-user.target.wants/wazuh-dashboard.service → /etc/systemd/system/wazuh-dashboard.service.
15/12/2025 12:11:45 INFO: wazuh-dashboard service started.
15/12/2025 12:11:45 DEBUG: Setting Wazuh indexer cluster passwords.
15/12/2025 12:11:45 DEBUG: Checking Wazuh installation.
15/12/2025 12:11:46 DEBUG: There are Wazuh remaining files.
15/12/2025 12:11:47 DEBUG: There are Filebeat remaining files.
15/12/2025 12:11:48 DEBUG: There are Wazuh dashboard remaining files.
15/12/2025 12:11:49 DEBUG: Restarting wazuh-dashboard service...
15/12/2025 12:11:50 DEBUG: wazuh-dashboard started.
15/12/2025 12:11:50 DEBUG: Changing API passwords.
15/12/2025 12:12:50 INFO: Initializing Wazuh dashboard web application.
15/12/2025 12:13:00 DEBUG: Retrying Wazuh dashboard connection...
15/12/2025 12:13:10 DEBUG: Retrying Wazuh dashboard connection...
15/12/2025 12:13:20 DEBUG: Retrying Wazuh dashboard connection...
15/12/2025 12:13:30 DEBUG: Retrying Wazuh dashboard connection...
15/12/2025 12:13:40 DEBUG: Retrying Wazuh dashboard connection...
15/12/2025 12:13:50 DEBUG: Retrying Wazuh dashboard connection...
15/12/2025 12:14:00 DEBUG: Retrying Wazuh dashboard connection...
15/12/2025 12:14:11 DEBUG: Retrying Wazuh dashboard connection...
15/12/2025 12:14:21 DEBUG: Retrying Wazuh dashboard connection...
15/12/2025 12:14:31 DEBUG: Retrying Wazuh dashboard connection...
15/12/2025 12:14:41 DEBUG: Retrying Wazuh dashboard connection...
15/12/2025 12:14:51 DEBUG: Retrying Wazuh dashboard connection...
15/12/2025 12:14:51 ERROR: Cannot connect to Wazuh dashboard.
^C
Do you want to remove the ongoing installation?[Y/N]n
root[@]twazma01:/home/tuser#
//

Accessed the dashboard at https://1.0.3.152/
Message on the browser:  Wazuh dashboard server is not ready yet

excerpt of systemctl status wazuh-dashboard.service:
● wazuh-dashboard.service - wazuh-dashboard
     Loaded: loaded (/etc/systemd/system/wazuh-dashboard.service; enabled; preset: enabled)
     Active: active (running) since Mon 2025-12-15 12:34:48 UTC; 19s ago
   Main PID: 11180 (node)
      Tasks: 11 (limit: 9432)
     Memory: 218.6M (peak: 219.0M)
        CPU: 5.399s
     CGroup: /system.slice/wazuh-dashboard.service
             └─11180 /usr/share/wazuh-dashboard/node/bin/node --no-warnings --max-http-header-size=65536 --unhandled-rejections=warn /usr/share/wazuh-dashboard/src/cli/dist

regards
Nash

Stuti Gupta schrieb am Montag, 15. Dezember 2025 um 06:21:04 UTC+1:

[Stuti Gupta]

Please don't stop the processes in between.

If you see the error 

15/12/2025 12:14:51 DEBUG: Retrying Wazuh dashboard connection...
15/12/2025 12:14:51 ERROR: Cannot connect to Wazuh dashboard.

Let it continue, and in the meantime, open a browser and try accessing the Wazuh Dashboard at:
https://<wazuh-dashboard_ip>

Then see if the process restarted itself and connected 

Even after this, you see the error the share the wazuh-indexer logs and wazuh-dashboard as well:
journalctl -u wazuh-dashboard | grep -i -E "error|warn"
cat /var/log/wazuh-indexer/wazuh-cluster.log | grep -i -E "error|warn"

[Nash Hen]

The Wazuh dashboard is accessible and i'm able to login.

When logged in i'm landing on Server Api site with status offline and Message "Could not select any API entry".

Logging to the server API cli seems ok:
TOKEN=$(curl -u wazuh-wui:wazuh-wui-password -k -X POST "https://localhost:55000/security/user/authenticate?raw=true")
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   404  100   404    0     0   1057      0 --:--:-- --:--:-- --:--:--  1060

curl -k -X GET "https://localhost:55000/?pretty=true" -H "Authorization: Bearer $TOKEN"
{
   "data": {
      "title": "Wazuh API REST",
      "api_version": "4.14.1",
      "revision": "rc2",
      "license_name": "GPL 2.0",
      "license_url": "https://github.com/wazuh/wazuh/blob/v4.14.1/LICENSE",
      "hostname": "twazma01",
      "timestamp": "2025-12-17T10:43:00Z"
   },
   "error": 0

/usr/share/wazuh-dashboard/data/wazuh/config/wazuh.yml is set to:
hosts:
  - default:
      url: https://localhost
      port: 55000
      username: wazuh-wui
      password: wazuh-wui-password
      run_as: false

restarted the wazuh-dashboard and wazuh-manager service

still no API Connect

[Nash Hen]

Found the misconfiguration in wazuh.yml
changed the url to manager ip

Now API server is online and connected.

There is only one error checking updates
Error in CTI service request: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1017)