How to Host a Discord Bot 24/7 on a Linux VPS

A Discord bot running on your laptop works fine until the first Windows reboot or Wi-Fi outage. To keep a bot available 24 hours a day, you need a server that stays on all the time — and a cheap Linux VPS solves that for under USD 6/month with room to grow.

This tutorial targets developers who already have a working bot in discord.js (Node.js) or discord.py (Python) and want to deploy it to production for the first time. You will learn how to prepare the VPS, transfer your code, manage the process with PM2 or systemd, and make sure the bot restarts automatically if the VPS reboots.

Estimated time: 30-45 minutes from the first SSH connection to a bot online with auto-restart configured.

Prerequisites

Keep the bot token handy (from https://discord.com/developers/applications → your application → Bot → Reset Token). You will paste this token into a .env file on the VPS.

SSH connection and dedicated user

Running a bot as root is a bad practice — any compromised dependency becomes full access to the VPS. Create a dedicated user to isolate the process.

ssh root@your-vps-ip

adduser bot
usermod -aG sudo bot

su - bot
whoami

Installing the runtime

Choose the stack according to your bot’s language. This section covers Node.js (for discord.js) and Python (for discord.py) — skip to the appropriate subsection.

Node.js for discord.js

The recommended way to install Node.js on Ubuntu is via NodeSource, which keeps packages updated for each LTS major version.

curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
sudo apt install -y nodejs

node --version
npm --version

Python for discord.py

Ubuntu 24.04 ships with Python 3.12. You only need venv and pip to isolate dependencies.

sudo apt update
sudo apt install -y python3-pip python3-venv git

Transferring the code

You can upload your code via Git (recommended — keeps history and makes updates easier) or SCP directly from your computer.

cd ~
git clone https://github.com/your-username/your-bot.git
cd your-bot

scp -r ./your-bot bot@your-vps-ip:/home/bot/

npm install --production

python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt

Environment variables

Never leave the bot token hardcoded in the source. Use a .env file with restricted permissions.

nano .env

DISCORD_TOKEN=your-token-here
NODE_ENV=production

chmod 600 .env

Process management with PM2

PM2 is the de facto process manager for the Node.js ecosystem. It does automatic restart on crash, keeps structured logs, and integrates with systemd to survive a reboot.

sudo npm install -g pm2

pm2 start index.js --name my-bot

pm2 startup
pm2 save

Process management with systemd

For Python bots or when you prefer the base Linux stack, systemd is the native alternative. Nothing to install — it ships with Ubuntu.

sudo nano /etc/systemd/system/my-bot.service

[Unit]
Description=My Discord Bot
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=bot
WorkingDirectory=/home/bot/your-bot
ExecStart=/home/bot/your-bot/venv/bin/python3 bot.py
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

sudo systemctl daemon-reload
sudo systemctl enable my-bot
sudo systemctl start my-bot

Verification

Confirm the bot is running and responding on Discord.

With PM2:

pm2 status
pm2 logs my-bot --lines 50

You should see the bot with online status in the table and logs showing messages like Logged in as MyBot#1234.

With systemd:

sudo systemctl status my-bot
sudo journalctl -u my-bot -n 50 -f

Output should show active (running) in green. The -f flag on journalctl tails logs in real time (Ctrl+C to exit).

On Discord itself, go to your test server and send a command the bot responds to. Confirm it appears online (green dot) in the member list.

Troubleshooting

Bot shows offline status even though the process is running

Usually an invalid token (you generated a new one and forgot to update .env) or the bot does not have the right intent enabled in the Developer Portal. Check PM2/journalctl logs for Invalid Token or DisallowedIntents.

”EADDRINUSE” error at startup

You have another instance of the bot running. List with pm2 list or sudo systemctl status my-bot and stop the duplicate before restarting.

Bot consumes growing RAM until it crashes

Memory leak in the code — common in message handlers that accumulate state without clearing it. Use pm2 monit to watch usage in real time. To mitigate while investigating, configure --max-memory-restart 500M in PM2, which restarts the process when it exceeds 500 MB.

Next steps

With the bot running 24/7, consider the next production-focused steps:

• Configure automatic backups of the code and database (if any) to another location — rsync via cron to another server or an S3-compatible service
• Add external monitoring (UptimeRobot, Healthchecks.io) that pings your bot or a health-check endpoint
• Implement structured logging (Winston for Node.js, structlog for Python) and centralize it in Loki or Elasticsearch if you run multiple bots
• Use native sharding from discord.js/discord.py if the bot grows past 2,500 servers
• If you are putting this into serious production, a Hostini VPS in Brazil delivers low latency to Discord’s South American gateways and scheduled snapshots to restore the bot in minutes if something goes wrong.