Gates

A gate is the noset program on one of your Linux servers. Your agents run inside it, and every action they take passes through it. Gates in the web app lists every gate of your organization.

Status

Each gate shows one status:

Status	Meaning
Online	The gate polled Noset in the last minute. Gates poll every 10 seconds.
Not polling	No poll for over a minute: the server is off, offline, or noset.service stopped.
Never polled	The gate was connected but has not polled yet.
Evidence mismatch	The gate’s evidence does not match what Noset holds. Look at it at once.

The Rules column says whether the gate applied the newest rules. Behind means it gets them on its next poll. Needs attention filters the list to gates that are not polling, behind, or show an alert.

While a gate cannot reach Noset it keeps its last rules: Deny keeps denying, Allow keeps running, and Ask gets “Noset cannot reach the approval service, try again later”. See the FAQ.

A gate’s page

Click a gate to see its host name, system, Noset version, who connected it (and whether with a token), the address it polls from, its key’s fingerprint, and its recent agent sessions.

Connect a server

Admins connect servers under Gates › Connect a server:

• With a browser: run the install command and noset login on the server, open the link it prints, check the code, name the gate and connect it. Step by step: Install the gate.
• With a token: for CI and many servers at once. Pick how long the token works and for how many servers, then run the two commands it shows on each server. The token is shown once; Noset keeps only its fingerprint. Treat it like a password. You can revoke a token in the list below it.

Each server gets its own key. No person’s login is stored on it.

Disconnect a gate

On a gate’s page, Disconnect stops it from getting rules and approvals. It keeps enforcing the rules it has until its offline limit runs out, and its evidence stays. To connect it again, run noset login on the server.