Server agent installed and externally reachable

Hi UptimeMonster team,

I’m on an AppSumo Tier 4 lifetime plan. Your server-monitor agent shows “This server is not connected with agent” in the dashboard, and after systematic network-level diagnosis I can demonstrate the failure is on your platform’s side. Details below.

Server entry: name classbasics_com, host 115.70.64.123 (static IP), check interval 1 minute, agent public key 88567aeb-60b4-43a6-aae4-c18015dd017e.

What I’ve verified on my side:

1. Agent installed and running: umon.service active, umon_listener (package umon 1.0.0-1.el7) listening on 0.0.0.0:5991, API/secret keys present in /etc/umon/umon.cfg. Local TCP connections to port 5991 succeed.
2. Port forward configured: WAN 115.70.64.123:5991 → agent host :5991 (TCP).
3. External reachability independently proven: third-party TCP checks (check-host.net) from multiple countries (Switzerland, India, USA) completed full TCP handshakes with the agent through the forward — confirmed via router connection-tracking showing ASSURED bidirectional sessions.
4. Your platform never connects: router NAT packet counters on the 5991 forward, plus continuous connection-table monitoring over an extended window — including the minutes immediately after pressing Activate with the 1-minute interval — recorded zero inbound connection attempts from any UptimeMonster address. Your documented monitoring IP 162.55.41.109 has never sent a single packet to this host on any port I forward.

So: agent up, port open and proven reachable from the public internet, and nothing to receive. Please check whether your server-agent poller is actually operational for my account, and tell me which source IP(s) the agent poller uses so I can allowlist them precisely (I keep the forward source-restricted rather than exposing the port to the whole internet — your docs only list 162.55.41.109 / 2a01:4f8:c012:9c4a::1, and the poller evidently isn’t among them).

Related product issues found while diagnosing:

5. Your installer fails silently on its own download. The dashboard-provided bash installer fetches https://uptimemonster.com/downloads/server-agent/umon-1.0.0.u1804_amd64.deb with wget, but your CDN rejects wget’s default user-agent, the script discards the error (>/dev/null 2>&1), and then prints “Installation Completed” with no agent installed. I only got a working install by downloading the .deb manually with a browser user-agent. Anyone less persistent stops here.
6. The OS options are obsolete. The installer offers only CentOS and Ubuntu 22.x — CentOS 7 reached end-of-life in June 2024 (your .deb is literally an EL7 build, 1.0.0-1.el7, with 2023-dated libraries, packaged under an Ubuntu 18.04 filename — 18.04 is also EOL). There’s no supported path for current distributions (Debian 12/13, Ubuntu 24.04, RHEL 9 family). It runs on Debian 13 only because the script happens not to check.
7. The WordPress plugin is a release candidate. The only available build of UptimeMonster Site Monitor is 1.0.0-rc.1 (installs as 1.0.0, no update channel). Shipping an RC as the production plugin, years on, needs either a stable release or a note on its status.
8. Minor: the installer adds the agent’s service user to the sudo group, which is unnecessary for its operation and undesirable from a hardening standpoint.

Happy to re-open the firewall for a supervised test as soon as you can confirm the poller is firing and from which addresses.

Thanks,
Damien