How do I configure SignalR when running multiple GreenStack replicas?
When you scale your GreenStack site beyond a single container, the Umbraco back office needs a shared SignalR backplane so editors connected to different replicas stay in sync.
When you need this
Section titled “When you need this”You need to configure a SignalR backplane only when your GreenStack service is running 2 or more replicas. A single-replica site works fine with the default in-process SignalR and does not need any of the configuration below.
If you’re not sure how many replicas you’re running, check your service in UmbPanel — the replica count is shown on your site’s overview.
How to configure it
Section titled “How to configure it”Follow the Using existing infrastructure approach from the Umbraco documentation:
SignalR in Backoffice Load Balanced Environment — Using existing infrastructure
That section walks through wiring the back office SignalR hub into your existing Umbraco SQL database — covering the required NuGet packages, the DI registration, and the configuration values.
Note: GreenStack already provides the database that this approach uses as the backplane, so no additional infrastructure needs provisioning — just apply the configuration to your project.