Install the Cloudmon Controller using the Cloudmon installation script, register it, and verify that all required services are running successfully using the Cloudmon CLI.
Cloudmon can be deployed as a single-host installation for small environments, or as a distributed installation where the Controller and database are hosted on separate servers for production use. The sections below walk through both paths, from downloading the installation script to verifying that the deployment is healthy.
| Requirement | Details |
|---|---|
| Server sizing and OS | Verify that the server meets the requirements specified in System Requirements. |
| Deployment model | Determine whether you are deploying Cloudmon as Single Network, Distributed, DMZ, or MSP. See Deployment Models. |
| Root privileges | Root or sudo access is required to run the installation script. |
| Internet access | Internet connectivity is required because the installation script downloads the required packages and dependencies. |
The script installs the required database components and configures the default database settings.
Install and configure the database before installing the Controller. The Controller installation requires a reachable database.
On the Controller server, download the installation script if it is not already available, then run:
<controller-ip> with the IP address or hostname of your Controller: https://<controller-ip>The email address entered during registration becomes the login username and has to be valid.
After installing all required components, perform the following checks on each host.
The installation is considered successful when the following conditions are met:
cloudmon check reports the system and required services as healthy.cloudmon status shows the required services as running.https://<controller-ip> and the login page opens successfully.| Issue | Possible Cause | Recommended Action |
|---|---|---|
| Installation fails partway through | Missing prerequisite or database was not installed before the Controller | Run cloudmon check. Review the installation logs using cloudmon log server cloudmon.log. See Where can I find the logs if the installation fails? |
| 502 Bad Gateway | Incorrect database credentials or Controller service is not running | Verify the database configuration in /usr/local/cloudmon/server/.env, run cloudmon restart, and verify using cloudmon status. |
| Default NGINX welcome page is displayed | NGINX is serving its default site instead of Cloudmon | Run cloudmon show open-ports, remove /etc/nginx/sites-enabled/default if applicable, and reload NGINX. See Cloudmon UI shows "Welcome to nginx" |
| A service is stopped or repeatedly fails | Service failed to start or crashed after a configuration change | Run cloudmon status, followed by cloudmon restart. If the issue persists, enable debug logging using cloudmon debug enable server and check the logs using cloudmon log server cloudmon.log. |
| Disk usage is increasing rapidly | Data retention, insufficient disk capacity, or debug logging is enabled | Check debug logging using cloudmon debug status server. Disable debug logging when it is no longer required. See Resolve disk space issues |
When contacting Support, include:
cloudmon check output