A token is refused

When Hetscale refuses a token, nothing is stored and nothing changes. Each heading below is the first sentence of a message the panel shows; under it, what the message means and what to do. A new token is created in the Hetzner Console: your project → Security → API tokens → Generate API token.

This does not look like a Hetzner API token.

What you pasted is empty, or it holds a space or a line break. Paste the whole token on one line. A token that was cut short passes this check and gets the next message instead.

Hetzner does not accept this token.

Hetzner does not know the token: it may be mistyped or revoked. Create a new token in the Hetzner Console, with the Read permission to connect a project or refresh a report, with Read & Write to go Live.

This token can create and delete servers.

Observe works with a Read token only, so a token that can write is refused when you connect a project. Create a token with the Read permission.

When you replace a project’s token, on its overview or with Refresh report, the message reads “This project reads with a Read token, and this token can write.” Hetscale takes a Read & Write token only when a node group goes Live, on its Go Live page (Go Live); paste a Read token of the same project instead.

This token can only read.

Going Live needs a token with the Read & Write permission: create one in the node group’s project, choose Connect Read & Write on its Go Live page and paste it under Read & Write token.

When you replace a project’s token, on its overview or with Refresh report, the message reads “A group of this project is Live, paused or rehearsing, so its token must be able to write.” Paste a Read & Write token of the same project.

This token is already connected to another Hetscale organization.

Another organization holds this token, and each organization connects its own. Create a separate token for this organization, with the permission you need.

This token is already connected to this organization.

The token is already the token of one of your projects. Replacing a project’s token takes a new one: create it in the Hetzner Console.

This token belongs to another Hetzner project: it cannot see the group’s load balancer.

This message comes from Connect Read & Write on a node group’s Go Live page. The token works, but it does not see the node group’s load balancer: create the token in the node group’s project, and check that the load balancer still exists.

When you replace a project’s token, on its overview or with Refresh report, the message reads “None of this project’s load balancers (…) is visible with this token.”, with the ids of the load balancers of the project’s node groups and of its latest read in the brackets. Hetscale knows a load balancer by the id Hetzner gave it, not by its name, so one created again under the same name has another id. If the token belongs to another project, paste the right project’s token. If none of those load balancers exists any more, the node groups cannot come back: archive the node groups, then the project, connect the project again and start observing on the new load balancer.

This token belongs to …, a project you already connected.

A project is connected once. Hetscale recognises it by a load balancer it knows from it: one of its node groups’ load balancers, archived node groups included, or one its latest read listed. The token sees such a load balancer of the project the message names. Replace the token there, with Replace token on its overview (Replace a project’s token). When that project is in the Archive, the message says “a project in the Archive”: restore it first (Archive and restore).

This project is in the Archive.

A project’s token is replaced only outside the Archive. Restore the project, then replace its token.

Hetscale knows no load balancer of this project to recognise a new token by.

This is the tooltip of Replace token when the button is disabled; no token is asked for. The project has no node group, and its latest read listed no load balancer, so nothing would show that a new token belongs to it. Connect it as a new project instead (Connect a project).

Hetzner’s rate limit for this project is spent right now.

Hetzner allows 3,600 API requests an hour per project, shared by every tool that uses the project. Try again in a few minutes, or after the time the message names.

Hetzner did not answer.

Hetzner’s API did not answer. Try again in a minute.

Hetzner answered the level check in an unexpected way

Before it stores a token, Hetscale checks its permission, and Hetzner answered that check in a way Hetscale does not recognise; the message shows Hetzner’s code. Write to support with that code.