Setup Guide

Gnomes Manager runs two ways. Pick the one that matches how you bot β€” most people running multiple servers will want the second.

β‘  Local setup β€” one PC

This is the default and needs no configuration. Best if you run your accounts on a single computer.

  1. Install

    Download the Windows installer from the home page and run it.

  2. Sign in & subscribe

    Create your account in the app, pick a plan, and pay in crypto (your first month is 50% off). This unlocks launching.

  3. Import & launch

    Paste your accounts and proxies, then hit launch. The dashboard and the live mosaic are right there on your PC.

That's it. Nothing is exposed to the internet β€” the dashboard is only reachable on your own machine. You can switch to the control-hub setup any time.

β‘‘ Control hub β€” manage many servers

If you run bots on several servers across different networks, host the control hub on a small VPS. Every agent β€” and your browser β€” connects to that one hub, so you see and control everything from a single dashboard, from anywhere.

Your browser ─────────────┐ β–Ό [ Control Hub on a VPS ] ◄──── Agent on bot server #1 hub.yourdomain.com (HTTPS)◄──── Agent on bot server #2 ◄──── Agent on bot server #3 (any network)
You likely already have what you need. Any cheap Linux VPS (1 vCPU / 1 GB RAM) runs the hub β€” it's just a lightweight Node service. If you rent botting servers, one of them (or a separate $4/mo VPS) works fine.
  1. Get a VPS and point a subdomain at it

    Spin up an Ubuntu/Debian VPS. In your domain's DNS, add an A record like hub.yourdomain.com β†’ your-VPS-IP.

  2. Install Caddy (automatic HTTPS)

    Caddy gives your hub a real HTTPS certificate with zero fuss:

    sudo apt update && sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https curl
    curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
    curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list
    sudo apt update && sudo apt install -y caddy
  3. Upload the hub and run setup

    Put the hub files in /opt/gnomes-master, then run the one-shot setup β€” it installs Node, dependencies, generates a strong access token, sets up the database, and starts the hub as a background service:

    cd /opt/gnomes-master && sudo bash setup.sh

    Write down the AGENT_TOKEN it prints β€” you'll use it on every agent.

  4. Turn on HTTPS

    Edit the included Caddyfile.example to use your subdomain, then:

    sudo cp Caddyfile.example /etc/caddy/Caddyfile
    sudo systemctl reload caddy
  5. Connect your agents

    On each bot machine, open Gnomes Manager, choose β€œConnect to a remote hub”, and enter your hub URL (https://hub.yourdomain.com) and the token from step 3. The agent links up and its clients appear on the hub.

  6. Open your dashboard from anywhere

    Go to https://hub.yourdomain.com in any browser β€” desktop or phone β€” sign in, and you'll see every server's accounts and the live mosaic in one place.

Is it safe to put online?

Yes β€” and the app keeps you safe by default rather than leaving it to you:

  • Strong access required. The hub refuses to start if it's public without a strong token, so it can never go live wide-open.
  • HTTPS enforced. Logins use secure cookies and Caddy encrypts all traffic β€” nothing is sent in the clear.
  • Login-gated. Only your signed-in account can reach the dashboard; agents authenticate with the shared token. Brute-force attempts are rate-limited.
  • Credentials encrypted at rest. Account passwords and 2FA secrets are AES-256 encrypted on the hub. Back up the data/ folder β€” it holds the encryption key; losing it means stored credentials can't be recovered.
One rule: never open the hub's port directly to the internet β€” always go through HTTPS (Caddy). The setup above does this for you.

Need a hand?

Email support@gnomesmanager.com and we'll walk you through it.