Installation
AllInOneMonitor is a plain PHP application: upload, open the installer, add one cron line. It runs on a single shared-hosting (cPanel) account and scales out to several servers (see Deployment).
Requirements
- PHP 8.1 or newer with the extensions
pdo_mysql,curl,openssl,json,mbstring;zipis optional (backups). - MySQL 5.7+ / MariaDB 10.3+ (utf8mb4).
- Apache with
mod_rewrite(the shipped.htaccess) or nginx (see Deployment). Everything that is not a real file is routed toindex.php. - A cron that can run every minute, or an external cron service that can call a URL every minute.
- Optional: shell functions (
shell_exec) for ICMP ping monitors; without them ping monitors fall back to a TCP connection. includes/,storage/anduploads/writable by the web user.
Fresh install
- Upload the release ZIP and extract it into the document root (or a sub-folder:
/monitorworks too). - Open
https://your-domain/install.php. Step 1 checks the requirements and asks for the database (host, port, name, user, password), the site URL and name, the administrator (name, e-mail, password of 8+ characters) and, optionally, a licence key from LCPanel (https://lcpanel.com). - Step 2 writes
includes/config.php(database, site URL, name and a freshly generated 64-characterAIM_SECRET_KEY), creates the tables, seeds the defaults (settings, plans, thecoreprobe, e-mail templates, public pages, the 2.0.0 changelog), creates the admin account with its organisation and writesinstalled.lock. - Step 3 shows the cron line and the web-cron URL. Add the cron (below), sign in, and delete
install.php.
The lock file stops the installer from running again; removing it lets you re-run the installer against the same database without dropping anything.
config.php
define('DB_HOST', 'localhost');
define('DB_PORT', 3306);
define('DB_NAME', 'allinonemonitor');
define('DB_USER', '...');
define('DB_PASS', '...');
define('SITE_URL', 'https://monitor.example.com'); // no trailing slash
define('SITE_NAME', 'AllInOneMonitor');
define('AIM_SECRET_KEY', '64 hex characters'); // encrypts credentials, hashes tokens - back it up
define('AIM_DEBUG', false); // true shows errors on screen; never on a live site
define('AIM_TIMEZONE', 'UTC');
define('AIM_ALLOW_PRIVATE_TARGETS', false); // let monitors reach LAN addresses
A release ZIP never contains config.php, so an upgrade never overwrites yours. The site URL can also be changed later in Admin → Settings (the setting wins over the constant). Keep AIM_SECRET_KEY with your backups: without it every stored credential and token is unreadable (see Backup & recovery).
Cron
Shared hosting (cPanel → Cron Jobs), every minute:
* * * * * /usr/local/bin/php /home/USER/public_html/cron/cron.php >/dev/null 2>&1
Each run queues the due checks, works the queue for about 50 seconds (adjustable in Settings) and leaves; a lock prevents overlapping runs. If your host offers no shell cron, call the web cron from any external cron service every minute:
https://monitor.example.com/cron/cron.php?key=<cron key shown on Admin → System health>
Admin → System health shows when the cron last ran; the dashboard warns when it is late.
Upgrading to a new version
- Back up the database and
includes/config.php(Backup & recovery). - Extract the new ZIP over the folder (nothing in
includes/config.php,uploads/orstorage/is in the ZIP). - Open
https://your-domain/db_update.phponce, signed in as admin (or runphp db_update.phpfrom the shell). It creates missing tables and columns and runs each one-time step once; the steps are recorded, so running it again is harmless. - Check Admin → System health.
Upgrading from the old monitor script
The 2.0.0 installer and updater understand the database of the previous "Advanced Monitor / ServerWatch" script. Nothing is dropped.
- Back up the old database and its
includes/config.php. - Extract the 2.0.0 ZIP over the old folder, keeping
includes/config.php(the old constants still work; SMTP constants are moved into the settings by the updater). - If
installed.lockdoes not exist, openinstall.php, point it at the same database and enter the admin e-mail: an existing user with that e-mail becomes the admin, its password is set to the one you enter, and the installer detects the upgrade. - Open
db_update.phponce. It renamesmonitor_logstomonitor_results, converts the tables to utf8mb4, widens the old enums, adds indexes, seeds the new defaults, creates a personal organisation for every user (with a subscription for users who had a paid package), moves monitors, incidents, channels and tags into those organisations, encrypts stored passwords and channel configurations, rolls the result history up per day and records every step.
What changes for old users:
- The old addresses redirect:
dashboard.php,login.php,register.phpanduser/*.phpgo to the new panel;public/monitor.php,public/embed.php,public/heartbeat.phpandapi/status.phpkeep working at the old addresses with the same tokens. - Heartbeat tokens, public monitor tokens, badge and embed links stay the same.
- Users keep their e-mail and password; existing users are treated as verified. Each user now owns an organisation named after them.
- Monitors keep their settings; the old
max_retriesbecomes confirmations, the old minutes interval becomes seconds,httpsmonitors becomehttpwith the SSL check on. - Alert channels keep working; their settings are now stored encrypted.
- Packages keep their prices and counts; new limits get sensible defaults the admin can adjust under Plans.
Licence
The installation talks to the licence server LCPanel at https://lcpanel.com (product code allinonemonitor; the address can be changed under Admin → Licence, an old license.faruk.bd address is switched to https://lcpanel.com by itself). Enter the key in the installer or later under Admin → Licence; the state and addons are shown there and re-checked in the background. Keys are issued in your client area at https://lcpanel.com/user/licenses.php; product page, changelog and documentation are at https://lcpanel.com/products/allinonemonitor.
The updater page (2.1.3): db_update.php first shows a pre-flight page - the installed and the new version, the tables, columns and one-time steps it will add, a backup reminder with a ready mysqldump command and system checks (PHP version and extensions, database connection, writable storage/). Nothing changes until you press Run the update; then every step is listed with its result and time, and Copy log copies the same lines the command line prints. A failed step is shown in red with its error and runs again next time.
Upgrading to 2.1.2: the update moves the installation from the old license.faruk.bd to https://lcpanel.com and discards the old licence key (keys from the old server no longer work). After db_update.php, sign in as admin, open Admin → Licence and activate a new key from lcpanel.com.
When lcpanel.com is down: an active licence keeps working with no time limit (site, panels, admin, modules, limits). The admin shows a small "Licence server unreachable" notice and the check is retried automatically (1 h, 2 h, 4 h … up to the normal interval). Activating or changing a key and releasing the domain need the server and ask you to try again later. Only an explicit answer from the server (invalid, suspended, revoked, expired, another domain) changes the licence.
একটি ক্লিক আমাদের এই ডকস উন্নত করতে সাহায্য করে।

