
# Install a FiveM Server on Windows Server

Want to create your own **GTA V multiplayer server** with FiveM? This comprehensive guide walks you through the complete installation and configuration process on **Windows Server**.

---

## 📋 Before You Begin

<Prerequisites>

✅ A **Windows Server** VPS (Windows Server 2019/2022 recommended)
✅ At least **8 GB RAM** (16 GB recommended for RP servers)
✅ RDP access to your server
✅ A **CFX.re account** to get your license
✅ Basic command line knowledge

</Prerequisites>

---

<StepSection number="1" title="Get Your FiveM License Key">

Before installing anything, you need an **official license** from FiveM.

<SubSection title="Create an Account and Generate the Key">

<CodeBlock title="Steps on Keymaster">

1. Go to [keymaster.fivem.net](https://keymaster.fivem.net)
2. Log in with your CFX.re account (or create one)
3. Click **"New Server"**
4. Choose **"Server Key"** type
5. Fill in the information:
   - **Server name**: Your server name
   - **Server IP**: Your VPS IP address
6. Click **"Generate"**
7. Copy the generated license key

</CodeBlock>

<WarningBox>
⚠️ **Important**

NEVER share your license key publicly. It's tied to your server IP and can be revoked if misused.
</WarningBox>

</SubSection>

</StepSection>

---

<StepSection number="2" title="Prepare Windows Server">

<SubSection title="Install Visual C++ Redistributables">

FiveM requires **Visual C++ Redistributables** to function.

<CodeBlock title="Download and install">

1. Download **Visual C++ 2019 Redistributable**:
   - [64-bit version](https://aka.ms/vs/16/release/vc_redist.x64.exe)
2. Run the installer
3. Restart the server if prompted

</CodeBlock>

</SubSection>

<SubSection title="Create the Directory Structure">

<CodeBlock title="Create folders">

```powershell
# Open PowerShell as Administrator
# Create main directory
New-Item -ItemType Directory -Path "C:\FiveM-Server"

# Create subfolders
New-Item -ItemType Directory -Path "C:\FiveM-Server\server"
New-Item -ItemType Directory -Path "C:\FiveM-Server\server-data"
```

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="3" title="Download FiveM Artifacts">

**Artifacts** are the FiveM server files.

<CodeBlock title="Download the latest version">

1. Go to [FiveM Artifacts](https://runtime.fivem.net/artifacts/fivem/build_server_windows/master/)
2. Download the **latest** version (top of the list)
3. Extract the content to `C:\FiveM-Server\server\`

**Or via PowerShell:**

```powershell
# Download the latest artifact
Invoke-WebRequest -Uri "https://runtime.fivem.net/artifacts/fivem/build_server_windows/master/7290-d3f3d99d3283bd2ebf4cf8a668906d4dcbf33641/server.zip" -OutFile "C:\FiveM-Server\server.zip"

# Extract
Expand-Archive -Path "C:\FiveM-Server\server.zip" -DestinationPath "C:\FiveM-Server\server" -Force
```

</CodeBlock>

<InfoBox>
💡 **Tip:** Check [runtime.fivem.net](https://runtime.fivem.net/artifacts/fivem/build_server_windows/master/) regularly for updates. A well-maintained server is more stable!
</InfoBox>

</StepSection>

---

<StepSection number="4" title="Configure Windows Firewall">

<SubSection title="Open Required Ports">

<CodeBlock title="PowerShell commands">

```powershell
# Open UDP port 30120 (Game)
New-NetFirewallRule -DisplayName "FiveM Server - Game" -Direction Inbound -Protocol UDP -LocalPort 30120 -Action Allow

# Open TCP port 30120 (HTTP)
New-NetFirewallRule -DisplayName "FiveM Server - HTTP" -Direction Inbound -Protocol TCP -LocalPort 30120 -Action Allow

# Open TCP port 40120 (txAdmin)
New-NetFirewallRule -DisplayName "FiveM Server - txAdmin" -Direction Inbound -Protocol TCP -LocalPort 40120 -Action Allow
```

</CodeBlock>

<WarningBox>
⚠️ **Important**

Also configure your VPS firewall (if applicable) to allow these ports. Check your provider's panel (AtmosNode Control Panel, OVH, etc.).
</WarningBox>

</SubSection>

</StepSection>

---

<StepSection number="5" title="Install and Start txAdmin">

**txAdmin** is the official FiveM server management interface.

<SubSection title="First Launch">

<CodeBlock title="Start txAdmin">

```powershell
# Navigate to the server folder
cd C:\FiveM-Server\server

# Start txAdmin
.\FXServer.exe +set citizen_dir C:\FiveM-Server\server\citizen +set sv_licenseKey "YOUR_LICENSE_KEY" +set txAdminPort 40120
```

</CodeBlock>

<InfoBox>
💡 **Replace** `YOUR_LICENSE_KEY` with the key you generated in Step 1.
</InfoBox>

</SubSection>

<SubSection title="Initial Configuration">

<CodeBlock title="Access txAdmin">

1. Open your browser and go to: `http://YOUR_SERVER_IP:40120`
2. Create an administrator account
3. Choose a setup option:
   - **Popular Recipe** → Pre-configured template (ESX, QBCore, etc.)
   - **Custom** → Manual configuration
4. Follow the installation wizard

</CodeBlock>

<SuccessBox>
✅ txAdmin is now installed! You can manage your server from the web interface.
</SuccessBox>

</SubSection>

</StepSection>

---

<StepSection number="6" title="Configure server.cfg">

<CodeBlock title="Recommended server.cfg configuration">

```bash
# License
sv_licenseKey "YOUR_LICENSE_KEY"

# Server Information
sv_hostname "^1My RP France Server ^7| ^2Recruitment Open"
sv_projectName "My Roleplay Server"
sv_projectDesc "Quality roleplay server on FiveM"

# Maximum Players
sv_maxclients 64

# Endpoint (Server IP)
endpoint_add_tcp "0.0.0.0:30120"
endpoint_add_udp "0.0.0.0:30120"

# GTA V Version
sv_enforceGameBuild 2802

# Steam API Key (optional)
# sv_steamApiKey "YOUR_STEAM_API_KEY"

# Tags for server list
sets tags "roleplay, france, economy, whitelist"

# Language
sets locale "fr-FR"

# OneSync (required for +32 players)
set onesync on

# Script Hook (security)
sv_scriptHookAllowed 0

# Resources to start
ensure mapmanager
ensure chat
ensure spawnmanager
ensure sessionmanager
ensure basic-gamemode
ensure hardcap
ensure rconlog
```

</CodeBlock>

<ToolDescription>

**Important Parameters:**

- **sv_maxclients** → Maximum number of players (default: 32, max with OneSync: 2048)
- **sv_enforceGameBuild** → Required GTA V version (2802 = latest)
- **endpoint_add_tcp/udp** → Server ports
- **onesync** → Enable for +32 players
- **sv_scriptHookAllowed** → Disable for security

</ToolDescription>

<WarningBox>
⚠️ **Security**

**NEVER share** your `sv_licenseKey` or `sv_steamApiKey` publicly!
</WarningBox>

</StepSection>

---

<StepSection number="7" title="Add Resources (Mods)">

<SubSection title="ESX Framework (Roleplay)">

<CodeBlock title="Install ESX Legacy">

```powershell
# Navigate to resources folder
cd C:\FiveM-Server\server-data\resources

# Clone ESX Legacy
git clone https://github.com/esx-framework/esx_core.git [esx]
```

</CodeBlock>

<CodeBlock title="Add to server.cfg">

```bash
# ESX Framework
ensure es_extended
ensure esx_menu_default
ensure esx_menu_dialog
ensure esx_menu_list
```

</CodeBlock>

</SubSection>

<SubSection title="QBCore Framework (Alternative)">

<CodeBlock title="Install QBCore">

```powershell
# Download QBCore
git clone https://github.com/qbcore-framework/qb-core.git [qb]
```

</CodeBlock>

</SubSection>

<SubSection title="Popular Resources">

<ReferenceTable>

**Recommended resources:**

| Resource | Description |
|----------|-------------|
| **gcphone** | Phone system for RP |
| **esx_policejob** | Police job |
| **esx_ambulancejob** | EMS job |
| **mythic_hospital** | Advanced hospital system |
| **pma-voice** | Voice proximity (VOIP) |
| **esx_vehicleshop** | Car dealership |

</ReferenceTable>

<InfoBox>
💡 Find resources on [forum.cfx.re](https://forum.cfx.re/c/development/releases/) or [GitHub](https://github.com/topics/fivem).
</InfoBox>

</SubSection>

</StepSection>

---

<StepSection number="8" title="Performance Optimization">

<SubSection title="Optimize server.cfg">

<CodeBlock title="Performance parameters">

```bash
# Increase thread pool
set sv_threadedStreamingEnabled true

# Optimize network performance
set sv_maxPing 0
set sv_pureLevel 1

# Resource limits
set sv_resourceScriptTickCount 10000
set sv_scriptTickInterval 0
```

</CodeBlock>

</SubSection>

<SubSection title="RAM and CPU Optimization">

<CodeBlock title="Windows Server settings">

1. Open **Task Manager**
2. Right-click on **FXServer.exe**
3. Select **Set Priority** → **High**
4. Go to **Details** tab
5. Right-click → **Set Affinity** → Select all CPU cores

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="9" title="Auto-Start Configuration">

<SubSection title="Create a Startup Script">

<CodeBlock title="Create start.bat">

```batch
@echo off
cd /d C:\FiveM-Server\server

:start
echo Starting FiveM Server...
FXServer.exe +exec server.cfg

echo Server stopped. Restarting in 10 seconds...
timeout /t 10
goto start
```

</CodeBlock>

<CodeBlock title="Save as">

Save this file as `C:\FiveM-Server\start.bat`

</CodeBlock>

</SubSection>

<SubSection title="Create a Windows Service">

<CodeBlock title="Using NSSM (Non-Sucking Service Manager)">

```powershell
# Download NSSM
Invoke-WebRequest -Uri "https://nssm.cc/release/nssm-2.24.zip" -OutFile "C:\nssm.zip"
Expand-Archive -Path "C:\nssm.zip" -DestinationPath "C:\nssm"

# Install the service
C:\nssm\nssm-2.24\win64\nssm.exe install FiveM-Server "C:\FiveM-Server\start.bat"

# Start the service
Start-Service FiveM-Server
```

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="10" title="Manage Your Server with txAdmin">

<SubSection title="Key Features">

<ReferenceTable>

**Main txAdmin features:**

| Feature | Description |
|---------|-------------|
| **Dashboard** | Real-time stats and monitoring |
| **Console** | Interactive server console |
| **Resources** | Manage and restart resources |
| **Players** | Player list, kick, ban |
| **Database** | Integrated database management |
| **Backups** | Automatic server backups |
| **Logs** | View and search logs |

</ReferenceTable>

</SubSection>

<SubSection title="Useful Commands">

<CommandList>

**Start the server**
```powershell
cd C:\FiveM-Server\server
.\FXServer.exe +exec server.cfg
```

**View logs in real-time**
```powershell
Get-Content C:\FiveM-Server\server-data\logs\server.log -Wait
```

**Restart a resource**
```
Access txAdmin → Resources → Restart
```

**Manage players**
```
Access txAdmin → Players → Actions
```

</CommandList>

</SubSection>

<SubSection title="txAdmin Shortcuts">

<ReferenceTable>

**Keyboard shortcuts:**

| Shortcut | Action |
|----------|--------|
| `Ctrl + C` | Stop the server (console) |
| `refresh` | Refresh resource list |
| `restart [resource]` | Restart a resource |
| `stop [resource]` | Stop a resource |
| `start [resource]` | Start a resource |

</ReferenceTable>

</SubSection>

</StepSection>

---

## 💬 Need Help?

If you encounter any difficulties:

<HelpCards>

<HelpCard title="📚 FAQ" link="/en/faq" />

<HelpCard title="💬 Discord" link="https://discord.gg/atmosnode">
24/7 Community Support
</HelpCard>

<HelpCard title="🎫 Support Ticket" link="https://client.atmosnode.com" />

</HelpCards>

---

<Congratulations>

**🎮 Congratulations!**

Your FiveM server is now installed and configured. You can now add resources, customize your server, and welcome players!

**Next Steps:**
- Install an RP framework (ESX or QBCore)
- Add custom resources and scripts
- Configure player whitelist
- Set up backups with txAdmin

</Congratulations>


Complete guide to install and configure a FiveM GTA V server on Windows Server. License, txAdmin, optimization, and best practices.

Install a FiveM Server on Windows Server


# Install a Minecraft Server on Debian

Create your own **Minecraft Java Edition server** on Debian or Ubuntu. This guide covers vanilla installation, optimization, and server management.

---

## 📋 Before You Begin

<Prerequisites>

✅ **Linux VPS** Debian 11/12 or Ubuntu 20.04/22.04
✅ **Minimum 2 GB RAM** (4 GB recommended for 10+ players)
✅ **SSH access** with sudo rights
✅ **Java 17** or higher (installed in this guide)
✅ **Port 25565** available

</Prerequisites>

<InfoBox>
💡 **AtmosNode Recommendation:** A VPS with Ryzen 9 9950X3D, 4 GB DDR5 RAM, and NVMe Gen5 provides excellent performance for 20-30 simultaneous players.
</InfoBox>

---

<StepSection number="1" title="Update the System">

Start by updating your Debian/Ubuntu system.

<CodeBlock title="Update packages">

```bash
# Update package list
sudo apt update

# Upgrade the system
sudo apt upgrade -y
```

</CodeBlock>

</StepSection>

---

<StepSection number="2" title="Install Java (OpenJDK 17)">

Minecraft requires Java to run. Install OpenJDK 17, the recommended version.

<CodeBlock title="Install Java 17">

```bash
# Install OpenJDK 17
sudo apt install openjdk-17-jre-headless -y

# Verify installation
java -version
```

</CodeBlock>

<SuccessBox>
✅ You should see something like: `openjdk version "17.0.x"`
</SuccessBox>

<InfoBox>
💡 **Java versions by Minecraft version:**
- Minecraft 1.17 and below: Java 8 or 11
- Minecraft 1.18 to 1.20.4: Java 17
- Minecraft 1.20.5+: Java 21 recommended
</InfoBox>

</StepSection>

---

<StepSection number="3" title="Create a Dedicated User">

For security reasons, create a dedicated user for Minecraft.

<CodeBlock title="Create minecraft user">

```bash
# Create the user
sudo useradd -r -m -U -d /opt/minecraft -s /bin/bash minecraft

# Switch to minecraft user
sudo su - minecraft
```

</CodeBlock>

<WarningBox>
⚠️ **Best Practice**

Never run a Minecraft server as root! Always use a dedicated user with limited permissions.
</WarningBox>

</StepSection>

---

<StepSection number="4" title="Download Minecraft Server">

Download the latest Minecraft Java Edition server.

<SubSection title="Create Directory Structure">

<CodeBlock>

```bash
# Create server directory
mkdir -p ~/server
cd ~/server
```

</CodeBlock>

</SubSection>

<SubSection title="Download the Server">

<CodeBlock title="Download Vanilla Minecraft">

```bash
# Download the latest version (1.21.1 at time of writing)
wget https://piston-data.mojang.com/v1/objects/59353fb40c36d304f2035d51e7d6e6baa98dc05c/server.jar -O minecraft_server.jar

# Or for a specific version, visit:
# https://www.minecraft.net/en-us/download/server
```

</CodeBlock>

<InfoBox>
💡 **Tip:** Always check the latest URL at [minecraft.net/download/server](https://www.minecraft.net/en-us/download/server) for the most recent version.
</InfoBox>

</SubSection>

</StepSection>

---

<StepSection number="5" title="Accept EULA and First Run">

Before starting the server, you must accept the EULA (End User License Agreement).

<CodeBlock title="First run to generate files">

```bash
# Start the server for the first time
java -Xmx1024M -Xms1024M -jar minecraft_server.jar nogui
```

</CodeBlock>

<CodeBlock title="Accept the EULA">

```bash
# The server will stop and create an eula.txt file
# Edit the file to accept the EULA
nano eula.txt

# Change "eula=false" to "eula=true"
# Save with Ctrl+O then Enter, exit with Ctrl+X
```

</CodeBlock>

<WarningBox>
⚠️ **Important**

By accepting the EULA, you agree to Minecraft's terms of use. Read them at [account.mojang.com/terms](https://account.mojang.com/terms).
</WarningBox>

</StepSection>

---

<StepSection number="6" title="Configure Firewall">

Allow Minecraft port (25565) in your firewall.

<CodeBlock title="UFW Configuration (Ubuntu/Debian)">

```bash
# Allow Minecraft port
sudo ufw allow 25565/tcp

# Check status
sudo ufw status
```

</CodeBlock>

<InfoBox>
💡 **Note:** If you have an external firewall (AtmosNode panel, OVH, etc.), remember to also open port 25565 in your management interface.
</InfoBox>

</StepSection>

---

<StepSection number="7" title="Configure server.properties">

Customize your server settings.

<CodeBlock title="Edit server.properties">

```bash
# Edit configuration file
nano server.properties
```

</CodeBlock>

<CodeBlock title="Recommended configuration">

```properties
# Server information
server-name=My Minecraft Server
motd=§aWelcome to my server! §7| §ePlayers: {ONLINE}/{MAX}
server-ip=
server-port=25565

# Game settings
gamemode=survival
difficulty=normal
hardcore=false
pvp=true
max-players=20

# World
level-name=world
level-seed=
generate-structures=true
spawn-protection=16
view-distance=10
simulation-distance=10

# Performance
max-tick-time=60000
max-world-size=29999984

# Whitelist and security
white-list=false
enforce-whitelist=false
online-mode=true
enable-command-block=false

# RCON (remote administration)
enable-rcon=false
rcon.password=
rcon.port=25575
```

</CodeBlock>

<ToolDescription>

**Important parameters:**

- **max-players** → Maximum number of players (adjust based on your RAM)
- **view-distance** → Render distance (10 = 160 blocks, reduced to save RAM)
- **simulation-distance** → Entity calculation distance (10 recommended)
- **online-mode** → Mojang verification (true = premium accounts only)
- **white-list** → Enable whitelist (true = only authorized players can join)

</ToolDescription>

</StepSection>

---

<StepSection number="8" title="Create Startup Script">

Create a script to easily start the server.

<CodeBlock title="Create start.sh">

```bash
# Create the script
nano start.sh
```

</CodeBlock>

<CodeBlock title="Script content">

```bash
#!/bin/bash

# RAM configuration (adjust according to your VPS)
MIN_RAM="2G"
MAX_RAM="4G"

# Start server
java -Xms$MIN_RAM -Xmx$MAX_RAM \
  -XX:+UseG1GC \
  -XX:+ParallelRefProcEnabled \
  -XX:MaxGCPauseMillis=200 \
  -XX:+UnlockExperimentalVMOptions \
  -XX:+DisableExplicitGC \
  -XX:+AlwaysPreTouch \
  -XX:G1HeapWastePercent=5 \
  -XX:G1MixedGCCountTarget=4 \
  -XX:G1MixedGCLiveThresholdPercent=90 \
  -XX:G1RSetUpdatingPauseTimePercent=5 \
  -XX:SurvivorRatio=32 \
  -XX:+PerfDisableSharedMem \
  -XX:MaxTenuringThreshold=1 \
  -Dusing.aikars.flags=https://mcflags.emc.gs \
  -Daikars.new.flags=true \
  -jar minecraft_server.jar nogui
```

</CodeBlock>

<CodeBlock title="Make script executable">

```bash
# Add execute permissions
chmod +x start.sh
```

</CodeBlock>

<InfoBox>
💡 **Aikar's optimization flags:** These JVM parameters are specifically designed to optimize Minecraft performance. More info at [aikar.co/flags](https://aikar.co/2018/07/02/tuning-the-jvm-g1gc-garbage-collector-flags-for-minecraft/).
</InfoBox>

</StepSection>

---

<StepSection number="9" title="Use Screen to Manage the Server">

Screen allows you to keep the server running in the background.

<SubSection title="Install Screen">

<CodeBlock>

```bash
# Return to root to install screen
exit

# Install screen
sudo apt install screen -y

# Switch back to minecraft user
sudo su - minecraft
cd ~/server
```

</CodeBlock>

</SubSection>

<SubSection title="Start with Screen">

<CodeBlock title="Screen commands">

```bash
# Create a screen session named "minecraft"
screen -S minecraft

# Start the server
./start.sh

# Detach session: Ctrl+A then D
# The server keeps running in the background

# To return to the session
screen -r minecraft

# List all sessions
screen -ls
```

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="10" title="Configure Auto-Start">

Create a systemd service to automatically start the server.

<CodeBlock title="Create systemd service">

```bash
# Return to root
exit

# Create service file
sudo nano /etc/systemd/system/minecraft.service
```

</CodeBlock>

<CodeBlock title="Service content">

```ini
[Unit]
Description=Minecraft Server
After=network.target

[Service]
User=minecraft
Group=minecraft
WorkingDirectory=/opt/minecraft/server
ExecStart=/opt/minecraft/server/start.sh
Restart=on-failure
RestartSec=10

[Install]
WantedBy=multi-user.target
```

</CodeBlock>

<CodeBlock title="Enable and start service">

```bash
# Reload systemd
sudo systemctl daemon-reload

# Enable at startup
sudo systemctl enable minecraft

# Start server
sudo systemctl start minecraft

# Check status
sudo systemctl status minecraft

# View logs in real-time
sudo journalctl -u minecraft -f
```

</CodeBlock>

<SuccessBox>
✅ Your Minecraft server now starts automatically when the VPS boots!
</SuccessBox>

</StepSection>

---

<StepSection number="11" title="Useful Administration Commands">

<CommandList>

**Stop server properly**
```bash
sudo systemctl stop minecraft
```

**Restart server**
```bash
sudo systemctl restart minecraft
```

**View logs**
```bash
sudo journalctl -u minecraft -n 50
```

**Access console (with screen)**
```bash
sudo su - minecraft
screen -r minecraft
```

**Save the world**
```bash
# In Minecraft console
save-all
```

**Add player to whitelist**
```bash
# In Minecraft console
whitelist add PlayerName
whitelist on
```

</CommandList>

<ReferenceTable>

**Minecraft console commands:**

| Command | Description |
|---------|-------------|
| `whitelist add <player>` | Add to whitelist |
| `whitelist remove <player>` | Remove from whitelist |
| `op <player>` | Give admin rights |
| `deop <player>` | Remove admin rights |
| `kick <player>` | Kick a player |
| `ban <player>` | Ban a player |
| `pardon <player>` | Unban a player |
| `stop` | Stop the server |
| `save-all` | Save the world |
| `list` | List connected players |

</ReferenceTable>

</StepSection>

---

<StepSection number="12" title="Performance Optimization">

<SubSection title="RAM Adjustment">

<CodeBlock title="RAM based on player count">

```bash
# 1-5 players: 2 GB RAM
MIN_RAM="1G"
MAX_RAM="2G"

# 5-10 players: 3-4 GB RAM
MIN_RAM="2G"
MAX_RAM="4G"

# 10-20 players: 4-6 GB RAM
MIN_RAM="3G"
MAX_RAM="6G"

# 20+ players: 6-8 GB RAM
MIN_RAM="4G"
MAX_RAM="8G"
```

</CodeBlock>

<WarningBox>
⚠️ **Important**

Never allocate ALL your VPS RAM to Minecraft! Leave at least 1 GB for the operating system.
</WarningBox>

</SubSection>

<SubSection title="Optimize server.properties">

<CodeBlock title="Parameters for better performance">

```properties
# Reduce view distance
view-distance=8
simulation-distance=8

# Limit entities
max-players=15

# Disable resource-intensive features if needed
spawn-monsters=true
spawn-animals=true
spawn-npcs=true
```

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="13" title="Alternatives: Paper and Spigot">

For better performance, consider **Paper** or **Spigot** instead of Vanilla.

<SubSection title="Install Paper (Recommended)">

<CodeBlock title="Download Paper">

```bash
# Switch to minecraft user
sudo su - minecraft
cd ~/server

# Download Paper (version 1.21.1)
wget https://api.papermc.io/v2/projects/paper/versions/1.21.1/builds/119/downloads/paper-1.21.1-119.jar -O paper.jar

# Modify start.sh to use paper.jar instead of minecraft_server.jar
nano start.sh
# Replace "minecraft_server.jar" with "paper.jar"
```

</CodeBlock>

<InfoBox>
💡 **Paper advantages:**
- Better performance (up to 50% faster)
- Bukkit/Spigot plugin support
- Built-in anti-lag optimizations
- Advanced configuration with paper.yml
</InfoBox>

</SubSection>

<SubSection title="Install Spigot">

<CodeBlock title="Compile Spigot with BuildTools">

```bash
# Install Git (if not already installed)
sudo apt install git -y

# Switch to minecraft user
sudo su - minecraft
mkdir ~/buildtools && cd ~/buildtools

# Download BuildTools
wget https://hub.spigotmc.org/jenkins/job/BuildTools/lastSuccessfulBuild/artifact/target/BuildTools.jar

# Compile Spigot (takes 5-10 minutes)
java -jar BuildTools.jar --rev 1.21.1

# Copy to server folder
cp spigot-*.jar ~/server/spigot.jar
```

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="14" title="Automatic Backups">

Create regular backups of your world.

<CodeBlock title="Backup script">

```bash
# Create backup script
sudo nano /usr/local/bin/minecraft-backup.sh
```

</CodeBlock>

<CodeBlock title="Script content">

```bash
#!/bin/bash

# Configuration
BACKUP_DIR="/opt/minecraft/backups"
SERVER_DIR="/opt/minecraft/server"
DATE=$(date +%Y-%m-%d_%H-%M-%S)
BACKUP_FILE="minecraft-backup-$DATE.tar.gz"

# Create backup folder
mkdir -p $BACKUP_DIR

# Create archive (exclude backups and logs)
tar -czf "$BACKUP_DIR/$BACKUP_FILE" \
    -C $SERVER_DIR \
    --exclude='backups' \
    --exclude='logs' \
    world world_nether world_the_end server.properties ops.json whitelist.json

# Keep only the last 7 backups
cd $BACKUP_DIR
ls -t | tail -n +8 | xargs -r rm

echo "Backup created: $BACKUP_FILE"
```

</CodeBlock>

<CodeBlock title="Automate with cron">

```bash
# Make script executable
sudo chmod +x /usr/local/bin/minecraft-backup.sh

# Add to crontab (backup every 6 hours)
sudo crontab -e

# Add this line:
0 */6 * * * /usr/local/bin/minecraft-backup.sh
```

</CodeBlock>

</StepSection>

---

## 💬 Need Help?

If you encounter any difficulties with your Minecraft server:

<HelpCards>

<HelpCard title="📚 Minecraft Wiki" link="https://minecraft.wiki">
Official documentation
</HelpCard>

<HelpCard title="💬 Discord AtmosNode" link="https://discord.gg/atmosnode">
24/7 VPS Support
</HelpCard>

<HelpCard title="🎫 AtmosNode Support" link="https://client.atmosnode.com">
Technical support ticket
</HelpCard>

</HelpCards>

---

<Congratulations>

**⛏️ Congratulations!**

Your Minecraft server is now operational on Debian! Share your server IP with friends and start building your world!

**To connect:** Open Minecraft → Multiplayer → Add Server → `YOUR_VPS_IP:25565`

</Congratulations>


Complete guide to install and configure a Minecraft Java Edition server on Debian/Ubuntu. Installation, optimization, and management with Screen.

Install a Minecraft Server on Debian


# Getting Started with Your Linux VPS

Congratulations! You've just received your AtmosNode Linux VPS. This guide walks you through the first steps to get your server up and running.

---

## 📋 Prerequisites

<Prerequisites>

✅ **Welcome email** received with your credentials
✅ Your **VPS IP address**
✅ **Root password** or SSH key
✅ **SSH client** installed on your computer

</Prerequisites>

---

<StepSection number="1" title="Connect via SSH">

The first step is to remotely connect to your server using SSH (Secure Shell).

<SubSection title="On Windows">

**Option A: PowerShell / Windows Terminal** (Recommended)

```bash
ssh root@YOUR_VPS_IP
```

<InfoBox>
💡 **Tip:** Replace `YOUR_VPS_IP` with the IP address from your welcome email.
</InfoBox>

**Option B: PuTTY**

1. Download PuTTY from [putty.org](https://www.putty.org/)
2. Enter your VPS IP in "Host Name"
3. Port: `22`
4. Click "Open"

</SubSection>

<SubSection title="On macOS / Linux">

Open your Terminal and run:

```bash
ssh root@YOUR_VPS_IP
```

</SubSection>

<SubSection title="First Connection">

On your first connection, you'll see this message:

```
The authenticity of host '123.456.789.0' can't be established.
Are you sure you want to continue connecting (yes/no)?
```

<SuccessBox>
✅ Type **`yes`** and press Enter. This is normal for a first connection!
</SuccessBox>

</SubSection>

</StepSection>

---

<StepSection number="2" title="Update the System">

**First security rule**: always update the system before any configuration.

<CodeBlock title="On Ubuntu / Debian">

```bash
apt update && apt upgrade -y
```

</CodeBlock>

<CodeBlock title="On CentOS / Rocky Linux">

```bash
yum update -y
```

</CodeBlock>

<InfoBox>
ℹ️ This command updates all installed packages. It may take a few minutes.
</InfoBox>

</StepSection>

---

<StepSection number="3" title="Create a Secure User">

<WarningBox>
⚠️ **Security Best Practice**

Never work directly with the **root** account! Create a dedicated user for daily operations.
</WarningBox>

<CodeBlock title="Create a new user">

```bash
# Create a user (replace 'yourname' with your name)
adduser yourname

# Add admin privileges (sudo)
usermod -aG sudo yourname
```

</CodeBlock>

<CodeBlock title="Test the new user">

Disconnect and reconnect with your new account:

```bash
# Type 'exit' to disconnect
exit

# Reconnect with the new user
ssh yourname@YOUR_VPS_IP
```

</CodeBlock>

</StepSection>

---

<StepSection number="4" title="Configure the Firewall">

Protect your VPS by enabling a firewall to block unauthorized connections.

<SubSection title="With UFW (Ubuntu/Debian)">

<CodeBlock title="Installation and configuration">

```bash
# Install UFW
sudo apt install ufw -y

# Allow SSH (IMPORTANT: Do this BEFORE enabling!)
sudo ufw allow 22/tcp

# Enable firewall
sudo ufw enable

# Check status
sudo ufw status
```

</CodeBlock>

<WarningBox>
⚠️ **Warning:** Always allow SSH (port 22) **BEFORE** enabling the firewall, or you'll lock yourself out!
</WarningBox>

</SubSection>

<SubSection title="With FirewallD (CentOS/Rocky)">

<CodeBlock title="Installation and configuration">

```bash
# Start firewalld
sudo systemctl start firewalld
sudo systemctl enable firewalld

# Allow SSH
sudo firewall-cmd --permanent --add-service=ssh
sudo firewall-cmd --reload

# Verify
sudo firewall-cmd --list-all
```

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="5" title="Secure SSH">

Strengthen your SSH access security by modifying the configuration.

<CodeBlock title="Edit SSH configuration">

```bash
sudo nano /etc/ssh/sshd_config
```

</CodeBlock>

<CodeBlock title="Recommended changes">

```bash
# Disable direct root login
PermitRootLogin no

# Disable password authentication (after setting up SSH keys)
# PasswordAuthentication no

# Change SSH port (optional but recommended)
# Port 2222
```

</CodeBlock>

<InfoBox>
💡 **Tip:** Keep password authentication enabled until you've set up SSH key authentication!
</InfoBox>

<CodeBlock title="Restart SSH">

```bash
sudo systemctl restart sshd
```

</CodeBlock>

</StepSection>

---

<StepSection number="6" title="Install Essential Tools">

Install basic utilities to make server administration easier.

<CodeBlock title="On Ubuntu/Debian">

```bash
sudo apt install -y curl wget git vim htop net-tools unzip
```

</CodeBlock>

<CodeBlock title="On CentOS/Rocky">

```bash
sudo yum install -y curl wget git vim htop net-tools unzip
```

</CodeBlock>

<ToolDescription>

**Installed tools:**

- **curl/wget** → Download files from the internet
- **git** → Version control system
- **vim** → Advanced text editor
- **htop** → Interactive system monitor
- **net-tools** → Network utilities (ifconfig, netstat...)
- **unzip** → Extract compressed files

</ToolDescription>

</StepSection>

---

<StepSection number="7" title="Configure the Hostname">

Give your server a custom name to easily recognize it.

<CodeBlock title="Set the hostname">

```bash
# Set hostname
sudo hostnamectl set-hostname my-atmos-vps

# Verify configuration
hostnamectl
```

</CodeBlock>

</StepSection>

---

<StepSection number="8" title="Enable Automatic Updates">

Enable automatic security updates to keep your system protected continuously.

<SubSection title="On Ubuntu/Debian">

<CodeBlock>

```bash
# Install unattended-upgrades
sudo apt install unattended-upgrades -y

# Enable automatic updates
sudo dpkg-reconfigure --priority=low unattended-upgrades
```

</CodeBlock>

</SubSection>

<SubSection title="On CentOS/Rocky">

<CodeBlock>

```bash
# Install yum-cron
sudo yum install yum-cron -y

# Enable and start
sudo systemctl enable --now yum-cron
```

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="9" title="Monitor the System">

Learn essential commands to monitor your VPS.

<CommandList>

**Disk space used**
```bash
df -h
```

**RAM usage**
```bash
free -h
```

**Interactive system monitor**
```bash
htop
```

**List of processes**
```bash
ps aux
```

**Service status**
```bash
systemctl status
```

</CommandList>

<ReferenceTable>

**Monitoring commands:**

| Command | Description |
|---------|-------------|
| `df -h` | Available disk space (human-readable) |
| `free -h` | RAM usage and available memory |
| `htop` | Interactive process monitor |
| `uptime` | System uptime and load |
| `top` | Real-time system statistics |
| `systemctl status` | Status of all services |

</ReferenceTable>

</StepSection>

---

## 💬 Need Help?

If you encounter difficulties, our team is here to help:

<HelpCards>

<HelpCard title="📚 FAQ" link="/en/faq" />

<HelpCard title="💬 Discord" link="https://discord.gg/atmosnode">
24/7 Community Support
</HelpCard>

<HelpCard title="🎫 Support Ticket" link="https://client.atmosnode.com" />

</HelpCards>

---

<Congratulations>

**🎉 Congratulations!**

Your Linux VPS is now properly configured and secured.
Explore our other tutorials to install your applications and services!

</Congratulations>


Complete guide to get started with your AtmosNode Linux VPS. SSH connection, basic setup, and security hardening.

Getting Started with Your Linux VPS


# Secure Your Linux VPS

Now that your VPS is up and running, it's time to strengthen its security. This guide walks you through protecting your server against common threats.

---

## 📋 Prerequisites

<Prerequisites>

✅ Have a working Linux VPS
✅ SSH access with a non-root user
✅ Sudo privileges configured
✅ Completed the [Getting Started with Your Linux VPS](/en/wiki/getting-started/getting-started-linux-vps) guide

</Prerequisites>

---

<StepSection number="1" title="Configure SSH Key Authentication">

SSH key authentication is **much more secure** than passwords.

<SubSection title="On Your Local Computer - Windows (PowerShell)">

<CodeBlock title="Generate an SSH key pair">

```bash
# Generate an SSH key pair
ssh-keygen -t ed25519 -C "your-email@example.com"

# Press Enter to accept the default location
# Set a passphrase (optional but recommended)
```

</CodeBlock>

<InfoBox>
💡 **Tip:** The ed25519 key is more secure and faster than RSA. If your system doesn't support it, use `ssh-keygen -t rsa -b 4096`.
</InfoBox>

<CodeBlock title="Copy the public key to your VPS">

```bash
type $env:USERPROFILE\.ssh\id_ed25519.pub | ssh yourname@YOUR_VPS_IP "cat >> ~/.ssh/authorized_keys"
```

</CodeBlock>

</SubSection>

<SubSection title="On Your Local Computer - macOS / Linux">

<CodeBlock title="Generate and copy the key">

```bash
# Generate an SSH key pair
ssh-keygen -t ed25519 -C "your-email@example.com"

# Copy the key to your VPS
ssh-copy-id yourname@YOUR_VPS_IP
```

</CodeBlock>

</SubSection>

<SubSection title="Test Key Authentication">

<CodeBlock>

```bash
# Connect to your VPS (should not ask for password)
ssh yourname@YOUR_VPS_IP
```

</CodeBlock>

<SuccessBox>
✅ If the connection works without a password, your SSH key is properly configured!
</SuccessBox>

</SubSection>

</StepSection>

---

<StepSection number="2" title="Disable Password Authentication">

Once SSH keys are configured, disable password authentication.

<WarningBox>
⚠️ **WARNING**

Before disabling password authentication, verify that you can connect with your SSH key! Keep a backup SSH session open.
</WarningBox>

<CodeBlock title="Edit SSH configuration">

```bash
# Edit SSH configuration
sudo nano /etc/ssh/sshd_config
```

</CodeBlock>

<CodeBlock title="Modify or add these lines">

```bash
# Disable password authentication
PasswordAuthentication no

# Disable challenge-response authentication
ChallengeResponseAuthentication no

# Completely disable root login
PermitRootLogin no

# Allow only your user (optional)
AllowUsers yourname
```

</CodeBlock>

<CodeBlock title="Restart SSH service">

```bash
sudo systemctl restart sshd
```

</CodeBlock>

</StepSection>

---

<StepSection number="3" title="Change Default SSH Port">

Changing the SSH port reduces automated intrusion attempts.

<CodeBlock title="Edit SSH configuration">

```bash
# Edit SSH configuration
sudo nano /etc/ssh/sshd_config
```

</CodeBlock>

<CodeBlock title="Change the port">

```bash
# Default port: 22
Port 2222
```

</CodeBlock>

<InfoBox>
💡 **Tip:** Choose a port between 1024 and 65535. Avoid common ports like 2222, prefer something like 49152.
</InfoBox>

<SubSection title="Update Firewall - UFW (Ubuntu/Debian)">

<CodeBlock>

```bash
# Allow the new port
sudo ufw allow 2222/tcp

# Remove the old port
sudo ufw delete allow 22/tcp

# Reload UFW
sudo ufw reload
```

</CodeBlock>

</SubSection>

<SubSection title="Update Firewall - FirewallD (CentOS/Rocky)">

<CodeBlock>

```bash
# Add the new port
sudo firewall-cmd --permanent --add-port=2222/tcp

# Remove the old port
sudo firewall-cmd --permanent --remove-service=ssh

# Reload firewall
sudo firewall-cmd --reload
```

</CodeBlock>

</SubSection>

<CodeBlock title="Restart SSH and reconnect">

```bash
# Restart SSH
sudo systemctl restart sshd

# To reconnect with the new port
ssh -p 2222 yourname@YOUR_VPS_IP
```

</CodeBlock>

</StepSection>

---

<StepSection number="4" title="Install and Configure Fail2ban">

Fail2ban protects your server against brute force attacks by temporarily banning suspicious IPs.

<SubSection title="Installation">

<CodeBlock title="On Ubuntu / Debian">

```bash
sudo apt update
sudo apt install fail2ban -y
```

</CodeBlock>

<CodeBlock title="On CentOS / Rocky Linux">

```bash
sudo yum install epel-release -y
sudo yum install fail2ban -y
```

</CodeBlock>

</SubSection>

<SubSection title="Configure Fail2ban">

<CodeBlock title="Create a local configuration file">

```bash
# Create a local configuration file
sudo cp /etc/fail2ban/jail.conf /etc/fail2ban/jail.local
sudo nano /etc/fail2ban/jail.local
```

</CodeBlock>

<CodeBlock title="Recommended configuration">

```ini
[DEFAULT]
# Ban duration (in seconds) - 1 hour
bantime = 3600

# Detection window duration (10 minutes)
findtime = 600

# Number of attempts before ban
maxretry = 5

# Action to perform (ban the IP)
banaction = iptables-multiport

[sshd]
enabled = true
port = 2222
logpath = %(sshd_log)s
backend = %(sshd_backend)s
maxretry = 3
bantime = 86400
```

</CodeBlock>

<ToolDescription>

**Configuration explained:**

- **bantime = 86400** → Ban for 24 hours
- **findtime = 600** → Monitor over a 10-minute window
- **maxretry = 3** → Ban after 3 failed attempts
- **port = 2222** → If you changed the SSH port

</ToolDescription>

<CodeBlock title="Start and enable Fail2ban">

```bash
# Start and enable Fail2ban
sudo systemctl start fail2ban
sudo systemctl enable fail2ban

# Check status
sudo systemctl status fail2ban
```

</CodeBlock>

</SubSection>

<SubSection title="Verify Fail2ban">

<CommandList>

**View SSH protection status**
```bash
sudo fail2ban-client status sshd
```

**View all active jails**
```bash
sudo fail2ban-client status
```

</CommandList>

<ReferenceTable>

**Useful Fail2ban commands:**

| Command | Description |
|---------|-------------|
| `sudo fail2ban-client status sshd` | SSH jail status |
| `sudo fail2ban-client set sshd unbanip IP` | Unban an IP |
| `sudo fail2ban-client reload` | Reload configuration |
| `sudo tail -f /var/log/fail2ban.log` | View logs in real-time |

</ReferenceTable>

</SubSection>

</StepSection>

---

<StepSection number="5" title="Configure Advanced Firewall">

Configure your firewall to only allow necessary services.

<SubSection title="UFW Configuration (Ubuntu/Debian)">

<CodeBlock>

```bash
# Reset UFW (optional)
sudo ufw --force reset

# Default policy: deny all incoming traffic
sudo ufw default deny incoming
sudo ufw default allow outgoing

# Allow SSH (with new port)
sudo ufw allow 2222/tcp

# Allow HTTP and HTTPS (if you have a web server)
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp

# Limit SSH connections (anti-bruteforce protection)
sudo ufw limit 2222/tcp

# Enable UFW
sudo ufw enable

# Check status
sudo ufw status verbose
```

</CodeBlock>

</SubSection>

<SubSection title="FirewallD Configuration (CentOS/Rocky)">

<CodeBlock>

```bash
# Set default zone
sudo firewall-cmd --set-default-zone=public

# Allow SSH
sudo firewall-cmd --permanent --add-port=2222/tcp

# Allow HTTP/HTTPS
sudo firewall-cmd --permanent --add-service=http
sudo firewall-cmd --permanent --add-service=https

# Limit SSH connections
sudo firewall-cmd --permanent --add-rich-rule='rule service name=ssh limit value=3/m accept'

# Reload
sudo firewall-cmd --reload

# Verify
sudo firewall-cmd --list-all
```

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="6" title="Monitor System Logs">

Regularly monitor logs to detect suspicious activity.

<CommandList>

**View recent SSH login attempts**
```bash
sudo grep "Failed password" /var/log/auth.log | tail -20
```

**View successful SSH connections**
```bash
sudo grep "Accepted" /var/log/auth.log | tail -20
```

**Monitor logs in real-time**
```bash
sudo tail -f /var/log/auth.log
```

</CommandList>

<InfoBox>
💡 **Tip:** On CentOS/Rocky, use `/var/log/secure` instead of `/var/log/auth.log`.
</InfoBox>

</StepSection>

---

<StepSection number="7" title="Install Security Audit Tools">

<SubSection title="Lynis - Automatic Security Audit">

<CodeBlock title="Installation and usage">

```bash
# Installation on Ubuntu/Debian
sudo apt install lynis -y

# Installation on CentOS/Rocky
sudo yum install lynis -y

# Run a complete audit
sudo lynis audit system
```

</CodeBlock>

</SubSection>

<SubSection title="RKHunter - Rootkit Detection">

<CodeBlock title="Installation and usage">

```bash
# Installation on Ubuntu/Debian
sudo apt install rkhunter -y

# Installation on CentOS/Rocky
sudo yum install rkhunter -y

# Update database
sudo rkhunter --update

# Run a scan
sudo rkhunter --check
```

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="8" title="Keep System Updated">

<CodeBlock title="On Ubuntu/Debian">

```bash
# Configure automatic security updates
sudo apt install unattended-upgrades -y
sudo dpkg-reconfigure -plow unattended-upgrades

# Check for updates manually
sudo apt update && sudo apt upgrade -y
```

</CodeBlock>

<WarningBox>
⚠️ **Important**

Security updates are crucial. Configure automatic updates and regularly verify your system is up to date.
</WarningBox>

</StepSection>

---

<StepSection number="9" title="Configure Automatic Backups">

Never neglect backups!

<CodeBlock title="Create directory and script">

```bash
# Create a directory for backups
mkdir -p ~/backups

# Create backup script
sudo nano /usr/local/bin/backup.sh
```

</CodeBlock>

<CodeBlock title="Backup script">

```bash
#!/bin/bash

# Configuration
BACKUP_DIR="/home/yourname/backups"
DATE=$(date +%Y-%m-%d_%H-%M-%S)
BACKUP_FILE="backup_$DATE.tar.gz"

# Create archive
tar -czf "$BACKUP_DIR/$BACKUP_FILE" \
    /etc \
    /home/yourname \
    --exclude=/home/yourname/backups

# Keep only the last 7 backups
cd "$BACKUP_DIR"
ls -t | tail -n +8 | xargs -r rm

echo "Backup created: $BACKUP_FILE"
```

</CodeBlock>

<CodeBlock title="Automate with cron">

```bash
# Make the script executable
sudo chmod +x /usr/local/bin/backup.sh

# Add a cron job (daily backup at 3 AM)
sudo crontab -e
```

</CodeBlock>

<CodeBlock title="Add this line to crontab">

```bash
0 3 * * * /usr/local/bin/backup.sh
```

</CodeBlock>

</StepSection>

---

<StepSection number="10" title="Security Checklist">

<Prerequisites>

**Verify that you have:**

✅ Configured SSH key authentication
✅ Disabled password authentication
✅ Disabled root login
✅ Changed default SSH port
✅ Installed and configured Fail2ban
✅ Properly configured your firewall
✅ Installed audit tools (Lynis, RKHunter)
✅ Enabled automatic updates
✅ Configured regular backups
✅ Monitored system logs

</Prerequisites>

</StepSection>

---

## 💬 Need Help?

If you encounter difficulties:

<HelpCards>

<HelpCard title="📚 FAQ" link="/en/faq" />

<HelpCard title="💬 Discord" link="https://discord.gg/atmosnode">
24/7 Community Support
</HelpCard>

<HelpCard title="🎫 Support Ticket" link="https://client.atmosnode.com" />

</HelpCards>

---

<Congratulations>

**🔒 Congratulations!**

Your VPS is now well secured. Security is an ongoing process: regularly monitor your logs and keep your system updated!

</Congratulations>


Complete guide to harden your Linux VPS security. Fail2ban, SSH key authentication, and security best practices.

Secure Your Linux VPS


# Install Node.js on Your Linux VPS

This guide explains how to install Node.js and npm on your Linux VPS, whether you're using Ubuntu, Debian, CentOS, or Rocky Linux. We'll cover multiple installation methods, including using **nvm** (Node Version Manager) to easily manage multiple Node.js versions.

---

## 📋 Prerequisites

<Prerequisites>

✅ A Linux VPS (Ubuntu, Debian, CentOS, Rocky Linux)
✅ SSH access with sudo privileges
✅ A stable Internet connection
✅ At least 1 GB of available RAM

</Prerequisites>

---

<StepSection number="1" title="Install Node.js with nvm (Recommended)">

**nvm** (Node Version Manager) is the recommended method because it makes managing multiple Node.js versions easy.

<ToolDescription>

**Benefits of nvm:**

- Install multiple versions of Node.js
- Easily switch between versions
- Install Node.js without root privileges
- Manage versions per project

</ToolDescription>

<SubSection title="Download and install nvm">

<CodeBlock title="With curl">

```bash
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
```

</CodeBlock>

<CodeBlock title="With wget">

```bash
wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
```

</CodeBlock>

</SubSection>

<SubSection title="Load nvm into your session">

<CodeBlock title="For Bash">

```bash
source ~/.bashrc
```

</CodeBlock>

<CodeBlock title="For Zsh">

```bash
source ~/.zshrc
```

</CodeBlock>

<CodeBlock title="Verify installation">

```bash
nvm --version
```

</CodeBlock>

</SubSection>

<SubSection title="Install Node.js">

<CodeBlock title="Install latest LTS version">

```bash
nvm install --lts
```

</CodeBlock>

<CodeBlock title="Install specific version">

```bash
# Install Node.js 20
nvm install 20

# Install Node.js 18
nvm install 18

# Install Node.js 16
nvm install 16
```

</CodeBlock>

<CodeBlock title="Set default version">

```bash
nvm alias default 20
```

</CodeBlock>

</SubSection>

<SubSection title="Verify installation">

<CommandList>

**Node.js version**
```bash
node --version
```

**npm version**
```bash
npm --version
```

</CommandList>

<SuccessBox>
✅ Node.js and npm are now installed via nvm!
</SuccessBox>

<ReferenceTable>

**Useful nvm commands:**

| Command | Description |
|---------|-------------|
| `nvm list` | List installed versions |
| `nvm ls-remote` | List all available versions |
| `nvm use 20` | Use a specific version |
| `nvm uninstall 16` | Uninstall a version |
| `nvm current` | Show current version |

</ReferenceTable>

</SubSection>

</StepSection>

---

<StepSection number="2" title="Install via package manager">

Alternative to nvm: direct installation via NodeSource repositories.

<SubSection title="Ubuntu and Debian">

<CodeBlock title="Add NodeSource repository">

```bash
# Update packages
sudo apt update

# Install curl if needed
sudo apt install -y curl

# Add NodeSource repository for Node.js 20
curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -

# Install Node.js and npm
sudo apt install -y nodejs
```

</CodeBlock>

<InfoBox>
💡 **Tip:** For other versions, replace `setup_20.x` with `setup_18.x` (Node.js 18) or `setup_21.x` (Node.js 21).
</InfoBox>

<CodeBlock title="Verify installation">

```bash
node --version
npm --version
```

</CodeBlock>

</SubSection>

<SubSection title="CentOS, Rocky Linux and AlmaLinux">

<CodeBlock title="Add NodeSource repository">

```bash
# Update packages
sudo dnf update -y  # or yum update -y

# Add NodeSource repository for Node.js 20
curl -fsSL https://rpm.nodesource.com/setup_20.x | sudo bash -

# Install Node.js and npm
sudo dnf install -y nodejs  # or yum install -y nodejs
```

</CodeBlock>

<CodeBlock title="Verify installation">

```bash
node --version
npm --version
```

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="3" title="Post-installation configuration">

<SubSection title="Configure npm without sudo">

By default, npm requires sudo for global installations. Let's configure npm to use a local directory.

<CodeBlock>

```bash
# Create a directory for global packages
mkdir ~/.npm-global

# Configure npm to use this directory
npm config set prefix '~/.npm-global'

# Add the directory to PATH
echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc
source ~/.bashrc
```

</CodeBlock>

</SubSection>

<SubSection title="Update npm">

<CodeBlock>

```bash
npm install -g npm@latest
```

</CodeBlock>

</SubSection>

<SubSection title="Alternative package managers">

<InfoBox>
💡 **Tip:** For faster installations, you can use alternative package managers.
</InfoBox>

<CodeBlock title="Install pnpm (faster)">

```bash
npm install -g pnpm
```

</CodeBlock>

<CodeBlock title="Install Yarn">

```bash
npm install -g yarn
```

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="4" title="Install development tools">

<SubSection title="Build tools">

<CodeBlock title="On Ubuntu/Debian">

```bash
sudo apt install -y build-essential
```

</CodeBlock>

<CodeBlock title="On CentOS/Rocky Linux">

```bash
sudo dnf groupinstall "Development Tools" -y
```

</CodeBlock>

</SubSection>

<SubSection title="Git">

<CodeBlock title="On Ubuntu/Debian">

```bash
sudo apt install -y git
```

</CodeBlock>

<CodeBlock title="On CentOS/Rocky Linux">

```bash
sudo dnf install -y git
```

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="5" title="Test your installation">

<SubSection title="Create a simple Node.js application">

<CodeBlock title="Create the project">

```bash
mkdir ~/test-nodejs
cd ~/test-nodejs
nano server.js
```

</CodeBlock>

<CodeBlock title="Application code (server.js)">

```javascript
const http = require('http');

const hostname = '0.0.0.0';
const port = 3000;

const server = http.createServer((req, res) => {
  res.statusCode = 200;
  res.setHeader('Content-Type', 'text/plain');
  res.end('Hello from Node.js on AtmosNode VPS!\n');
});

server.listen(port, hostname, () => {
  console.log(`Server running at http://${hostname}:${port}/`);
});
```

</CodeBlock>

<InfoBox>
ℹ️ Save and exit with Ctrl+X, then Y, then Enter.
</InfoBox>

</SubSection>

<SubSection title="Start the server">

<CodeBlock title="Start the application">

```bash
node server.js
```

</CodeBlock>

<CodeBlock title="Test from another terminal">

```bash
curl http://localhost:3000
```

</CodeBlock>

<SuccessBox>
✅ You should see: `Hello from Node.js on AtmosNode VPS!`
</SuccessBox>

</SubSection>

<SubSection title="Access from outside">

<WarningBox>
⚠️ **Access from the Internet**

To access your application from the Internet, you need to open the port in your firewall.
</WarningBox>

<CodeBlock title="With UFW">

```bash
sudo ufw allow 3000/tcp
```

</CodeBlock>

<CodeBlock title="With FirewallD">

```bash
sudo firewall-cmd --permanent --add-port=3000/tcp
sudo firewall-cmd --reload
```

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="6" title="Manage processes with PM2">

PM2 is a process manager to keep your Node.js applications online 24/7.

<ToolDescription>

**PM2 features:**

- Keep your applications online 24/7
- Automatically restart on crash
- Manage logs
- Start applications on server boot
- Cluster mode to use all CPU cores

</ToolDescription>

<SubSection title="Install PM2">

<CodeBlock>

```bash
npm install -g pm2
```

</CodeBlock>

</SubSection>

<SubSection title="Use PM2">

<CommandList>

**Start an application**
```bash
pm2 start server.js
```

**List applications**
```bash
pm2 list
```

**View logs**
```bash
pm2 logs
```

**Stop an application**
```bash
pm2 stop server
```

**Restart an application**
```bash
pm2 restart server
```

**Delete an application**
```bash
pm2 delete server
```

**Start PM2 on boot**
```bash
pm2 startup
pm2 save
```

</CommandList>

<ReferenceTable>

**Advanced PM2 commands:**

| Command | Description |
|---------|-------------|
| `pm2 monit` | Interactive dashboard |
| `pm2 status` | System statistics |
| `pm2 start server.js -i max` | Cluster mode (all cores) |
| `pm2 reload all` | Zero-downtime restart |

</ReferenceTable>

</SubSection>

</StepSection>

---

<StepSection number="7" title="Security best practices">

<SubSection title="Never run Node.js as root">

<CodeBlock title="Create a dedicated user">

```bash
sudo adduser nodejs
sudo su - nodejs
```

</CodeBlock>

</SubSection>

<SubSection title="Use a reverse proxy (Nginx)">

<CodeBlock title="Install Nginx">

```bash
# Ubuntu/Debian
sudo apt install -y nginx

# CentOS/Rocky
sudo dnf install -y nginx
```

</CodeBlock>

<CodeBlock title="Nginx configuration (/etc/nginx/sites-available/nodejs-app)">

```nginx
server {
    listen 80;
    server_name your-domain.com;

    location / {
        proxy_pass http://localhost:3000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }
}
```

</CodeBlock>

<CodeBlock title="Enable configuration">

```bash
sudo ln -s /etc/nginx/sites-available/nodejs-app /etc/nginx/sites-enabled/
sudo nginx -t
sudo systemctl reload nginx
```

</CodeBlock>

</SubSection>

<SubSection title="Secure environment variables">

<CodeBlock title="Install dotenv">

```bash
npm install dotenv
```

</CodeBlock>

<CodeBlock title="Create a .env file">

```bash
DATABASE_URL=your-database-url
API_KEY=your-secret-key
```

</CodeBlock>

<CodeBlock title="Use in code">

```javascript
require('dotenv').config();
const apiKey = process.env.API_KEY;
```

</CodeBlock>

</SubSection>

<SubSection title="Update regularly">

<CommandList>

**Check for vulnerabilities**
```bash
npm audit
```

**Fix automatically**
```bash
npm audit fix
```

**Update Node.js with nvm**
```bash
nvm install node --reinstall-packages-from=current
```

</CommandList>

</SubSection>

</StepSection>

---

<StepSection number="8" title="Verification checklist">

<Prerequisites>

**Verify that you have:**

✅ Node.js is installed and working (`node --version`)
✅ npm is installed and working (`npm --version`)
✅ nvm is configured to manage versions (if used)
✅ Build tools are installed
✅ PM2 is installed for process management
✅ An Nginx reverse proxy is configured
✅ Node.js applications don't run as root
✅ npm packages are up to date without vulnerabilities
✅ Sensitive environment variables are secured
✅ PM2 starts automatically on system boot

</Prerequisites>

</StepSection>

---

## 🎓 Useful resources

<ToolDescription>

**Official documentation:**

- **Node.js**: https://nodejs.org/docs
- **npm**: https://docs.npmjs.com
- **nvm**: https://github.com/nvm-sh/nvm
- **PM2**: https://pm2.keymetrics.io/docs
- **Node.js Best Practices**: https://github.com/goldbergyoni/nodebestpractices

</ToolDescription>

---

## 💬 Need Help?

If you encounter any difficulties:

<HelpCards>

<HelpCard title="📚 FAQ" link="/en/faq" />

<HelpCard title="💬 Discord" link="https://discord.gg/atmosnode">
24/7 Community Support
</HelpCard>

<HelpCard title="🎫 Support Ticket" link="https://client.atmosnode.com" />

</HelpCards>

---

<Congratulations>

**🎉 Congratulations!**

Node.js is now installed and configured on your VPS! You're ready to develop and deploy your server-side JavaScript applications.

</Congratulations>


Complete guide to install Node.js and npm on Ubuntu, Debian, CentOS, and Rocky Linux. Learn how to use nvm to manage multiple Node.js versions.

Install Node.js on Your Linux VPS


# Install phpMyAdmin for Pterodactyl

Easily manage your MySQL databases with phpMyAdmin directly from your Pterodactyl server.

---

## 📋 Prerequisites

<Prerequisites>

✅ A server with Pterodactyl Panel installed
✅ MySQL/MariaDB configured and functional
✅ Nginx or Apache installed
✅ Root or sudo access to the server
✅ A domain name or subdomain (recommended)

</Prerequisites>

---

<StepSection number="1" title="Install phpMyAdmin">

<SubSection title="On Ubuntu / Debian">

<CodeBlock title="Install packages">

```bash
# Update packages
sudo apt update

# Install phpMyAdmin
sudo apt install phpmyadmin php-mbstring php-zip php-gd php-json php-curl -y
```

</CodeBlock>

<InfoBox>
💡 **Tip:** During installation, select **"apache2"** with the spacebar even if you're using Nginx (we'll configure Nginx manually).
</InfoBox>

<ToolDescription>

**During installation:**

1. Select web server: **apache2** (press space then Enter)
2. Configure database: **Yes**
3. Set a password for phpMyAdmin

</ToolDescription>

</SubSection>

<SubSection title="On CentOS / Rocky Linux">

<CodeBlock>

```bash
# Install EPEL repository
sudo yum install epel-release -y

# Install phpMyAdmin
sudo yum install phpmyadmin -y
```

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="2" title="Configure phpMyAdmin">

<SubSection title="Enable Required PHP Extensions">

<CodeBlock>

```bash
# Enable mbstring
sudo phpenmod mbstring

# Restart PHP-FPM
sudo systemctl restart php8.1-fpm
```

</CodeBlock>

<InfoBox>
💡 **Note:** Replace `php8.1-fpm` with your PHP version (`php7.4-fpm`, `php8.2-fpm`, etc.).
</InfoBox>

</SubSection>

<SubSection title="Create a Symbolic Link">

<CodeBlock title="Option 1: Link to Pterodactyl">

```bash
# Create a link to Pterodactyl's web directory
sudo ln -s /usr/share/phpmyadmin /var/www/pterodactyl/public/phpmyadmin
```

</CodeBlock>

<CodeBlock title="Option 2: Separate directory (recommended)">

```bash
# Create a dedicated folder
sudo mkdir -p /var/www/phpmyadmin
sudo cp -r /usr/share/phpmyadmin/* /var/www/phpmyadmin/
sudo chown -R www-data:www-data /var/www/phpmyadmin
```

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="3" title="Configure Nginx">

Create an Nginx configuration for phpMyAdmin.

<CodeBlock title="Create configuration file">

```bash
sudo nano /etc/nginx/sites-available/phpmyadmin
```

</CodeBlock>

<CodeBlock title="Recommended configuration">

```nginx
server {
    listen 80;
    server_name phpmyadmin.yourdomain.com;

    root /var/www/phpmyadmin;
    index index.php index.html;

    # Logs
    access_log /var/log/nginx/phpmyadmin-access.log;
    error_log /var/log/nginx/phpmyadmin-error.log;

    # Security - Block access to sensitive files
    location ~ ^/(libraries|setup/frames|setup/libs) {
        deny all;
        return 404;
    }

    location / {
        try_files $uri $uri/ =404;
    }

    location ~ \.php$ {
        fastcgi_pass unix:/run/php/php8.1-fpm.sock;
        fastcgi_index index.php;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
    }

    # Block access to hidden files
    location ~ /\. {
        deny all;
    }
}
```

</CodeBlock>

<WarningBox>
⚠️ **Important**

Replace `phpmyadmin.yourdomain.com` with your own domain and `php8.1-fpm.sock` with your PHP version.
</WarningBox>

<CodeBlock title="Enable configuration">

```bash
# Create symbolic link
sudo ln -s /etc/nginx/sites-available/phpmyadmin /etc/nginx/sites-enabled/

# Test Nginx configuration
sudo nginx -t

# Restart Nginx
sudo systemctl restart nginx
```

</CodeBlock>

</StepSection>

---

<StepSection number="4" title="Secure phpMyAdmin with SSL">

Use Certbot to get a free SSL certificate.

<CodeBlock title="Install Certbot">

```bash
# Install Certbot
sudo apt install certbot python3-certbot-nginx -y

# Obtain SSL certificate
sudo certbot --nginx -d phpmyadmin.yourdomain.com
```

</CodeBlock>

<SuccessBox>
✅ Certbot will automatically configure Nginx to use HTTPS and redirect HTTP to HTTPS.
</SuccessBox>

</StepSection>

---

<StepSection number="5" title="Create a Dedicated MySQL User">

For better security, create a specific MySQL user for phpMyAdmin.

<CodeBlock title="Connect to MySQL">

```bash
# Connect to MySQL
sudo mysql -u root -p
```

</CodeBlock>

<CodeBlock title="Create user in MySQL">

```sql
-- Create a user with all privileges
CREATE USER 'phpmyadmin_user'@'localhost' IDENTIFIED BY 'strong_password';

-- Grant all privileges
GRANT ALL PRIVILEGES ON *.* TO 'phpmyadmin_user'@'localhost' WITH GRANT OPTION;

-- Apply changes
FLUSH PRIVILEGES;

-- Exit
EXIT;
```

</CodeBlock>

<InfoBox>
💡 **Tip:** Replace `strong_password` with a complex and unique password.
</InfoBox>

</StepSection>

---

<StepSection number="6" title="Strengthen Security">

<SubSection title="Configure HTTP Authentication">

Add an extra layer of security with HTTP authentication.

<CodeBlock title="Create password file">

```bash
# Install apache2-utils
sudo apt install apache2-utils -y

# Create a password file
sudo htpasswd -c /etc/nginx/.htpasswd admin_user
```

</CodeBlock>

<CodeBlock title="Modify Nginx configuration">

```bash
sudo nano /etc/nginx/sites-available/phpmyadmin
```

</CodeBlock>

<CodeBlock title="Add authentication">

```nginx
location / {
    auth_basic "Restricted Area";
    auth_basic_user_file /etc/nginx/.htpasswd;
    try_files $uri $uri/ =404;
}
```

</CodeBlock>

<CodeBlock title="Restart Nginx">

```bash
sudo systemctl restart nginx
```

</CodeBlock>

</SubSection>

<SubSection title="Change Access URL">

Modify the default URL for better security.

<CodeBlock title="Modify configuration">

```bash
sudo nano /etc/nginx/sites-available/phpmyadmin
```

</CodeBlock>

<CodeBlock title="Change the access path">

```nginx
location /my-secret-panel {
    auth_basic "Restricted Area";
    auth_basic_user_file /etc/nginx/.htpasswd;
    alias /var/www/phpmyadmin;
    index index.php;

    location ~ \.php$ {
        fastcgi_pass unix:/run/php/php8.1-fpm.sock;
        fastcgi_param SCRIPT_FILENAME $request_filename;
        include fastcgi_params;
    }
}
```

</CodeBlock>

</SubSection>

<SubSection title="Restrict Access by IP">

Limit phpMyAdmin access to specific IP addresses.

<CodeBlock>

```nginx
location /phpmyadmin {
    # Only allow these IPs
    allow 123.456.789.0;
    allow 192.168.1.0/24;
    deny all;

    auth_basic "Restricted Area";
    auth_basic_user_file /etc/nginx/.htpasswd;
    try_files $uri $uri/ =404;
}
```

</CodeBlock>

</SubSection>

</StepSection>

---

<StepSection number="7" title="Advanced phpMyAdmin Configuration">

Edit the configuration file to optimize phpMyAdmin.

<CodeBlock title="Edit configuration">

```bash
sudo nano /etc/phpmyadmin/config.inc.php
```

</CodeBlock>

<CodeBlock title="Recommended settings">

```php
// Increase session timeout
$cfg['LoginCookieValidity'] = 3600;

// Force HTTPS
$cfg['ForceSSL'] = true;

// Hide system databases
$cfg['Servers'][$i]['hide_db'] = '^(information_schema|performance_schema|mysql|sys)$';

// Limit number of displayed rows
$cfg['MaxRows'] = 50;

// Enable compression mode
$cfg['ZipDump'] = true;
$cfg['GZipDump'] = true;
```

</CodeBlock>

</StepSection>

---

<StepSection number="8" title="Verification and Testing">

Test your phpMyAdmin installation.

<ReferenceTable>

**Verification Checklist:**

| Item | Status |
|------|--------|
| phpMyAdmin accessible via HTTPS | ✅ |
| HTTP authentication works | ✅ |
| MySQL connection successful | ✅ |
| Valid SSL certificate | ✅ |
| Pterodactyl databases visible | ✅ |

</ReferenceTable>

<CodeBlock title="Access phpMyAdmin">

```
https://phpmyadmin.yourdomain.com
```

</CodeBlock>

<ToolDescription>

**Login with:**

- Username: `phpmyadmin_user` (or your MySQL user)
- Password: the one you set

</ToolDescription>

<SubSection title="Troubleshooting">

<CodeBlock title="403 Forbidden Error">

```bash
# Check permissions
sudo chown -R www-data:www-data /var/www/phpmyadmin
sudo chmod -R 755 /var/www/phpmyadmin
```

</CodeBlock>

<CodeBlock title="PHP-FPM Error">

```bash
# Check if PHP-FPM is running
sudo systemctl status php8.1-fpm

# Restart if necessary
sudo systemctl restart php8.1-fpm
```

</CodeBlock>

<CodeBlock title="MySQL Connection Error">

```bash
# Check if MySQL is running
sudo systemctl status mysql

# Test connection
mysql -u phpmyadmin_user -p
```

</CodeBlock>

</SubSection>

</StepSection>

---

## 💬 Need Help?

If you encounter difficulties:

<HelpCards>

<HelpCard title="📚 FAQ" link="/en/faq" />

<HelpCard title="💬 Discord" link="https://discord.gg/atmosnode">
24/7 Community Support
</HelpCard>

<HelpCard title="🎫 Support Ticket" link="https://client.atmosnode.com" />

</HelpCards>

---

<Congratulations>

**🎉 Congratulations!**

phpMyAdmin is now installed and secured on your Pterodactyl server. You can easily and securely manage your databases!

</Congratulations>


Complete guide to install and configure phpMyAdmin on your Pterodactyl panel. Easily manage your MySQL databases.

Documentation & Guides

Categories

Gaming

Getting Started

Tutorials

All Articles

Install a FiveM Server on Windows Server

Install a Minecraft Server on Debian

Getting Started with Your Linux VPS

Secure Your Linux VPS

Install Node.js on Your Linux VPS

Install phpMyAdmin for Pterodactyl