Security warnings

When you add a cluster, and every time Drover connects, it checks how the phone reaches it. Anything risky shows as a warning on the cluster's Overview and in the connection checks. Warnings never block you; they make sure an exposed cluster is a choice, not an accident.

The warnings

Public exposure

The address resolves to a public IP and the agent has ACLs off or no TLS. Anyone on the internet who finds it may be able to read your jobs, or run, stop and exec into them. This is the one warning that asks before connecting: Cancel, Connect read-only, or Connect anyway.

Fix: put the agent behind a VPN or a firewall, or turn on both ACLs and TLS. The warning goes away once the address is private or both are on.

ACLs disabled

The cluster runs without ACLs, so anyone who can reach the agent can do anything, no token needed. Fine on a lab cluster inside a VPN; risky anywhere else.

Fix: bootstrap Nomad's ACL system and give Drover its own token.

No TLS

Drover talks plain HTTP to this cluster, so requests and your token travel unencrypted unless a VPN tunnel encrypts them.

Fix: turn on TLS for the HTTP API, or mute this warning for a cluster you only reach through a tunnel.

Certificate checks off

Skip certificate verification is on for this cluster. Drover accepts any certificate, so someone on the network could pose as your agent and receive your token.

Fix: import the cluster's CA and set the server name (see TLS), then turn skip verification off.

Token expiring

The ACL token expires within seven days. After that, Drover can't read the cluster.

Fix: create a new token and paste it on the cluster's Security screen. The old one stays in use until the new one tests fine.

Turning warnings off

• For one cluster: on the cluster's Security screen, mute a warning. Other clusters still warn.
• For every cluster: More › Settings › Security warnings turns each kind off globally.

Turning a warning off only stops it warning. The connection checklist still shows the facts, without the warning colours.

Read-only, by choice

Any cluster can be kept read-only: Drover offers it when a cluster looks exposed, and you can switch it from the explanation that appears when you tap Read-only on the Overview. More › Settings › Read-only mode does the same for every cluster at once. Read-only hides every action that writes, and exec; jobs, logs and files still load.