Skip to content

Connect your own server

If you already rent a server somewhere else, you can run it with Netkeel instead of ordering a new one. You run one command on the machine as root. Netkeel then installs the same stack, backups and security it puts on every server, and the machine appears on your Servers page.

You pay your provider for the machine. Netkeel does not add an hourly charge for it. You still need a payment method on file: it pays for off-site backups and any extras you turn on. It still counts toward your server limit.

  • A fresh Ubuntu 24.04 install, 64-bit. Nothing else installed on it: Netkeel sets up the whole web stack itself, so it cannot share the machine with Nginx, Apache, MariaDB, MySQL, PostgreSQL or PHP that is already there.
  • Root access over SSH.
  • An SSH key you log in with. Netkeel turns off SSH password logins on its servers, so a machine you only reach with a password would lock you out. Add your public key first (for example with ssh-copy-id).
  • Enough memory for what it will host: 1 GB for most applications, 2 GB for OpenClaw and Hermes Agent. At least 10 GB of free disk space.
  • Ports 80 and 443 free, and the machine able to reach https://agent.netkeel.com.

The command checks all of this before it changes anything. If something is wrong, it says what and stops.

  1. Open Servers and click Connect your own. (In Create server, this is the Connect your own switch at the top.)
  2. Name the server and choose what it will host, its database and its web server, as in Create a server. There is no region or size: the machine is the one you already have.
  3. Click Get the command.
  4. Open a terminal on your machine as root, paste the command and run it.
  5. Setup runs in the background and takes several minutes. You can close the terminal. The server shows Waiting for connection until the machine reports, then Installing stack, then Online.

If the command has expired, or you lost it, open the server on the Servers page and click Show a new command. The old one stops working.

What is different from a server Netkeel orders

Section titled “What is different from a server Netkeel orders”

Netkeel does not own or control the machine, so some actions that need the cloud provider are not available. The panel hides them:

  • Reboot, power, Upgrade plan and Storage: use your provider’s console, or run reboot on the machine.
  • Opening ports from the panel: the cloud firewall belongs to your provider. Netkeel’s own firewall on the machine still applies.

Everything else works as on any other server: applications, backups, off-site backups, the firewall rules on the server, the Netkeel agent’s updates and moving applications between servers.

On the server’s page, go to Settings and click Delete. Tick Yes, remove this server from Netkeel. and click Remove server. Netkeel stops managing it. The off-site copies of the applications that were on it stay under Backups › Deleted for 14 days after each application was deleted. Your machine is not deleted or switched off. It keeps running, and your sites, databases, firewall and SSH settings stay as they are.

If the machine is online, Netkeel switches its own agent off for you a few seconds after you confirm. If it is offline, or the agent does not answer, turn the agent off yourself:

Terminal window
sudo systemctl disable --now netkeel-supervisor-guard.service netkeel-logrotate.timer netkeel-analytics.timer netkeel-agent.service
  • The command says the machine is not suitable. Read its message: it names the check that failed. Nothing was changed, so fix it and run the command again.
  • The command says it is not valid any more. It expired or the machine already connected. Ask for a new command on the server’s page.
  • The server stays on Waiting for connection. The command was not run, or the machine cannot reach https://agent.netkeel.com. Check the machine’s outgoing connections and run the command again.
  • The server shows Setup failed. The setup on the machine did not finish. Its log is /var/log/netkeel-bootstrap.log. Remove the server, reinstall Ubuntu 24.04 on the machine and connect it again.

See also Getting help.