Friction

Pain point · Reliability & bugs · Blocks work

UI says no workers connected after upgrading to 2025.10.1/2

3 source threads · first seen 2025-09 · last seen 2025-11

Summary

After updating with the official compose file, the interface warns that no workers are connected and background tasks will not run, though worker logs keep flowing. Rolling back to 2025.10.0 fixes it.

Affects
Docker compose user
Workaround
Roll back to 2025.10.0

Evidence

Excerpts are copied word for word from the source; follow the link to read it in full.

“In versions 2025.10.1 and 2025.10.2, the worker is displayed as not connected”

“Getting an unhealthy container for the authentik worker”

“After the update, I get a message saying that no workers are connected”

Report this item