One-ClickGitHub
Home / Documentation / Node.js Applications
Applications

Node.js Applications

Deploy a Node.js app with its own service and reverse proxy, then manage updates, runtime versions, HTTPS and backups from the terminal.

One-Click documentation · Step-by-step guide

Create an Application

one-click --nodejs-create

Choose a domain and NGINX or Apache, then deploy a starter application or your Git project as offered by the installer. One-Click configures an application account, Node.js runtime, service and local proxy port. Confirm the landing page or your own app responds before changing DNS or sharing the site.

Check your installed version

Menu options can differ between One-Click releases. The expanded options described below require a release that includes them; use the menu on your host to check which actions are available.

Open the Management Menu

one-click --nodejs-admin

Select your site, then choose an action. 0 takes you back. Option 12 opens backup/restore; newly added management options begin at 13.

1–5 · Services and logsStart, stop, restart, inspect status and follow application logs.
6–11 · Site administrationEnable at boot, check permissions, view the service file, edit environment settings, open the app directory or delete an app.
12 · Backup / RestoreSave and restore application files using the dedicated Node.js submenu.
13 · Update / RedeployUpdate a Git deployment and run the chosen install/build sequence, with rollback attempts on failure.
14 · Change Node.js versionChange the isolated runtime version for the selected app.
15 · Application health checksCheck HTTP responsiveness and set the path used for health checks.
16 · Startup commandChange how your application starts under systemd.
17 · SSL / HTTPSView certificate details, retry Let's Encrypt and inspect HTTPS/HSTS responses.
18 · DependenciesReinstall application packages and rebuild if required.
19 · Logs and historyInspect log rotation and restart history.

HTTPS and Public Access

Node.js applications are normally served through NGINX or Apache while the Node.js process listens on a local port. HTTPS setup uses One-Click's shared Let's Encrypt workflow; it is not a separate Node.js certificate system. Confirm your domain, DNS and challenge path are ready before issuing a certificate.

Updating Your App Safely

  1. Back up your app and keep a copy of important environment values separately.
  2. Confirm the service runs and passes its health check before changing it.
  3. Use option 13 for a deployment update or 18 for dependencies only.
  4. Check status, logs, HTTP response and the public proxy after each change.

Rollback attempts do not replace a tested restore procedure, especially when an update changes external databases or stored files.

Troubleshooting

If systemd is active but the site fails to load, check the health-check endpoint, application port, startup command, proxy configuration and HTTPS response. A running service alone does not confirm the website is healthy.

← All documentationTroubleshooting →