Skip to content
SHC Docs

A Hostinger node

This page has not been walked: no SHC test account exists on Hostinger. Its command lines are what the CLI takes; its output lines are left open.

Hostinger sells virtual servers and nothing SHC can connect to: no managed DNS, no load balancer, no block volumes. There is no hostinger connection type. A Hostinger node is a node like any other, whose cloud and location are the names you give it, and whose deployments keep their data on its disk.

Every Hostinger VPS is a monthly subscription, not an hourly meter. A server you keep for ten minutes costs a month. Decide before you create one.

Create one VPS: Debian 13, data center fra, named after the node. It has no private network and no firewall resource, so allow the cluster ports with the firewall on the server itself. Install SHC on it. Call the node hst01.

The join asks home01 for its token over ssh, so give root on hst01 the learn nodes’ names and a key home01 accepts, as the learn nodes have.

hst01
$ ssh home01 shc node token --fields token -o text | shc node join - --name hst01 --cloud hostinger --location fra
...
home01
$ shc node ls
...
$ shc node info hst01
...
$ shc install ~/learn/nginx -s hstweb --where node=hst01 --expose 18087=nginx:80
...
hst01
$ curl -s http://localhost:18087/
...
home01
$ shc uninstall hstweb -y
...
hst01
$ shc node leave
...
home01
$ shc node ls
...

Cancel the VPS in the Hostinger panel.

This page leaves the cluster as the runtimes ladder left it: the learn nodes, with no cloud node and no connection.

Next: An OpenStack node.