Context:
I have a Nextcloud (30.0.5) instance running in Kubernetes, and I’ve deployed an
externally dockerized Talk Backend consisting of:
- Coturn 4.6.2
- Spreed Backend
- NATS 2.2.1
- Janus
Backend Configuration: - The Spreed backend is configured to use the Nextcloud URL with a
generated secret. - The secret in the Nextcloud UI matches exactly with the one in the
Spreed backend configuration. Secrets are not the issue.
Network & DNS Setup: - Public DNS:
- turn.domain.com resolves to the company’s public IP. Port 3478 is
directly forwarded to the Coturn container. - signal.domain.com resolves to the public IP, but traffic goes
through an Nginx proxy, which forwards it to the Spreed container on
port 8085. - Internal DNS:
- turn.domain.com resolves directly to the Coturn container.
- signal.domain.com still goes through the proxy before reaching
Spreed.
There are currently no firewall rules in place.
Issue:
Whenever I try to create a chatroom in Nextcloud Talk, I receive the
error:
Failed attempt on ‘BackendRoomAuth’ from , throttling by
100ms.
What I’ve Ruled Out:
- Secrets are correct (verified multiple times), even tried allow all
backends. - DNS resolution is working (both internal and external).
- Port forwarding appears correct (TURN and Spreed backend are
accessible).
Question:
What could be causing the ‘BackendRoomAuth’ failed attempt error in
this setup?