Frequently asked questions
Answers to common questions about Wibbix.
What is Wibbix?
Wibbix is a life checker for remote WiFi bridges and any other network node. A desktop app runs the availability checks, stores the results locally, and syncs them to the server. The website shows the availability data, an interactive map and a network schema.
How does Wibbix check whether a node is alive?
By default the desktop app sends ICMP echo requests (a ping) to the node over raw sockets and aggregates several probes per check: availability is the share of successful replies and the RTT is their average.
Each node can optionally set a check port (1–65535). When a check port is set, Wibbix performs a TCP connect to ip:port instead of ICMP — the same number of attempts per check, aggregated the same way (availability = share of successful connects, RTT = average connect time).
Why does the ICMP check need elevated privileges, and the TCP check does not?
ICMP checks use raw sockets, which the operating system only allows for privileged processes: administrator on Windows, root or a setcap capability on Linux, and root on macOS.
The TCP check port path uses an ordinary TCP connect and needs no elevated privileges, so a TCP-only node can be checked even on a machine where ICMP is not available.
Which operating systems does the desktop app support?
The desktop app runs on Windows, macOS and Linux. Builds for each platform are available on the Downloads page.
Does the app work offline?
Yes. The desktop app is offline-first: checks keep running and their results are stored in a local SQLite database. When the machine is online again the results are synced to the server, where the website reads them.
What data does the desktop app collect?
Besides the availability results, the app periodically uploads structured logs and two device snapshots: system info (local IP/MAC addresses, hostname, OS and version, architecture, CPU and RAM, uptime, timezone/locale, app version, a per-install device ID and ICMP capability) and a running-process list. The server also records the client's public IP.
This helps with support and diagnostics. See the Privacy page for the full list, retention periods and the reasons the data is collected.
How do I connect the Telegram bot?
Desktop Settings shows a one-time linking code. Send the bot your login and that code (for example, /link <code>) and the bot links your Telegram chat to that account only.
Once linked, the bot notifies you when a node goes down (after several consecutive failed checks, to damp flapping) and recovers, and it answers interactive commands in all five interface languages.
How does licensing and payment work?
A license is a key with an expiry date, validated on login on both the website and the app. You register on the website, then buy a license in one of three plans (1, 6 or 12 months). Payment is handled by the NOWPayments cryptocurrency payment processor; when a payment is confirmed a license is issued automatically and the expiry stacks onto any remaining time.
Where do I download the app?
From the Downloads page, which lists the latest builds for Windows, macOS and Linux. It is public, so you can download without signing in.
Can I add or edit nodes on the website?
Not in this version. The website is read-only: it shows the dashboard, map and analytics. Creating, editing and deleting nodes and their links happens in the desktop app.