nodejs
How to Install Node.js, Python, and PHP on a Fresh VPS
A plain-English guide to installing the right app runtime on a fresh server without creating version conflicts or mystery errors.
You have a clean server, an app that needs Node.js, Python, or PHP, and one wrong install can leave you with mystery errors before the site even starts.
Short version: To install Node.js, Python, or PHP on a fresh server, first update the system, choose one version path, install the runtime and its package manager, then test it with a tiny app before adding your real project. Node.js usually needs npm, Python usually needs a virtual environment and pip, and PHP usually needs PHP-FPM plus Composer for modern frameworks. The safest setup is one where each project has clear versions, a predictable start method, and logs you can find later.
What are you actually installing?
Think of your server like an empty workshop. The operating system is the building. Node.js, Python, and PHP are the machines your code needs before it can do any work.
Node.js runs JavaScript outside the browser. If your project has a package.json file, it probably expects Node.js and npm, the tool that downloads JavaScript packages.
Python runs .py code. If your project has requirements.txt or pyproject.toml, it probably expects Python, pip, and usually a virtual environment. A virtual environment is a little fenced-off room where one project can keep its own packages without spilling them into another project.
PHP runs .php code. For websites, PHP usually works through PHP-FPM, a background worker that receives requests from a web server like Nginx. Modern PHP apps often use Composer to install libraries.
Which runtime should you install first?
Install the one your app asks for. The project files are the label on the box.
| Runtime | Install it when you see | Usually needs | Common mistake |
|---|---|---|---|
| Node.js | package.json, Next.js, Express, Nuxt | npm or another package manager | Installing a version older than the app expects |
| Python | requirements.txt, Django, Flask, FastAPI | pip and a virtual environment | Installing packages globally instead of per project |
| PHP | .php files, Laravel, WordPress, Symfony | PHP-FPM and Composer | Installing PHP but forgetting the web server connection |
You can install all three on one server, but do not treat that as one big bucket. Each project should have its own folder, its own version expectations, and its own way to start.
If this is your first fresh server, do the basic safety work first: updates, a firewall, and a normal user account. The firewall piece is covered in How to set up a firewall on your server.
How do you keep Node.js, Python, and PHP from breaking later?
The main danger is not the first install. It is the second project, three months later, when you forget what you changed.
For Node.js, choose a Node.js LTS version that matches your app. LTS means long-term support: a stable release line meant for real projects. Avoid mixing several install methods unless you know why. If node: command not found or npm: command not found appears, the server either does not have Node.js installed for that user, or the path to it is not available where the app starts.
For Python, protect the system Python. Many operating system tools depend on it. Put your app packages in a virtual environment instead of installing everything globally. If you see ModuleNotFoundError, it often means the package exists somewhere, just not in the environment your app is actually using.
For PHP, installing PHP is only half the job. A website also needs the web server to hand PHP files to PHP-FPM. If that connection points to the wrong PHP version, or to a PHP-FPM service that is not running, you can end up with 502 Bad Gateway even though the code itself is fine.
Whatever you install, make logs easy to find. Logs are the receipt for what your app tried to do. If the site starts and then dies, your next clue is usually there. For a beginner-friendly walkthrough, read How to Read Server Logs When Something Breaks.
FAQ
Can I install Node.js, Python, and PHP on the same server? Yes. Keep projects separated so one app does not depend on another app’s runtime or packages.
Should I use Docker instead? Docker can make versions easier to repeat, but it adds another layer to understand. If you are still learning servers, read Docker on a server for beginners before choosing that route.
**Why does node: command not found happen after I installed Node.js?** Usually the app is starting as a different user, or from an environment that does not know where Node.js is installed.
Do I need Composer for every PHP site? No. WordPress can run without Composer. Laravel, Symfony, and many modern PHP apps usually need it.
The shortcut
Server Manager helps you avoid the messy parts that usually appear after the first install: the wrong Node.js version for one app, Python packages landing in the wrong environment, PHP-FPM pointing at the wrong place, or a site failing with 502 Bad Gateway because one service is missing from the chain.
The real benefit is that the setup stays legible. Months later, you can still understand which project uses which runtime, where it lives, and what needs to be running for it to answer visitors. That spares you from rebuilding the server from memory when a small change breaks the site.
What does success look like?
A good install is boring. The runtime matches the app, the package manager works, the project starts in a repeatable way, and errors have a clear place to show up.
Once Node.js, Python, or PHP is installed cleanly, your server stops feeling like a black box. You know what is running, why it is there, and how to come back later without guessing.