The main requirement is a unique, free port

• 1. Create a new folder for the bot (in the example, folder hb1). This way you can install many bots in separate folders hb1, hb2...:
  mkdir -p /opt/hb1
• 2. Enter the created folder:
  cd /opt/hb1
• 3. Download and run the install_local.sh script:
  wget -qO- https://raw.githubusercontent.com/ksandric/hamster-bot/refs/heads/master/install_local.sh | bash
  This command downloads the install_local.sh script and runs it. (the script downloads → unpacks the zip → creates a .service in systemd)
• 4. During the process, the script will ask for a port and will check if it is free

Done! The bot is installed in the hb4 folder and a service named hb4.serviece will be started.
The terminal will show the bot log in real time. You can proceed to add API keys and configure strategies.

When you have 2 or more bots running on your VPS:
/opt/hb1
/opt/hb2
/opt/hb3

To update the bot in /opt/hb2, run the following commands in order:

• 1. Go to the target folder (example: hb2):
  cd /opt/hb2
• 2. Download and run the update_local.sh script:
  wget -qO- https://raw.githubusercontent.com/ksandric/hamster-bot/refs/heads/master/update_local.sh | bash

Done! Only the bot in /hb2 will be updated and restarted. The script automatically finds the service associated with the selected folder.

If you installed many different bots on your Linux VPS and can’t tell which .service belongs to which bot folder, use this command:
grep -rl "hb_c" /usr/lib/systemd/system/

This command lists all services that reference the executable hb_c (the bot binary). This helps you find the correct service and the folder it belongs to.

In the screenshot, there are 5 services but only (2) bot folders — meaning there are extra services.

If you use a folder name as the search string, you’ll get a list of services pointing to that folder:
grep -rl "/hb/" /usr/lib/systemd/system/

If you want to remove a bot service, run:
1. systemctl stop hb2.service - stop the hb2 service
2. systemctl disable hb2.service - disable the hb2 service
3. rm -rf /usr/lib/systemd/system/hb2.service - remove the hb2.service file

wget -qO- https://raw.githubusercontent.com/ksandric/hamster-bot/refs/heads/master/restart_all.sh | bash

1. This script finds all services associated with the bot and separately lists which ones are currently enabled.
2. Restarts only the enabled ones with a 15-second pause between services.

wget -qO- https://raw.githubusercontent.com/ksandric/hamster-bot/refs/heads/master/update_all.sh | bash

1. This script finds all services associated with the bot and separately lists which ones are currently enabled.
2. Updates only the active bots.

Video guide link: youtu.be/jxb6aZQwtN4

First, connect to your VPS via SSH using termius (or putty)

• Create a folder for the bot (example folder name "hb")
  mkdir -p /opt/hb
• Go to the folder
  cd /opt/hb
• Download the zip archive
  wget https://github.com/ksandric/hamster-bot/blob/master/hb_linux-x64.zip?raw=true
• If unzip is not installed, install it
  sudo apt install unzip
• Unpack the archive
  unzip hb_linux-x64.zip?raw=true
• Delete the zip archive
  rm -rf hb_linux-x64.zip?raw=true
• Make the file executable (the binary is hb_c)
  chmod +x ./hb_c

After that you can run it with ./hb_c, but that is not suitable for the bot. You should create a service so the bot runs in the background and doesn’t stop when the terminal session ends.

• Go to the directory
  cd /usr/lib/systemd/system/
• Create the hamster-bot_1.service file. You can create it with:
  nano hamster-bot_1.service
  (the name can be any, the format is always .service. You can create many services, but make sure the bots use different ports in their configs)

File contents: hamster-bot_1.service
[Unit]
Description=hamster-bot_1
After=multi-user.target
[Service]
Environment="DOTNET_BUNDLE_EXTRACT_BASE_DIR=%h/.net"
Type=simple
ExecStart=/opt/hb/hb_c
WorkingDirectory=/opt/hb
RestartSec=61
Restart=always
[Install]
WantedBy=multi-user.target


• Save changes and close the file with Ctrl+x, then press Y, then Enter
• Run the commands:
• systemctl daemon-reload
• systemctl enable hamster-bot_1.service
• apt-get update
• apt-get install -y libfreetype6
• apt-get install -y libfontconfig1
• apt-get install -y fontconfig
• sudo timedatectl set-timezone UTC
• Optionally install fail2ban:
  apt-get install fail2ban
• To open the port where the bot runs so the web interface is accessible by your server IP (example port 80):
• iptables -I INPUT -p tcp --dport 80 -j ACCEPT
• ufw allow 80
• To start the service, run:
  systemctl start hamster-bot_1.service
• Done! The service is now available and will start automatically with the server (+ auto‑restart if it stops). To manage the service:
• View log in real time: journalctl --follow -u hamster-bot_1.service
• Check status: systemctl status hamster-bot_1.service
• Stop: systemctl stop hamster-bot_1.service
• Disable: systemctl disable hamster-bot_1.service
• Restart: systemctl restart hamster-bot_1.service
• After starting, to read the bot log in real time:
• Go to the folder cd /opt/hb/logs
• Open the log tail -f log_date_here.log (general log + logs per strategy)

Video guide link: youtu.be/FJgu7OfgUWU

First, connect to your VPS via SSH using termius (or putty)

Example service name: "hamster-bot_1.service".
Bot files folder: "/opt/hb"

1. Stop the bot (stop the service)
   systemctl stop hamster-bot_1.service
2. Go to the bot folder
   cd /opt/hb
3. Download the zip archive
   wget https://github.com/ksandric/hamster-bot/blob/master/hb_linux-x64.zip?raw=true
4. Unpack with file replacement (settings_program.json will be ignored)
   unzip -u hb_linux-x64.zip?raw=true -x settings_program.json
5. Delete the zip archive
   rm -rf hb_linux-x64.zip?raw=true
6. Make the file executable again
   chmod +x ./hb_c
7. Start the bot
   systemctl restart hamster-bot_1.service
8. Done! The bot will continue running with your settings. Everything is applied without closing positions or orders

If your Linux VPS has low memory:

(1) View available and used memory:
df -h

(2) Utility with memory usage visualization. For easy search of large folders:
ncdu /

I often notice that on Ubuntu systems with limited memory, system logs can take up a lot of space. These two commands will free up space:
journalctl --vacuum-size=100M
rm /var/log/*.[0-9]
But it's better to adjust the config to prevent this from happening.

Bot logs can also take up a lot of space in some situations. They are stored in the /logs folder. Here are the log parameters in the config:
"log": {
"log_months": 2, — how many months to keep logs
"debug_mode": false,
"log_size_mb": 50, — log file size limit
"log_files_count": 5 — file rotation N times when size limit is reached },
The bot logs CPU, RAM, and disk usage. It sends an alert to Telegram when critical values are reached.