Keep your Ubuntu agent up to date

Before you begin

This release is qualified for Ubuntu 24.04 x64, using the official agent 0.3.1 installer with Node.js 24.21.0. Install and confirm that agent first using the Ubuntu guide. You need administrator access, system Python 3.12, OpenSSL, systemd 255 or newer, at least 1 GiB of free space, and outbound HTTPS to app.777pinger.com.

Existing agents are never enrolled remotely. Prepare the updater only on the computer you choose. A pre-existing, partially installed, modified, or unsupported updater stops for review rather than being overwritten. Windows unattended updates, other Linux distributions, ARM, macOS and routers are not covered by this release.

1. Download and verify

Download the updater setup helper from this official HTTPS page. The helper contains the expected publisher fingerprint and verifies the signed package before extracting any program code. Do not use a helper from an email attachment or an unrelated website, and do not bypass security warnings.

In its download folder, run this verification-only command:

/usr/bin/python3.12 -I -B ./777pinger-updater-setup.py

It downloads about 90 MB and should report that the 777 Easy LLC updater signature and all package files were verified. It does not change your agent, ask for a token, or enable updates. Stop if verification fails.

2. Prepare the updater—still off

Run the following and confirm locally. This stages only the verified package in a new protected folder:

sudo /usr/bin/python3.12 -I -B ./777pinger-updater-setup.py --prepare

Then run the command it prints. For the default local installation name:

sudo /usr/bin/python3.12 -I -B /opt/777pinger/updater-setup-20260920/package/launcher.py --install --name main

This checks the known installed agent and prepares disabled updater services. It does not replace your token or agent program and does not enable an update schedule. Keep any partial staging if it stops; contact support rather than deleting safety records to force another attempt.

3. Choose your update settings

These controls generate commands for your Ubuntu terminal. Nothing changes when you edit this page. Review and confirm each change on the computer running the agent.

Use the local name chosen during installation, usually main—not the dashboard location name. Use a named time zone such as America/New_York or Europe/London. Daylight-saving changes follow that zone. An overnight window belongs to the day it starts.

Pause for 24 hours Clear pause

Enable automatic updates

sudo /usr/bin/python3.12 -I -B /opt/777pinger/updater/controller/linux-pilot-controls.py enable main --policy-json '{"schema":1,"mode":"automatic","timeZone":"UTC","window":null,"pauseUntil":null}'

Change the schedule or pause an enabled updater

sudo /usr/bin/python3.12 -I -B /opt/777pinger/updater/controller/linux-pilot-controls.py configure main --policy-json '{"schema":1,"mode":"automatic","timeZone":"UTC","window":null,"pauseUntil":null}'

Changing the schedule does not turn on a disabled updater. Use Enable when you want to resume a disabled updater.

Check status

sudo /usr/bin/python3.12 -I -B /opt/777pinger/updater/controller/linux-pilot-controls.py status main

Disable future automatic updates

sudo /usr/bin/python3.12 -I -B /opt/777pinger/updater/controller/linux-pilot-controls.py disable main

For a change, the terminal shows the exact policy and a confirmation phrase. Type that phrase only after reviewing it. Disabling or pausing does not interrupt an update already running. Monitoring continues; a software update briefly restarts this agent.

What to expect

The updater accepts only authenticated stable releases that pass its version, rollout, schedule and recovery checks. An expired or invalid release is not installed. If verification or recovery needs attention, it stops rather than repeatedly replacing files.

After enabling or after an update, check the local status, then confirm Connected and a fresh saved result in the dashboard. A running service alone is not proof of monitoring. Keep the computer and any VM host awake and online. No reboot is required for an agent update.

Keep protected update records for troubleshooting, but never send your agent token. This updater does not change billing, monitor targets, alert channels or text-message hours.

Removing an updater-enabled installation

Disable future updates first, then contact support for reviewed removal of the updater services and agent together. The original manual installer’s uninstall command is not the removal procedure for an updater-enabled installation. Do not delete update or recovery records by hand.