Skip to the products
LCPanelLicence Center Panel

Requirements and installation

PHP and database versions, HTTPS, uploading to cPanel, creating the database, the five installer steps, the cron job, updating later, the database update page, the .htaccess rules and the 403 fix.

Getting started Updated 6 Nov 2026 2 / 26

This chapter takes you from an empty hosting account to a working site. It uses cPanel, which most shared hosts offer. Any PHP host works the same way.

1. What the server needs

ItemNeeded
PHP7.4 or newer. 8.x is recommended.
DatabaseMySQL 5.7 or newer, or MariaDB 10.3 or newer
PHP extensionspdo_mysql, curl, json, mbstring, openssl. gd and zip are recommended.
Web serverApache with .htaccess, LiteSpeed, or Nginx with the same rewrite rule
HTTPSRequired. Browsers allow the camera and microphone only on HTTPS pages.
CronOne job every 5 minutes
OptionalA coturn TURN server for people behind strict firewalls

The installer checks the PHP version and extensions on its first screen and tells you what is missing.

Sizing in short: a small site with a handful of rooms runs on any shared plan. The load comes from many people polling the signalling endpoint at the same moment. If you expect many rooms at once, use a VPS and read the long-polling note in Meeting settings.

2. Get HTTPS first

  1. In cPanel open SSL/TLS Status.
  2. Select your domain and press Run AutoSSL. Wait until the lock is green.
  3. Open https://your-domain/ and check that the browser shows a lock.

Do this before the installer. A meeting room on plain HTTP cannot reach the camera.

3. Upload the files

  1. Download the AIOMeeting ZIP from your account at lcpanel.com.
  2. In cPanel open File Manager and go to public_html (or the folder of your sub-domain).
  3. Press Upload, choose the ZIP, then Extract it there. The folder must hold index.php, install.php, rtc.php and the .htaccess file.
  4. Make sure hidden files are shown (Settings, Show Hidden Files) so you can see .htaccess.

A sub-folder install, such as https://example.com/meet/, works too. The script finds its own base path.

4. Create the database

  1. In cPanel open MySQL Databases.
  2. Create a database, for example cpuser_meet.
  3. Create a user with a strong password.
  4. Add the user to the database with All Privileges.
  5. Write down the database name, user and password. cPanel adds your account name as a prefix.

5. Run the installer

Open https://your-domain/install.php. It has five steps.

  1. Requirements. Everything must be green. Press Continue.
  2. Database. Host is localhost and port 3306 on cPanel. Type the database name, user and password. Keep the table prefix am_ unless the database is shared with another script.
  3. Site and administrator. Site name, site URL (no trailing slash), contact e-mail, country, time zone, admin username, and the admin password twice (at least 8 characters). The contact e-mail is the sender address of every mail.
  4. Licence. Paste the key from lcpanel.com. It looks like AIOM-XXXX-XXXX-XXXX-XXXX and is bound to this domain. You can press Skip for now. Without a licence the admin area opens only the Licence page.
  5. Done. The page shows the admin address and the cron line.

The installer writes config.php and installed.lock. It refuses to run again after that. You may delete install.php for extra safety.

6. The cron job

Meetings need a heartbeat. Every 5 minutes the cron sends reminders, ends sessions that nobody left properly, enforces package time limits, prunes old signals and works the job queue (mails, webhooks). Hourly and daily jobs handle orders, packages, currency rates, the sitemap and housekeeping.

In cPanel open Cron Jobs and add one job with the setting Once Per Five Minutes:

/usr/local/bin/php /home/CPUSER/public_html/cron/cron.php

Replace CPUSER and the folder. If your host uses another PHP path, copy the one it shows for its other cron examples. The installer's last screen prints the exact path of your install.

If your host cannot run PHP from cron, use a web cron instead. Any service that opens a URL every 5 minutes will do:

https://your-domain/cron.php?key=YOUR_CRON_KEY

The key is under Settings, Cron in the admin panel. The page returns Invalid cron key for a wrong key.

Check it later on System and Maintenance or the Automation Log. A job that ran in the last 5 minutes shows its result there.

7. After the install

  • Sign in at /admin/login with the admin account.
  • Open Health and Security Check and fix every red line.
  • Confirm that config.php and the data/ and uploads/ folders are writable by PHP but not readable from the web.
  • Continue with First steps.

8. Updating later

An update ZIP never contains config.php, installed.lock, data/ or uploads/. Back up the files and the database, extract the ZIP over the site, then run the database update. It only adds what is missing.

The database update page

Since 1.2.0 the update has a page of its own. Sign in to the admin panel, then open https://your-domain/db_update.php (or System and Maintenance and its update button). Only an administrator with the permission to update can open it.

  1. The page shows the file version and the database version, and lists the steps that are waiting.
  2. Press Run the update.
  3. The page lists what was done, with the time each step took. Running it again is safe and does nothing new.

On the command line, php db_update.php runs the steps at once and prints a text report.

Folder rules (.htaccess)

The update ZIP carries the .htaccess files. Keep them after you extract.

  • uploads/.htaccess switches PHP off in the upload folder and refuses .php, .phtml, .phar, .sh and similar files. An uploaded file can never run as PHP.
  • The main .htaccess refuses direct requests to includes/, data/, cron/, languages/, the plugin code and the page files of admin/pages/, admin/ajax/, site/pages/ and site/ajax/. The web entry points index.php and rtc.php stay open.

403 on /admin/ (LiteSpeed and some Apache set-ups)

Before 1.2.0 the rule that protects the page files could also answer 403 for /admin/ and /admin/pages/ on LiteSpeed and some Apache set-ups. Version 1.2.0 refuses only the real PHP files of those folders. If you still see 403 on the admin address after an update, replace your .htaccess with the one from the update ZIP, make sure AllowOverride is on for the folder, and reload. See Troubleshooting.

Was this helpful?
Share this chapter