777pinger · Linux download
Ubuntu private agent
For Ubuntu 24.04 x64. Includes Node.js and starts automatically with the computer.
Checking download availability…
Before you begin
Use an always-on Ubuntu 24.04 x64 computer or VM, with systemd 255 or newer, Python 3.12 or newer, administrator access and at least 500 MiB free. Use an active Pro or higher plan for private agents. The installer does not change your system Node, PATH or firewall, and does not reboot the computer.
TCP connection checks only: no Linux ping, discovery, port scanning or vulnerability checks. An accepted TCP connection does not prove an application or DNS query worked. Other Linux distributions, ARM, containers, WSL, macOS and routers are not qualified by this release.
Keep the computer awake and online. Allow outbound HTTPS to app.777pinger.com and access to your chosen TCP targets. A VM also needs its host and VM software running; this installer does not configure host autostart.
1. Download and verify
Use only this official HTTPS download page. This Linux archive is not publisher-signed. Its checksum checks the downloaded bytes against this page; it is not an independent publisher signature. Stop on browser security warnings or any mismatch.
In a terminal in your download folder, run this before extracting or running the package:
printf '%s %s\n' 'c45c70400fb4e5d2f879b9a60e20752dba46986bbbfecd9c5b76a0b72977ce99' '777pinger-ubuntu24-x64-0.1.0.tar.gz' | sha256sum --checkContinue only if it prints the archive name followed by OK. Extract the complete archive into a new empty folder, keep all files together, then open a terminal inside that folder.
sh ./setup checkThis read-only check verifies the package and computer requirements. It does not install an agent or request a token. Do not bypass a failed check.
2. Install a new location
- Open Private agents and create a new location. Choose its connection alerts. Do not reuse a location already running elsewhere.
- Read the included README.md, then run
sudo sh ./setup install. Confirm the named installation and paste the location’s one-time token only into the hidden prompt. Never put it in a command, screenshot or support chat. Clear your clipboard afterward. - Keep this package for status checks and removal. Installation creates the
777pinger-main.servicestartup service. Existing installations are never overwritten.
If you deliberately need another local instance, use --name office consistently with install, status and uninstall. This local name is separate from the location name in the dashboard. Stop any manual copy of the same cloud location before installing.
3. Confirm monitoring
Return to Private agents and wait for Connected. Create a Local port or service monitor and select this location. For a test, turn all notification channels off. Confirm a fresh saved result in monitor history at your normal plan interval. Installation success or a running service alone is not proof of monitoring.
Automatic startup after reboot and fresh scheduled TCP results were verified on Ubuntu 24.04 x64. This does not guarantee every machine configuration.
Status, updates and removal
sudo sh ./setup statusThe service runs as a non-root, isolated user. The connection token is encrypted using systemd’s local host key, not saved in commands or environment variables. This is not TPM sealing or full-disk encryption: protect VM images and backups, and never clone a connected agent.
Updates are manual until you explicitly enable the optional updater. Follow the signed automatic-updater setup guide to prepare it and choose when updates may start. This base installer never enrolls an existing agent automatically and does not include in-place repair. If installation fails after creating files, those files are retained for support review. Do not repeatedly retry or delete them to force installation.
Before removing an agent, review its monitor and connection-alert settings to avoid unintended outage notifications. Then run:
sudo sh ./setup uninstallConfirmation permanently removes only that local instance’s service, program files and encrypted token. Cloud monitors, history and token authorization remain. Revoke the location separately if it must no longer connect. Your other agents and system Node are unchanged.
If you have prepared the optional updater, do not use the manual uninstall command above. Disable future updates and contact support for reviewed removal of the updater and agent together.
Release details
Installer 0.1.0 · agent 0.3.1 · Node.js 24.21.0 · 44,582,796 bytes.
SHA-256:
c45c70400fb4e5d2f879b9a60e20752dba46986bbbfecd9c5b76a0b72977ce99