Replace a project's token

A project keeps its node groups, reports and timeline when its token changes: Replace token puts a new token of the same Hetzner project in place of the current one. Use it when the token stopped working, to rotate a token that still works, or to read a project again after its token was erased.

Where do I replace it?

Open Projects → the project → Overview. The token sits there with its permission and its state, next to Replace token; Erase token is in the More menu. Paste the new token under New token.

To refresh a node group’s report after the project’s token was erased or revoked, use Refresh report on the node group’s Report page, once its trial is over. It asks for a new Read token, or for a Read & Write token while a node group of the project outside the Archive is Live, paused or rehearsing, and puts it in place the same way.

What does Hetscale check?

The new token must read one of the load balancers Hetscale knows from the project: one of its node groups’ load balancers, archived node groups included, or one its latest read listed. 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. A token that sees none of them is refused, and the message names every id it looked for:

• 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.

The checks of a new connection come first. Each message and what to do are on A token is refused.

Which permission can the new token have?

• The same permission as now: accepted at any time.
• Read & Write in place of Read: only through Go Live, with Connect Read & Write on a node group’s Go Live page (Go Live).
• Read in place of Read & Write: only while no node group of the project outside the Archive is Live, paused or rehearsing.

What happens when it is replaced?

The old token is erased at that instant, and nothing moves: the project, its node groups, their reports and trials stay as they are. Hetscale reads the project at once, unless a read was asked for less than a minute before, and the timeline of each node group records the change.

If the old token had stopped working, because it was erased or Hetzner revoked it, the project’s Live node groups come back paused: Hetzner may have changed while nothing read it. Check their servers, then resume each one with Resume, beside Controls on its Overview. Rotating a token that still works changes nothing else.