One VPS, Multiple Nodes: The Beginner's Guide
Difficulty grade:
Intermediate
66%
Need help setting up your node?
Step-by-Step GUIDE
Disclaimer
The information provided in this guide is for general informational purposes only. By accessing or using this guide, you acknowledge and agree that the author and this website shall not be held responsible or liable for any errors, omissions, or outcomes resulting from the use of this material. This includes, without limitation, any direct, indirect, incidental, or consequential damages to hardware, software, data, or any other property. While reasonable efforts have been made to ensure the accuracy and reliability of the content, no warranties or guarantees are provided, either express or implied. Users assume full responsibility for the implementation of any instructions contained herein and are strongly advised to perform appropriate backups and due diligence before proceeding. For official support or the most up-to-date information, please consult the relevant project’s official documentation or support channels.
Section 1: Connecting to the VPS
To access your VPS, you have two options
- Built-in Console: Most providers (e.g., DigitalOcean) offer a web-based console in their dashboard — no setup required.
- SSH Method: Use PowerShell or PuTTY on Windows, or Terminal on macOS/Linux — most VPS use
rootas the default username.
Run this command:
ssh username@your_server_ipReplace username and your_server_ip with your actual VPS login credentials. You’ll be prompted to enter the password to complete the login.
Example: ssh root@192.0.2.123
Section 2: Installing and Running the Node
Why Optimize VPS Usage?
Separate VPS instances for each node may seem straightforward but can rack up expenses quickly. Imagine paying $6/month per VPS — running five nodes could cost you $360 annually! By consolidating nodes onto one VPS, you can slash hosting costs and simplify management.
Additionally, fewer servers mean fewer headaches. Managing multiple VPS instances for blockchain and DePIN nodes can become cumbersome, especially for new projects where returns may be minimal. A single, optimized VPS setup reduces complexity and operational strain.
Tools and Preparation
Screen vs. Docker: Which to Use?
Advantages of Screen:
- Minimal System Overhead
- Beginner-Friendly
- Quick Setup
Disadvantages of Screen:
- Limited Isolation
- Less Organized for Complex Setups
Advantages of Docker:
- Strong Isolation
- Scalability
- Versatility
Disadvantages of Docker:
- Higher Resource Usage
- Steeper Learning Curve
- Overkill for Simple Setups
For this tutorial, we’ll focus on Screen for its simplicity and cost efficiency.
What You’ll Need:
- A reliable VPS (e.g., Contabo Cloud VPS 2)
- Basic Linux familiarity
- Screen tool
Setting Up Screen
sudo apt-get updatesudo apt-get install screen
Using Screen for Multiple Nodes
Each node gets its own session. Follow these steps:
1. Create a Screen Session:
screen -S node_nameReplace node_name with a descriptive name.
2. Run Node Setup Commands:
./start_node_command.sh
3. Detach the Session:
Press Ctrl + A, then D
4. List Active Sessions:
screen -ls
5. Reattach to a Session:
screen -r node_name
6. Terminate a Session:
Reattach:
screen -r node_nameThen press Ctrl + A, K to kill it and confirm.
Alternatively:
screen -XS [screenID] quit
An Example Setup
Let’s say you’re running two nodes:
screen -S NodeA
./start_node_command.sh
Ctrl + A, D
screen -S NodeB
./start_node_command.sh
Ctrl + A, D
Monitoring VPS Resources
htopdf -huptime
Testing Nodes on a Second VPS
Use a low-cost VPS (e.g., RackNerd VPS) for testing node setups. You can easily reset if needed. This helps identify compatibility issues before moving to your main server.
Wrapping Up
Using Screen to run multiple nodes on one VPS saves cost and simplifies management. Whether you’re new or optimizing an existing setup, this approach makes node operations more efficient.
💬 Got questions or tips? Drop them in the comments or join our community on DEPINspirationHUB Discord to connect, share, and learn together!
