Installation code
To buy a license, you need the installation code from the server that will run Gadka. The Server ID is only part of that code.
The installation code starts with GDK- and contains the Server ID and hardware fingerprint hashes. Enter it in the shop to get a key that works only on that server.
Install Gadka on the intended server using the .run installer, then get the code from that machine.
Copy the code in the app
- Sign in as the owner with 2FA enabled.
- Click Admin in the left sidebar and select License.
- Next to Installation code, click Copy installation code.
The page also shows the Server ID separately, with a Copy Server ID button.
Get the code on the server
Run this command as root to print the installation code.
sudo gadka --config /etc/gadka/gadka.yaml admin license requestTo print just the Server ID, run the second command.
sudo gadka --config /etc/gadka/gadka.yaml admin license server-idWhat determines the code
The Server ID depends on the machine identifier (product_uuid on physical servers and virtual machines). The hardware fingerprint covers eight components: the system identifier, motherboard, processor, RAM, graphics card, network cards, system disk and kernel. The key works when the Server ID and at least five of the eight components match.
On Linux, only root can read these identifiers. Gadka runs without root privileges, so the installer writes /etc/systemd/system/gadka.service.d/10-credentials.conf. This file tells systemd to pass the identifiers to the service.
Codes from containers or Kubernetes
Running Gadka in a container, on Kubernetes or in a configuration designed for high availability requires an Enterprise license. If you enter its code when buying Standard, the shop will reject the code and direct you to the contact form.
Missing Server ID
The license page says “The Server ID could not be determined, so the Free edition applies.”
This usually means the server was installed with an installer older than 0.3.2. Those versions did not create the file that grants access to the machine identifiers. Your data remains available.
Update the server using installer version 0.3.2 or later. The installer adds the missing file. Check its contents with this command.
cat /etc/systemd/system/gadka.service.d/10-credentials.confLook for at least one LoadCredential= line. If the message persists after the update, send us the full message using the contact form.