Setup & help
Everything you need to run MyKAI Node on a Linux server, NAS or VPS.
Install
This one command is the all-in-one. No Docker yet? It installs the newest Docker first, then your Kaspa node. Paste it in a terminal on your server. No sudo needed in front, it asks for your password when it needs admin rights.
Leave blank for a fresh install. Paste your existing key to add this machine as a new node under the same account.
curl -fsSL https://mykai.dev/install.sh | bashSetting up Docker by itself works on the popular Linux versions: Ubuntu, Debian, Raspberry Pi OS, Fedora, CentOS, RHEL and Rocky. On a NAS, install Docker from its app store first (see On a NAS).
Downloads
- install.sh
Install script
The same script the command runs. Read it first if you like.
- docs.docker.com
Docker for Linux
The newest release, straight from Docker. Only needed if you'd rather install Docker yourself.
- Download
MyKAI for Windows
On a Windows PC? The 1-click installer is easier.
- GitHub
Source on GitHub
The install script and every release.
Before you start
- 64-bit Linux
- Intel/AMD (x86_64) or ARM64, like a Raspberry Pi 5, Ampere or Graviton. 32-bit systems won’t work.
- 200 GB free disk space, on an SSD
- A node normally uses 50–65 GB, but it grows to about 120 GB when the network is very busy. We saw that during the TPS world record.
- 16 GB RAM
- With 8 GB the first sync can run out of memory.
- Port 16111 open (optional)
- Open it in your router or VPS firewall so other nodes can connect to yours. Check your port
On a NAS
- Synology
- Install Container Manager from Package Center. Turn on SSH under Control Panel → Terminal & SNMP. Log in with SSH and paste the command.
- QNAP
- Install Container Station from App Center. Turn on SSH under Control Panel → Network & File Services → Telnet/SSH. Log in with SSH and paste the command.
- Unraid
- Turn Docker on under Settings → Docker. Open the terminal (the
>_icon at the top) and paste the command. - Another NAS
- Install Docker from its app store, turn on SSH, and paste the command.
Keep it running
The installer prints these for your machine at the end. Did it show them with sudo in front? Then use sudo too.
- See what it's doing
docker logs -f mykai-monitor- Update to the newest version
- Run the install command again. Your account key and synced data stay.
- Stop it
docker compose -f ~/.mykai-node/docker-compose.yml down- Remove everything, synced data included
docker compose -f ~/.mykai-node/docker-compose.yml down -v && rm -rf ~/.mykai-node- Your account key
- Saved in
~/.mykai-node/.mykai-account-key. Paste it on another machine to keep all your nodes under one account.
If something goes wrong
Find what you saw:
bash: /dev/fd/63: No such file or directory
That’s sudo in front of the older command, sudo bash <(curl …). Use the command at the top of this page instead. It asks for sudo itself.
Port 16111 is already in use
Another Kaspa node is running on this machine. MyKAI brings its own, so stop that one first, then run the command again.
This user isn't allowed to use Docker / Couldn't get admin rights
Run the command as root, or from an account that’s allowed to use sudo.
Docker couldn't be installed automatically
Docker’s own installer doesn’t know this Linux version. Install Docker yourself, then run the command again.
Docker isn't installed yet. On a Synology NAS…
Install Docker from your NAS app store first, see On a NAS.
Docker is installed but isn't running
Start Docker (sudo systemctl start docker, or turn it on in your NAS app), then run the command again.
Heads-up: … GB free on the disk Docker uses
The disk is on the small side. The node runs, but it can stop when the disk fills up. 200 GB free is safe.
Docker Hub is limiting downloads from this internet address
Wait an hour or so, then run the command again.
This is Windows (WSL)
On Windows the 1-click installer is the way to go.
It's running, but I don't see my node
Give it a few minutes, then check the live total on mykai.dev. The log shows what it’s doing: docker logs -f mykai-monitor. The first full sync takes a few hours.
Still stuck? Ask on Discord or open an issue on GitHub. Paste what the installer printed, that helps a lot.