Call

Lofingo Cloud

Install the full VPS control panel from one command.

Lofingo Cloud turns a clean VPS into a live dashboard with a backend API, React panel, Nginx reverse proxy support, database tooling, Git flows, and systemd-managed services.

fresh-vpsroot shell
curl -fsSL https://cloud.lofingo.com/panel/install.sh | sudo bash

Run this on a clean Ubuntu or Debian VPS. At the end, the installer prints the login URL, default admin email, and generated password.

Dashboardhttp://VPS-IP:3000
APIhttp://VPS-IP:3000/api
Runtimesystemd services
Releasestable channel

01

VPS requirements

Supported OS

Ubuntu 22.04+, Ubuntu 24.04+, Debian 12+, or compatible systemd Linux.

Network

Ports 80, 443, and 3000 should be free before installation starts.

Access

Run with root or sudo privileges on a clean VPS.

Resources

Minimum 1 vCPU, 1 GB RAM, and 10 GB disk. 2 GB RAM is recommended.

02

Fresh install

The installer is designed to fail before making major changes if the VPS is not clean enough. If a required port is busy, it prints the process using the port and exits instead of continuing with a broken setup.

curl -fsSL https://cloud.lofingo.com/panel/install.sh | sudo bash
  1. Detect OS, package manager, firewall, and architecture.
  2. Stop early with a clean error if ports 80, 443, or 3000 are already in use.
  3. Install required packages such as Node.js, Nginx, MariaDB, curl, tar, and systemd tools.
  4. Download the stable release manifest and verify the release artifact checksum.
  5. Create the application directory, database, generated secrets, and environment file.
  6. Install backend and frontend dependencies, build the dashboard, and run database migrations.
  7. Create systemd services for the API and dashboard so the panel starts after reboot.
  8. Open firewall access for 80, 443, and 3000 when ufw or firewalld is available.

03

What gets installed

Panel Workspace

  • Browser file manager
  • Code editor
  • Upload/download tools
  • Live server health

Deployment

  • Systemd app runtime
  • Deployment logs
  • Environment management
  • Restart and status actions

Domains

  • Nginx reverse proxy
  • Domain mapping
  • Port detection
  • SSL-ready structure

Databases

  • MariaDB/MySQL tools
  • PostgreSQL tools
  • Migration-ready schema
  • Local DB credentials

Git

  • Repository status
  • Pull and commit flows
  • Branch visibility
  • Auto-pull friendly backend

Access

  • Default bootstrap admin
  • HTTP-only auth cookies
  • User roles
  • Two-factor ready account flow

04

Installed server paths

PathUse
/opt/lofingo-cloudApplication source, backend, dashboard build, and runtime files.
/etc/lofingo-cloud/panel.envGenerated production environment configuration.
/var/backups/lofingo-cloudUpdate backups and rollback material.
/etc/systemd/systemSystem service units for API and dashboard runtime.

05

Update management

Installed servers use the stable channel to discover the latest release. Each version ships with a manifest, checksum file, and release bundle. The updater downloads the manifest, checks the tarball checksum, creates a backup, runs migrations, and restarts systemd services.

stable.jsonmanifest.jsontar.gzmigrationsrestart
https://cloud.lofingo.com/panel/install.shFresh VPS bootstrap script.
https://cloud.lofingo.com/panel/update.shPublic update bootstrap script.
https://cloud.lofingo.com/panel/channels/stable.jsonStable channel pointer used by installers and updaters.
https://cloud.lofingo.com/panel/releases/v1.0.16/manifest.jsonVersion metadata, checksums, and migration information.
https://cloud.lofingo.com/panel/releases/v1.0.16/lofingo-cloud-v1.0.16.tar.gzVersioned release bundle.

06

Management commands

lofingo-cloud status

Show API, dashboard, Nginx, database, and port status.

lofingo-cloud logs

Tail the Lofingo Cloud systemd logs.

lofingo-cloud restart

Restart the backend API and dashboard services.

lofingo-cloud update

Fetch the stable channel and apply a verified update.

07

Troubleshooting

Port 3000 is not opening

Check cloud-provider firewall rules first, then run lofingo-cloud status on the VPS.

Installer stopped on port check

Another app is already using 80, 443, or 3000. Stop that process or use a clean VPS before rerunning the installer.

Release URL returns 404

Publish the R2 release and confirm https://cloud.lofingo.com/panel/install.sh and the stable channel are live.

08

Security notes

  • The installer generates local secrets and stores them outside the web root.
  • Authentication uses HTTP-only cookies in the dashboard backend.
  • Release tarballs are verified by SHA-256 before installation or update.
  • Rotate the printed default admin password immediately after first login.
  • Keep cloud-provider firewall rules limited to the ports you actually need.