← Directory

Failover Guard

Failover Guard is an Unraid plugin that monitors a remote origin server, switches your domain's DNS to a replica on your NAS when the origin stops responding,…

  • Automation
  • Monitoring & Logging
  • Network Services
  • Plugins
  • Tools & Utilities
Failover Guard is an Unraid plugin that monitors a remote origin server, switches your domain's DNS to a replica on your NAS when the origin stops responding, notifies you of the switch and failback, and restores the original setup when the origin recovers.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score

Not enough data yet for a health score. It needs at least 2 of 4 factors: maintenance, popularity, ease of install, resource needs.

Availability: platform listings confirmed today

GitHub stars
0
Open issues
1
Last commit
2026-09-15
Latest release
v2026.09.15.1
Activity
stale

Checked today - source: GitHub (Nebur692/failover-guard-unraid-plugin)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install the required packages first Run sudo apt-get install pg-auto-failover-cli and sudo apt-get install postgresql-17-auto-failover so the command-line tool and PostgreSQL extension are available. Without them, pg_autoctl commands and automatic failover won’t work. source
  • Fill in node settings and protect data Set [node] hostname/port, [postgresql] pgdata (where the database files live), and [monitor] pguri (the address used to contact the failover monitor), and make sure the Postgres port (5432 in the examples) is reachable from other nodes. Keep pg_autoctl_node.ini and the pgdata folder safe; wrong settings or a lost data folder can stop the node from joining or lose data. source
  • Start the cluster with Docker Compose Run docker compose up app monitor node1 node2, which starts the application, monitor, and database node services together. If you skip this, the failover services stay stopped and nothing can monitor or fail over. source
  • Configure origin and proxy settings Install the Unraid plugin, then configure the remote origin, Cloudflare DNS, and Nginx Proxy Manager host before enabling failover. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Should ORIGIN_HOST be my public domain if it is behind a CDN?

No. Use the real host name of the remote server, because a domain behind a CDN can answer even when the origin is dead.

Can an open TCP port be enough to declare the origin healthy?

Not if a health path is configured. The plugin does not accept an open TCP port as proof of health when a health path is set, because a machine can boot with its web server dead.

Does Failover Guard talk to Nginx Proxy Manager through its API?

No. It enables and disables the matching NPM host the same way NPM does internally, so no API credentials are needed and the GUI stays consistent.

Does the plugin automatically back up or sync application data?

No, it never touches your data. You provide hook scripts for data movement because only you know what your data is.

What Cloudflare token permissions are required?

The token needs Zone:Read and DNS:Edit.

Answers sourced from github.com

Community

No community discussions collected yet.