RecoverNode v3.4 · Linux infrastructure resilience

Recovery that knows what failed before it acts.

RecoverNode watches the full path, from DNS and TLS through HTTP to your services, and works out which layer failed. It restarts a service only when local evidence shows that service is the problem. When the evidence points at DNS, the network or a provider, it alerts you instead of rebooting a healthy server.

Full-path visibilityCorrelated alertsGuarded recovery
RECOVERNODE STATUSPROTECTED
Observer nodeDNS path · delegation · authoritative/public DNS · TLS · HTTP · TCP
Healthy
Recovery guardsNginx · application · watchdog · Pi power health
Armed
DECISION POLICYAmbiguous evidence → alert, do not reboot
Built forMSPsWeb agenciesSmall hosting operatorsSelf-hosted Linux teams

New in RecoverNode v3.4

Planned changes shouldn't page you. Real outages should always reach you.

RecoverNode v3.4 lets you change DNS on purpose without a flood of false alarms, keeps alerts flowing through an independent emergency mail path when your own email is down, and serves the control panel over HTTPS only.

01

Change DNS without an alert storm

Open a DNS maintenance window for every property, or mute DNS alerts for one property for 1, 4 or 24 hours. Both end on their own, and HTTP, TLS and TCP alerts stay on throughout.

02

Accept the new answer

After a deliberate move, review the new DNS answer in the Control Panel and accept it as the expected value instead of editing configuration by hand.

03

Alerts that still arrive

Enroll a code-verified emergency alert address on a separate mail provider, so an outage that takes down your own domain's email is still reported.

The outage gap

Monitoring the endpoint is not enough when the failure lives somewhere in the path.

RecoverNode combines endpoint checks with resolver-path, delegation, authoritative and public DNS, TLS, semantic HTTP identity, TCP, local service evidence, and network-state diagnostics. Related failures can be correlated into one infrastructure incident so operators see the likely cause instead of an alert storm.

01

See the full failure path

A separate observer checks DNS paths and TTLs, delegation, authoritative and public resolvers, TLS, HTTP identity and latency, TCP services, and private infrastructure.

02

Correlate before escalating

Related multi-property DNS or network symptoms can be consolidated into one infrastructure incident while preserving each property's underlying failure evidence.

03

Recover only when justified

Nginx and application failures are classified separately, while backoff, action budgets, cooldowns, persistent state, and lockout prevent unsafe recovery loops.

Guarded automation

Designed around the failures automation usually gets wrong.

RecoverNode treats an unreachable server as evidence—not proof. Network paths, DNS, routing, and the observer itself can fail. Remote observations therefore do not directly authorize a reboot.

What guarded recovery means: RecoverNode first validates the failure on the protected host, identifies the unhealthy component, and performs only the specific recovery action allowed by its configured safeguards. If the evidence is ambiguous, it alerts instead of restarting or rebooting a system that may still be healthy.

Review the safety architecture →
✓False-positive resistanceMultiple local checks before disruptive recovery.
✓Service-specific recoveryNginx and upstream applications are evaluated independently.
✓DNS path and content integrityInternal-reference and client-facing resolver comparison, UDP/TCP answers, TTL risk, delegation, authoritative, public-recursive, expected-IP, and semantic content checks can expose stale caches, resolver divergence, DNS drift, or a wrong site served with a successful HTTP status.
✓Correlated infrastructure alertsMatching multi-site network or DNS failures can be consolidated into one infrastructure incident instead of creating an alert storm.
✓Hardware and power evidenceWatchdog recovery remains separate from supported Raspberry Pi power-condition reporting.
✓Auditable decisionsEvery failure, action, cooldown, and lockout is logged.

RecoverNode Admin Control Panel

Operate RecoverNode from one authenticated Admin Control Panel.

The RecoverNode Admin Control Panel is an authenticated LAN-only dashboard for day-to-day operation. Manage monitored properties, configure supported monitor families, inspect live-refreshing failure and recovery state, run diagnostics, control per-monitor alert policy, and rotate the administrator credential without exposing monitoring secrets in the browser.

01

Property control

Manage HTTP endpoints, TCP checks, DNS-path settings, and supported monitoring families from one local administrative surface.

02

Alert policy

Monitor state and alert delivery are controlled separately, and unconfigured monitor families cannot be enabled or presented as active alert policies.

03

Faster diagnosis

Active failures, recent recoveries, runtime state, and diagnostic evidence refresh together, while classification-aware guidance suggests the next operator action without authorizing automatic remediation.

What the deployment includes

Guided deployment for the environment you actually run.

The standard deployment includes the complete customer ZIP and walkthrough assistance. The installer discovers the environment, supports combined or separate Nginx and application hosts, creates the required configuration, installs the correct services, and validates the result without requiring manual configuration-file editing.

01

Discover

Read-only inventory detects Linux, services, ports, Nginx, applications, resolver configuration, effective Netplan state, configuration drift, watchdog support, Raspberry Pi capabilities, and likely topology.

02

Install

A guided walkthrough installs the observer, Nginx guard, application guard, combined-host components, and optional Raspberry Pi power-health monitoring where supported. Every installer question is explained in a plain-language guide, and mail logins are tested before they are saved.

03

Validate and reverse

Verification, status, rollback, uninstall, persistent-journal, and cold-start guidance are included in the same package.

Launch offer

Complete RecoverNode deployment

$249

$349 · $100 discount automatically applied at checkout. Ends December 24, 2026.

  • Independent observer plus one protected environment
  • Guarded Nginx and application-service recovery
  • DNS Path Integrity across internal-reference and client-facing resolvers, including TTL/cache-risk, UDP/TCP, delegation, authoritative, public-recursive, TLS, content-identity, and network-drift diagnostics
  • Recovery budgets, cooldowns, and lockout protection
  • Multi-site infrastructure incident correlation
  • RecoverNode Admin Control Panel with live status, diagnostics, per-monitor alert policy, and operator remediation guidance
  • Guided portable installation with verification, upgrade preservation, and rollback tools
  • Technical documentation and walkthrough assistance
  • 30 days of configuration support

Start with an environment review

Before activation, we review the environment, confirm the supported topology, identify the services being protected, and verify the recovery boundaries so the deployment matches the way your infrastructure actually operates.

Compare options

Reduce unattended downtime

Know what failed. Recover what is safe. Escalate what is not.

Request a free fit assessment