Troubleshooting

Common setup failures and what to check first.

Agent is not connected

Check the service logs, API key, and cloud URL.

systemctl status borela-agent
journalctl -u borela-agent -f

Database cannot be read

The borela user needs read access to the SQLite file and execute access on its parent directory.

namei -l /home/deploy/app/data/app.db

No restore points

Wait for the first successful backup ack, then list snapshots again.

borela-agent snapshots -project app

Payment required

The agent keeps local acks when the subscription is lapsed. Open the dashboard billing link and resume the subscription.