Skip to main content
HOW-TO

Migration from 2.x

One-time fix for pre-Feb-2026 installs

If you installed PC2 before February 2026, you're on version 2.6.x and PC2's auto-updater won't catch you up on its own (explanation below). This page is the one-time terminal walkthrough to fix that. After this, future updates happen automatically through the normal Auto Updates flow — no terminal needed.

Why Manual Update?​

The versioning was reset for the public launch:

  • Old versions: 2.6.0 -> 2.6.8 (pre-release/beta)
  • New versions: 0.1.1 -> 1.0.0+ (public release)

Your PC2 thinks 2.6.x is "newer" than 0.1.1, so auto-update won't kick in. This is a one-time fix -- after this, auto-updates work normally.

How to Update​

Step by Step​

pm2 stop pc2

cd ~/pc2.net
git fetch origin main
git reset --hard origin/main

npm install --legacy-peer-deps --ignore-scripts

cd pc2-node && npm run build

pm2 restart pc2

Verify​

Open your PC2 in browser and go to Settings -> About. You should see version 0.1.1 or higher.

Quick One-Liner​

pm2 stop pc2 && cd ~/pc2.net && git fetch origin main && git reset --hard origin/main && npm install --legacy-peer-deps --ignore-scripts && cd pc2-node && npm run build && pm2 restart pc2

After Migration​

Once you're on 0.1.1+, auto-updates work normally:

  • Go to Settings -> About -> Check for Updates
  • Or wait for the update notification

Your files and data are preserved during this update. Only the application code changes.

Troubleshooting​

"Permission denied" errors:

sudo chown -R $USER:$USER ~/pc2.net

Build fails:

rm -rf node_modules
npm install --legacy-peer-deps --ignore-scripts
cd pc2-node && npm run build

PM2 not found:

source ~/.nvm/nvm.sh