Proposal: Multi-Node / Cluster Management for Nginx Proxy Manager

[KailertB]

Overview

I would like to propose an optional Multi-Node / Cluster Management feature for Nginx Proxy Manager.

The goal is to make it possible to manage multiple Nginx Proxy Manager instances as a cluster, without requiring a separate permanent "Central Manager".

Every NPM instance could act as a management entry point for the cluster.

For example:

NPM-01
NPM-02
NPM-03
NPM-04

If I log in to NPM-02, I should be able to view and manage the other nodes (NPM-01, NPM-03, NPM-04) from the same interface.

If NPM-02 goes offline, I could simply log in to NPM-01 or NPM-03 and continue managing the cluster.

Important: Proxy Hosts Remain Node-Local

I am NOT proposing that all Proxy Hosts should be replicated across every node.

Each NPM instance should continue to have its own independent Proxy Hosts and Nginx configuration.

For example:

NPM-01

• app01.example.com
• api01.example.com

NPM-02

• app02.example.com
• api02.example.com

NPM-03

• app03.example.com

A Proxy Host created on NPM-02 would remain on NPM-02 only.

The cluster functionality would mainly be for management, node discovery, health/status, administration, and other cluster-level operations.

Example

A user logs into:

https://npm-02.example.com

They could see:

Cluster Nodes

• NPM-01 — Online
• NPM-02 — Online
• NPM-03 — Online
• NPM-04 — Offline

From NPM-02, the administrator could manage or access the other nodes.

Likewise, logging into NPM-03 should provide the same cluster management capabilities.

There should be no permanent master node.

Concept

                NPM Cluster

   ┌───────────────────────────┐
   │   Cluster Management      │
   │   Nodes / Health / Status │
   └─────────────┬─────────────┘
                 │
      ┌──────────┼──────────┐
      ▼          ▼          ▼
   NPM-01      NPM-02      NPM-03
      │          │          │
   Proxy A    Proxy C    Proxy E
   Proxy B    Proxy D    Proxy F

Each node remains an independent Nginx Proxy Manager and continues to handle its own traffic.

Why This Could Be Useful

This could be useful for environments running multiple NPM instances across:

• Multiple servers
• Multiple sites
• Different network segments
• Home labs
• Development / staging / production environments
• Distributed infrastructure

It would also avoid creating a single management point that becomes a single point of failure.

Possible Future Features

The cluster management layer could potentially provide:

• Node discovery
• Node health monitoring
• Node status
• Version compatibility checking
• Cluster membership
• Centralized administration
• Audit/event history
• Optional configuration synchronization for cluster-level settings

Proxy Host configuration would remain node-local unless explicitly configured otherwise.

I would be interested to hear whether this type of Multi-Node / Cluster Management would fit the project's roadmap or architecture.