Server agent and check locations

Bekci's program can run on other servers in two different roles. They are separate records in the panel and don't show up on each other's screens:

The agent uses no database. If it can't reach the main server (your Bekci panel), it holds its results and sends them once the connection is back.

Before you start#

• BASE_URL must be right. The install command takes the address the agent connects to from BASE_URL. If the panel is at https://bekci.example.com, BASE_URL must be that too (how to set it).
• HTTPS is recommended. By default the agent refuses to connect to an unencrypted (http://) address; if the panel uses http://, the install command adds that permission (PROBE_ALLOW_INSECURE=1) itself, but the token then travels over the network unencrypted.
• The server you install the agent on must be able to reach your panel's address (an outgoing HTTPS connection is enough; you don't need to open any incoming port for the agent).

Install the server agent#

1. In the panel, click Add server on the Servers page.
2. Enter a Server name that will appear in the list and in notifications (e.g. “Web server Frankfurt”) and click Create.
3. Choose the Docker, Native (systemd) or Windows tab under Install method and copy the command.
4. Run the command on the server you want to watch, as described below.

Install a check location#

A check location checks your monitors from another city or network too. That way you can tell whether an outage is seen from one place only or from everywhere.

1. Under Settings → Check locations, click New check location.
2. Give it a short name describing the place (e.g. “Frankfurt”) and save.
3. Run the command shown on the server that will be the check location (it needs Docker), as root, pasting the whole command. It creates /etc/uptime-probe.env and a container named uptime-probe.
4. Close the window with I've copied it, close.
5. On a monitor's edit page, select this check location under Locations and choose the Outage rule: down when any location, the majority of locations or all locations fail.

Files the install creates#

Updating#

The agent does not update itself: the program is downloaded and verified once, and the same program is used on every restart. That way, even if the server running your panel is compromised, no new program lands on your servers by itself. To update your agents after updating Bekci:

1. Get the current install command from the panel. Since the token is only shown once, this regenerates it (the old token stops working immediately):

   • Server agent: on the server's page, Install command → Regenerate token and show command.
   • Check location: in the Settings → Check locations list, Regenerate token in the row's menu.

2. For Docker installs, remove the old one first:

   terminalCopy

   docker rm -f uptime-agent; docker volume rm uptime-agent-bin     # server agent
   docker rm -f uptime-probe; docker volume rm uptime-probe-bin     # check location

3. Run the new command. For systemd and Windows installs there's nothing to remove; the command replaces the program and the service.

Removing#

First delete the server or check location in the panel (its token stops working). Then, on the server where the agent runs:

docker rm -f uptime-agent
docker volume rm uptime-agent-bin
rm -f /etc/uptime-agent.env

docker rm -f uptime-probe
docker volume rm uptime-probe-bin
rm -f /etc/uptime-probe.env

systemctl disable --now uptime-agent
rm -f /etc/systemd/system/uptime-agent.service /usr/local/bin/uptime /etc/uptime-agent.env
systemctl daemon-reload

& "$env:ProgramFiles\Uptime\uptime.exe" service uninstall
Remove-Item -Recurse -Force "$env:ProgramFiles\Uptime"

IP lock#

For new agents Lock to IP is on by default: the IP address of the agent's first connection is recorded (the full address for IPv4, the /64 block for IPv6), and requests from any other address are refused afterwards. Even if the token is stolen, it can't be used from another machine.

If the server's IP address changes (e.g. you moved the server), reset the lock; the next connection records the new address:

• Server agent: on the server's page, Settings → Reset lock.
• Check location: in the Settings → Check locations list, Edit in the row's menu → Reset lock.

You can turn the lock off entirely in the same place (the Lock to IP switch). If you suspect the token leaked, regenerate it and run the install command again (the update steps).

Troubleshooting#

Logs: on Docker docker logs uptime-agent (for a check location uptime-probe), on systemd journalctl -u uptime-agent, on Windows C:\Program Files\Uptime\agent.log. The agent's log messages are in Turkish; the table gives their meaning.