After installing the Cloudmon Controller, complete the registration process to set up the primary administrator account and configure the organization. The user created during registration becomes the Super Admin.
| Field | Description |
| First Name | First name of the primary administrator. |
| Last Name | Last name of the primary administrator. |
| Contact Email ID | Email address of the administrator. This becomes the username for all future logins and is case-sensitive. It replaces "admin" from the temporary credentials. |
| Contact Phone Number | Phone number of the primary administrator. |
| New Password | The permanent password for this account. This replaces the temporary "admin" password. |
| Company Name | The name of the organization. In MSP deployments, this becomes the MSP organization name in the controller. |
After saving, a confirmation email is sent to the registered email address. All future logins use the registered email as the username.
After registration, check the address and port used to access the controller and to send data to it. Servers and devices that send data to Cloudmon must be able to reach the controller at this address and port. If the address is a private IP address, only devices on that network can reach it.
| Field | Description |
| Web access URL | Required. The address used to access the controller. Include http:// or https://. Click Copy to copy the address. |
| Data ingestion port | Required. The port used to send data to the controller. Use a port from 1 to 65535. |
The same page also has the SSL Certificate, Password Policy and Allowed IPs tabs.
You can open a command line on the controller from your browser, without a separate SSH client. Commands run as the user the controller service runs as (usually root), with that user's login profile. Who connected, when, and your comment are recorded in the audit log, and every command line is written to the controller log.
| Field | Description |
| Session length | Required. How long the session lasts: 15 minutes, 30 minutes, 1 hour or 2 hours. You can extend it while connected, up to 2 hours in total. |
| Comment | Required. Why you are connecting, for example, to check disk usage under /var/log/cloudmon. |
Click the history icon in the window to open Controller terminal sessions, which lists the sessions opened on the controller, with when each started, the user, the length, the connection, the result, and the comment.
Super Admin: The user created during registration is designated as the Super Admin of the controller. This account has full read and write access across all features and settings and cannot be deleted. All fields except the Email ID can be edited after registration.
MSP deployments: The organization name registered during this step is automatically added as the MSP organization in Cloudmon. Only user accounts assigned to this organization will be able to receive alarm and device-related notifications across all managed customers.
| Symptom | Likely Cause | Fix |
| Registration page is not shown after logging in with admin/admin. | The Controller was already registered in a previous session, or the browser has a cached login state. | Clear browser cache and cookies, then reload the Controller URL. If registration was already completed, log in with the email and password set during registration. Contact Cloudmon Support if credentials are unknown. |
| Confirmation email not received after clicking Save. | Email was filtered to spam, or the address entered contained a typo. | Check the spam or junk folder. If not found within 5 minutes, confirm the email address was entered correctly. Contact Cloudmon Support to resend the confirmation if needed. |
| Login fails after registration is complete. | The registered email address is case-sensitive and may have been entered differently at login. | Enter the email exactly as typed during registration, matching letter case. If the password was forgotten, use the Reset Password option on the login screen. |