I've just done an install using the "Perfect Server Automated ISPConfig 3 Installation on Debian 11 and Debian 12..." tutorial on a Debian 12 server. All seems to have gone basically good except for a couple of minor things... I've noticed that in the Monitor menu if I try to click on Monit or Munin they come up with a "No Monit URI defined" or "No Munin URI defined" error... how can I correct that? And somehow when I was doing the install of ISPConfig I missed the "-monit-alert-email=..." parameter on the installer . What do I manually need to add to the monit configs to replicate whatever that parameter would have done?
I think the following tutorials should work to get munin and monit up and running. https://www.howtoforge.com/how-to-install-munin-monitoring-tool-on-debian-12/ https://www.howtoforge.com/how-to-install-monit-monitoring-tool-on-ubuntu-22-04/ ( should work fine on Debian too ) Regarding your other question, it probably just would have configured an email address in the monit.d config. https://mmonit.com/monit/documentation/monit.html#Setting-an-alert-recipient
System > Server config. But as @ahrasis mentioned, modern web browser clock accessing them in the iSPConfig GUI. Therefore, we do not configure that option as it won't work anyway in current browsers.
It is fixable though. Either by configuring a reverse proxy, add exceptions to the browser, x-frame-options/csp header. But having it run using reverse-proxy as ispapp probably would be the way to go as it would allow to configure measurements while having monit running listening on localhost. But this is probably on the roadmap, haven't checked. Otherwise, why not? It would require a webserver for munin on multi-servers though I guess, or mount the munin static contents on primary system :?
It's not on the roadmap, as there is no real benefit of showing the contents inside an iframe of the ISPConfig GUI; I even considered removing them from the UI or replacing the iframe with a simple link that opens the app in a new browser window.
I forgot about munins capabillity to connect to remote servers ha, no webserver for that needed. But I agree, just open a new window would be an easy fix and reduces complexity/workload. I think in the early days I just added a domain and configured proxy on that, When used to use the hostname as domain to get the letsencrypt. But yes.
