It also helps to be able to monitor from my personal network because the server to monitor tends to ban the office ip for brute force reasons which is basically 20 failed logins of any service (account, email, website).Ĭritical/pki: Cannot connect to host ‘ ’ on port ‘5665’ However the master doesnt know its domain despite setting it in the common name since it applies to the public ip. Hi yes, The master is sitting behind a NAT on a raspberry pi and i have port forwarded. It would be much easier to have icinga web on the client but its not like i can make it use lsphp7.4 and litespeed that have been configured as the default httpd/php even via command line, it still wants its php packages and apache. So far icinga2 has been a 2 week headache, i’ve been trying to push for monitoring of load so we dont overfill a webserver but it has not gone well with management because of the current time its been taking to set it up. Icingaweb2 is running well on the server (raspberry pi) and i checked that icinga2 is running as well with the port opened and port forwarded by the router. I’ve been following the guides but so far it hasnt helped. Everytime i try to connect them at the last step using the node wizard on the client i get:Ĭritical/pki: Cannot connect to host ‘ ’ on port ‘5665’Ĭritical/cli: Peer did not present a valid certificate. So i set up icinga on a raspberry pi within LAN to monitor it. Hi i’ve been trying to run the node wizard to connect nodes for monitoring, because the client is running a webserver that isnt compatible with icinga (icinga is hardcoded for a particular setup) and i dont want to disturb anything already running.

Ubuntu port forwarding wizard