Troubleshooting

Fix the most common Servor problems — unreachable servers, a broken agent, custom-domain and Cloudflare issues, and a locked vault.

Something not working? Start here. This hub points you to the exact fix for the problems people hit most, plus a quick decision guide so you land on the right page fast. If you just need a definition, see the glossary; for general questions, the FAQ.

Pick your problem

Server is unreachable

A server won't connect, shows unreachable, or commands don't run.

Repair the agent

The agent stopped reporting in and needs to be brought back online.

Custom domain / Cloudflare

Your status page domain won't verify or the certificate won't issue.

Vault is locked

You can't run commands, use the terminal, or the copilot.

Server shows "unreachable" or commands won't run

All day-to-day execution goes through the agent, not SSH. If the agent isn't reporting in, the server shows unreachable and nothing can run on it.

Check the server is actually online

Make sure the machine is powered on and has network access. A rebooted or suspended VPS takes the agent down with it.

Repair the agent

Use Repair the agent from the top bar or server settings. This reinstalls or restarts the agent over the initial SSH path. Open your servers to get there.

Work through the connection checklist

If it's still down, go through Connection issues — firewall, SSH access for setup, and outbound connectivity from the server.

SSH is only for setup

Servor uses SSH just for the initial probe, discovery and agent install. If SSH changed (new port, revoked key), repairing the agent may need it again. See What is SSH?.

The agent won't come back

If Repair the agent doesn't fix it, the usual causes are that the machine can't reach the internet outbound, a firewall blocks the connection, or the agent's service was removed. Re-running the one-line install from Add a server reinstalls it cleanly. Full details: Connection issues.

Custom domain won't verify (Cloudflare)

By far the most common status-page problem. If you use Cloudflare, the orange-cloud proxy must be turned off for your status-page record.

Set the record to DNS-only

In Cloudflare, open the DNS record for your status-page hostname and click the orange cloud so it turns grey (DNS-only). The orange proxy prevents the certificate from being issued.

Confirm the CNAME target

Make sure the record is a CNAME pointing at Servor's target exactly as shown in your status-page settings — no trailing typo, no extra subdomain.

Wait for DNS to propagate, then re-check

DNS changes can take a little while. Return to Custom domain and re-verify from your status pages.

Grey cloud, always

Even after it works, keep the record on grey cloud (DNS-only). Switching it back to the orange proxy later will break serving and the certificate again.

Vault is locked

If you see an unlock screen, or can't run commands, use the terminal or the copilot, your vault is locked. Enter your vault passphrase to unlock it for the session. Read-only viewers don't need to unlock. See Unlock your vault.

Forgot the passphrase? Servor can't reset it — use your recovery key (24 words). If you've lost both, encrypted data can't be recovered. See Account and security.

A teammate can't see anything

New members join instantly, but access to encrypted data needs a key grant, which happens automatically once any teammate with an unlocked vault is online. If they see a "waiting for a teammate to come online" screen, have someone unlock their vault to unblock it. See Invite teammates.

I'm not getting alerts

Check that you have an alert rule for the status change you care about, that a notification channel is connected and verified, and that a cooldown isn't suppressing repeats. Review them in Settings → Alerts. See Alerts.

A command was blocked

Servor's shared blacklist blocks known-dangerous commands (like rm -rf /) across the terminal, command runner and copilot. This is intentional and can't be disabled. Rework the command to avoid the destructive pattern.