For a team VPS in October 2026, install Node.js with nvm, pin projects to Node 24 (the current Active LTS line), run the application with PM2, and put Nginx and SSL in front of it. Use a dedicated non-root deploy account, commit an .nvmrc file, and save PM2’s startup configuration so the service returns after a reboot. Node 26 was released on 5 May 2026 and is scheduled to become LTS on 28 October 2026; until that date, Node 24 is the safer production baseline.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
Choose the Node.js release before you install anything
Version policy matters more on a shared VPS than on a personal laptop. A team needs one documented runtime, predictable security updates, and a controlled upgrade path.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →| Version | Status in October 2026 | Recommended use |
|---|---|---|
| Node 24 | Active LTS | Production and team development now |
| Node 26 | Released 5 May 2026; scheduled for LTS on 28 October 2026 | Test in a branch or staging environment before the LTS date; plan the production move after compatibility testing |
| Node 22 | Maintenance LTS | Keep only when an existing application or dependency requires it |
| Node 20 | End-of-life since 30 April 2026 | Do not start a new production deployment on it |
The release dates above are reported by PkgPulse, Entrant Technologies and AppsTimes. Node 26’s scheduled LTS date is 28 October 2026, with maintenance planned to begin on 20 October 2027 and end of life on 30 April 2029. Treat the date as a planning milestone and verify the current Node.js release schedule when you perform the upgrade.
The Node.js project has also announced a cadence change beginning with 27.x: instead of two major releases each year, there will be one, and each release is expected to become LTS. The reported schedule puts Alpha in October 2026, Current in April 2027 and LTS in October 2027. Those dates should be checked against the official schedule before being used in a long-term support policy.
#1 Best Overall
- 12th Intel Alder Lake N95 Processor – The GMKtec G3 S Mini PC is powered by the 12th Gen Intel N95 processor with 4 cores, 4 threads, 6MB cache and a burst frequency up to 3.4GHz. Compared with N100/N5105/N5100/N5095, the N95 delivers up to 36% overall performance improvement. Perfect for routine tasks, office work, and home entertainment, this compact mini desktop is more convenient than traditional bulky PCs.
- 8GB RAM & 256GB SSD Storage – Pre-installed with 8GB DDR4 memory and a fast 256GB M.2 2242 SSD, the G3 S mini desktop offers quicker startup, smoother multitasking, and faster file transfers. Enjoy seamless performance whether you’re working on multiple applications, browsing, or streaming content.
- Rich Interfaces & Connectivity – The G3 S mini computer comes equipped with USB 3.2 (up to 10Gbps), dual HDMI 2.0 (4K@60Hz), and a 3.5mm audio jack. With support for WiFi 5, Bluetooth 5.0, and Gigabit Ethernet (RJ45 1000MbE), it connects easily with monitors, projectors, printers, office equipment, and other peripherals, making it versatile for both home and business use.
- Dual 4K Display Support – Featuring upgraded Intel UHD Graphics (up to 1000MHz), the G3 S supports 4K video playback and AV1 decoding for a smooth viewing experience. With dual HDMI outputs, you can connect two 4K@60Hz displays simultaneously, enabling efficient multitasking for work and entertainment.
- GMKTEC WARRANTY - GMKtec offers a 3-year limited warranty (1 year replacement + 2 years parts replacement) for each mini PC, starting from the date of the purchase effective on all sales starting Oct. 2026. All defects due to design and workmanship are covered. With a professional after sales team always ready to attend to your needs, you can simply relax and enjoy your mini PC
Plan the VPS for a team
Use a current Ubuntu LTS image from your VPS provider, a DNS name for the application, and a firewall that exposes only SSH and web traffic. You need an administrator account for initial server work, but the application itself should run under a separate deploy user.
- A VPS with enough CPU, memory and disk for the application, its build process, logs and database client tools.
- An SSH key for each administrator or developer who needs access; avoid sharing one private key.
- A DNS record such as
app.example.compointing to the VPS address. - Source-control access and a deployment method agreed by the team.
- A decision about where persistent data lives. Do not place a production database on the application VPS without a backup and recovery plan.
Log in as the initial administrator, update the operating system, and create the deploy account:
Free tools Windows power users keep installed
One-click scans. No signup required.
sudo apt update && sudo apt upgrade -y
sudo adduser deploy
sudo usermod -aG sudo deploy
Copy an administrator’s public key to /home/deploy/.ssh/authorized_keys, test a new SSH session as deploy, and only then consider disabling password authentication. Keep one tested administrative recovery path before changing SSH settings.
Install Node.js with nvm
Ubuntu’s apt repository is convenient, but its Node.js package can lag behind the line your project needs and does not provide an easy per-project switch. nvm installs versions per user, lets the team test upgrades side by side, and works naturally with an .nvmrc file.
-
Switch to the deploy user
su - deploy -
Install nvm
Use the current installation command from the nvm project rather than copying an old release tag. After the installer finishes, open a new shell or load the profile it changed:
command -v nvm nvm --versionIf the command is not found, start a login shell with
su - deployagain. Do not install nvm withsudo; it belongs to the user who will run Node and PM2.Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Install the LTS line and set the default
nvm install --lts nvm alias default lts/* node --version npm --versionIn October 2026, the LTS selector should resolve to Node 24. Check the printed version rather than assuming the result.
-
Pin each repository
Inside every project, create
.nvmrccontaining the team’s chosen major line, for example:24Then run
nvm installandnvm usein that directory. Commit.nvmrcto source control. The file does not automatically switch shells, so developers still need to runnvm useor configure their shell prompt to do it.
Do not mix a system-wide Node installation with the nvm installation used by PM2. A command that works for one user can fail for another because each nvm installation has its own binaries and global npm directory.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Rank #2
- 【AMD Ryzen 3 5300U CPU: Outperforms N150 & 3500U】 BOSGAME E5 mini PC is powered by the TSMC 7nm FinFET architecture AMD Ryzen 3 5300U processor (4 Cores, 8 Threads, up to 3.8GHz boost, 6MB total cache). Compared to low-end Intel N150 or 3500U chips which only have 4 single threads and throttle under load, the 5300U delivers over 30% faster multi-core speed. Run 30+ browser tabs, large Excel sheets, and Zoom meetings simultaneously without system lag.
- 【8GB DDR4 RAM & 256GB NVMe SSD Storage】 Installed with high-speed 8GB DDR4 dual-channel memory and a fast 256GB M.2 2280 SSD, eliminating slow boot times and application loading delays. To accommodate growing data requirements, the upgradeable hardware design features dual SODIMM slots that allow you to expand memory up to 64GB RAM, ensuring smooth operation during heavy multitasking.
- 【High-Capacity Dual M.2 SSD Storage Expansion】 Never worry about running out of space for your business files. In addition to the pre-installed 256GB system drive, the motherboard houses an extra empty internal M.2 2280 NVMe PCIe 3.0 slot. This allows you to easily add a second solid-state drive for up to an additional 2TB of storage capacity (upgrades not included) without needing to remove or reinstall the original operating system.
- 【Radeon 6-Core Graphics & Triple 4K Displays】 Integrated with official AMD Radeon Graphics (6 Graphics Cores, 1500 MHz frequency) for casual gaming, photo editing, and crisp 4K media decoding. Featuring 1x HDMI 2.0 port, 1x DisplayPort, and 1x Full-Function Type-C port, the E5 outputs true 4K@60Hz resolution to three monitors at once. This multi-screen setup eliminates constant window-switching for traders, programmers, and office workers.
- 【Dual 2.5GbE LAN Ports for Advanced Networking】 Experience fast wired network transmission speeds up to 2500Mbps without lagging or buffering. The integration of dual 2.5 Gigabit Ethernet ports (powered by Realtek RTL8125 controller) makes this compact computer an exceptional hardware choice for tech enthusiasts. Easily configure it into software routers, hardware firewalls (pfSense, OpnSense), home NAS servers, or local homelabs.
Prepare the application and team permissions
Keep the checked-out code and runtime owned by deploy, not by root. Create a predictable directory layout:
sudo mkdir -p /srv/myapp
sudo chown -R deploy:deploy /srv/myapp
cd /srv/myapp
git clone YOUR_REPOSITORY_URL current
cd current
nvm use
npm ci
Replace the repository value with your real source-control URL; do not put credentials in a shell history or deployment script. Use npm ci for repeatable installs from a committed lockfile. Build and test before starting the service:
npm run build
npm test
Store secrets outside Git. A root-readable environment file, a VPS secret manager, or your CI/CD secret store is safer than committing a production .env. Make the application listen on localhost, for example 127.0.0.1:3000, because Nginx will be the public listener.
Run Node.js with PM2
PM2 is a Node-oriented process manager. It keeps the application running, records logs, and can restore processes after a reboot. Install it globally as the deploy user so its executable belongs to the same nvm-managed Node installation:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsnpm install -g pm2
pm2 --version
Create an ecosystem file
Put a configuration file in the repository so every team member deploys the same process name, working directory and environment. For an application using ES modules with "type": "module" in package.json, name the PM2 configuration ecosystem.config.cjs; PM2’s automatic discovery can otherwise treat a JavaScript config as an ES module.
module.exports = {
apps: [{
name: 'myapp',
script: './server.js',
cwd: '/srv/myapp/current',
instances: 1,
autorestart: true,
watch: false,
time: true,
env: {
NODE_ENV: 'production',
PORT: 3000
}
}]
};
Use the actual entry point and deployment path. Start it from the deploy account:
cd /srv/myapp/current
pm2 start ecosystem.config.cjs
pm2 status
pm2 logs myapp
Do not enable watch on a production VPS unless you have deliberately designed for the extra file activity. For a multi-process application, choose the instance count only after checking memory use and whether the application shares state correctly.
Make the process survive a reboot
-
Generate the startup command:
pm2 startup -
PM2 prints a command containing your user, home directory and a system service path. Copy and run that exact command with
sudoas instructed.What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Save the currently running process list:
pm2 save -
Reboot during a maintenance window and verify:
sudo reboot # after reconnecting as deploy pm2 status curl http://127.0.0.1:3000
pm2 startup creates the boot integration; pm2 save records which applications should be restored. Running one without the other is a common reason an application disappears after a restart.
Put Nginx in front of Node.js
Expose Nginx on ports 80 and 443 and keep Node on localhost. This gives the team one place for TLS termination, host routing, request limits and access logs.
Rank #3
- 【1-Year Worry-Free Warranty】Your satisfaction is our priority. Glorlin provides a 1-year warranty covering any hardware malfunctions. We support returns or exchanges to ensure a 100% worry-free shopping experience. Have a question? Reach out to us through our official after-sales email for a prompt solution.
- 【Reliable Performance with Ryzen 7 Processor】Powered by AMD Ryzen 7 8745HS (8 cores, 16 threads, up to 4.9GHz), this mini pc delivers stable performance for daily workloads. Suitable for office tasks, programming, and multitasking, it works well as a ryzen mini pc for both home and business use.
- 【Radeon 780M Graphics for Media and Light Gaming】Equipped with integrated Radeon 780M graphics, this mini gaming pc supports smooth 4K video playback and handles many popular games at adjusted settings. A practical mini computer for media, editing, and casual gaming.
- 【Mini PC 16GB RAM and Fast Storage】This mini pc 16gb ram configuration includes single 16GB DDR5 memory (4800MHz,3GB is assigned to VRAM by default) and a 1TB NVMe SSD, offering quick boot times and responsive system performance. Dual M.2 slots allow storage expansion up to 4TB for growing files and projects.
- 【Quad 4K Display Support for Productivity】The mini desktop computer supports up to four 4K displays via HDMI, DisplayPort, and dual USB-C ports. Ideal for multi-screen workflows such as coding, trading, or content creation with improved efficiency.
sudo apt install nginx -y
sudo ufw allow OpenSSH
sudo ufw allow 'Nginx Full'
sudo ufw enable
Create a server block such as /etc/nginx/sites-available/myapp:
server {
listen 80;
server_name app.example.com;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}
Enable and validate it:
sudo ln -s /etc/nginx/sites-available/myapp /etc/nginx/sites-enabled/myapp
sudo nginx -t
sudo systemctl reload nginx
Point DNS at the VPS before requesting a certificate. Use a trusted certificate authority and configure automatic renewal. After TLS is active, redirect HTTP to HTTPS and test renewal in the certificate tool’s dry-run mode. The exact certificate command depends on the certificate authority and Ubuntu package available on your server, so do not paste an unverified command into production.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Establish a team deployment workflow
A VPS is easier to maintain when deployment is repeatable rather than performed by SSH improvisation.
- Develop against the pinned line. Every repository carries
.nvmrc; CI uses the same major version. - Review the lockfile. Require code review for changes to
package-lock.jsonor another package manager lockfile. - Build outside the live directory. Deploy to a new release directory, run
npm ci, build and test, then switch acurrentsymlink or perform an equally atomic change. - Restart deliberately. Run
pm2 reload ecosystem.config.cjs --update-envwhen the application supports graceful reloads; use a full restart when configuration or process behavior requires it. - Keep rollback available. Retain the previous release until health checks pass and document the command that restores it.
- Separate access. Developers should not need root for routine deployments. Use narrowly scoped
sudoersrules only where an operation truly requires them.
Log rotation, disk alerts and an external backup of source, configuration and persistent data are part of the environment, not optional afterthoughts. PM2 logs are not a backup and should not be your only incident record.
Upgrade from Node 24 to Node 26 safely
Do not switch the live service on the LTS announcement date without testing. When Node 26 reaches LTS on 28 October 2026, install it alongside Node 24 and test the complete application:
nvm install 26
nvm use 26
node --version
npm ci
npm test
npm run build
Check native modules, framework support, startup flags, memory use and background jobs. Update the repository’s .nvmrc only after the team and CI pass. Deploy the new release beside the old one, watch health checks and logs, and keep the Node 24 rollback path until the change has proved stable. Node 26 is planned to enter maintenance on 20 October 2027 and reach end of life on 30 April 2029, so record those dates in the maintenance calendar.
Common failures and fixes
nvm: command not found: you are in a non-login shell or a different user. Start a fresh session asdeployand confirm the shell profile loads nvm.- PM2 uses the wrong Node version: PM2 was installed under another user’s system Node. Remove that installation, activate the deploy user’s nvm version, reinstall PM2, then regenerate
pm2 startupand runpm2 save. - The app works on localhost but not publicly: check
pm2 logs,curl http://127.0.0.1:3000,sudo nginx -t, DNS and the firewall. Confirm that Nginx points to the same port the application uses. - The app vanishes after reboot: run
pm2 statusas the deploy user, verify the generated startup service, and runpm2 saveafter every intentional process-list change. - Port 3000 is already in use: inspect
ss -ltnpandpm2 listbefore killing anything. Two copies of the service often indicate a manual Node process plus PM2. - HTTPS shows the wrong certificate: verify the Nginx
server_name, DNS target and enabled-site symlink, then reload only afternginx -tsucceeds.
Deployment checklist
- Node 24 is selected for production, with Node 26 tested separately until its 28 October 2026 LTS transition.
- Node was installed through nvm, not a conflicting system package.
- The repository contains a committed
.nvmrcand lockfile. - The application runs as a non-root deploy user.
- PM2 has an ecosystem configuration, a generated startup service and a saved process list.
- Nginx proxies to localhost, the firewall exposes only required ports, and HTTPS renewal is monitored.
- Logs, backups, rollback and access ownership are documented for the whole team.
Frequently Asked Questions
Should I install Node.js with apt or nvm on a team VPS?
Use nvm for this setup. It supports side-by-side versions and per-project pins; apt is simpler but can be behind the release line your application requires.
Can I use Node 26 in production before 28 October 2026?
Use it for compatibility testing and staging first. Node 24 is the Active LTS production baseline until Node 26 reaches its scheduled LTS date.
Why does PM2 need both startup and save?
The startup command integrates PM2 with boot; save records which processes PM2 should restore. Both are required for automatic recovery after reboot.
Recommended Free Tools
Should Node listen on the VPS’s public IP?
Normally no. Bind the application to localhost and let Nginx handle the public HTTP and HTTPS connections.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




