Deployments
How Hostinger records every Node.js build under Deployments in hPanel: history, per-build logs, redeploys, failed-build AI analysis, and deployment settings.
Last updated
Was this helpful?
How Hostinger records every Node.js build under Deployments in hPanel: history, per-build logs, redeploys, failed-build AI analysis, and deployment settings.
Every build of your Node.js app is recorded under Deployments in your website dashboard — history, per-build logs, redeploys, and the settings applied to future builds.
The overview card shows where your app deploys from — From pushes to your connected repo (Git), or Manually uploaded (archive) — plus the GitHub connection status and a Redeploy button.
Below it, the deployment history table:
Author
GitHub author with avatar
—
Branch
Deployed branch
—
Commit
Short hash + commit message
—
File
—
Archive filename
Time
When the build ran
When the build ran
Status
Building / Completed / Build failed
Building / Completed / Build failed
The build currently serving traffic is labeled Current. The table is searchable and paginated. Click a row for full details.
Each deployment's page shows:
State, time, and duration
Source — repository, branch, commit, and author (Git), or the uploaded file (archive)
Configuration — root directory, framework, build and output settings (default or custom), Node version
Build logs — the full log with line count; polls every few seconds while the build runs
Redeploy re-runs the build with the saved settings:
Git apps — pulls the latest code from the connected branch. History shows it as a manual deployment (no new commit).
Archive apps — rebuilds from the last uploaded archive. No re-upload needed.
Only one deployment runs at a time per site — buttons are disabled with "Another deployment is still running" until it finishes.
There is no per-commit rollback: to ship an older version, revert or reset in Git and push, or upload the older archive.
Deployments → Deployment settings edits the configuration applied to upcoming builds: framework preset, branch (Git), Node version, build command, package manager, output directory, entry file, and environment variables. Field reference: Build Settings.
Git apps — Save (applies on next push) or Save and redeploy (applies now).
Archive apps — choose Use previous files or Upload new files, then Save and redeploy.
When a build fails, the deployment is marked Build failed and Hostinger generates an AI analysis of the log — a diagnosis of what went wrong and a suggested solution — with a Fix and redeploy shortcut. Open it from the "Previous build failed. More details" link or the failed deployment's details page.
Common causes and fixes: Creating a Node.js App — Troubleshooting.
GitHub — automatic deployments on push
Build Settings — every configuration field
Runtime Logs — output from the running app, not the build
Last updated: July 22, 2026
Last updated
Was this helpful?
Was this helpful?