Zombie room keeps coming back

ℹ️ Support 💬 Talk (spreed)
, , ,
1
Support intro

Sorry to hear you’re facing problems :slightly_frowning_face:

help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:

example

Or for longer, use three backticks above and below the code snippet:

longer
example
here

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can :heart:

Some useful links to gather information about your Nextcloud Talk installation:
Information about Signaling server: /index.php/index.php/settings/admin/talk#signaling_server
Information about TURN server: /index.php/settings/admin/talk#turn_server
Information about STUN server: /index.php/settings/admin/talk#stun_server

Nextcloud version (eg, 24.0.1): 32.0.2
Talk Server version (eg, 14.0.2): 22.0.4
Custom Signaling server configured: yes
Custom TURN server configured: yes
Custom STUN server configured: yes

Trouble is, I created a room as nextcloud user, which comes back every day at 3 a.m. since weeks

Unfortunately as admin I had inserted a wrong secret, I don’t know whether a wrong turn-server secret or a wrong HPB-Backend secret. Only one of the secrets was wrong. No surprise, no video conference was possible, the participants were able to “see” the room, but no video and no sound. I deleted the room as user, changed to the admin user and corrected the wrong secret.

Since then the log is spammed with errors, every five or ten minutes from 3 am to 7:50 am every morning:

ClientException Client error: `POST https://turn.xxxx.de/standalone-signaling/api/v1/room/eizxmt7m` resulted in a `403 Forbidden` response: Authentication check failed

[core] Fehler: Error while running background job OCA\Talk\BackgroundJob\RemoveEmptyRooms (id: 29139, arguments: null)
	von ? von -- um 28.11.2025, 07:50:27

Of course, I tried to delete the rooms (the ID, here eizxmt7m, changes after every deletion) :

pi@nextcloudpi:~ $ sudo -u www-data php /var/www/nextcloud/occ talk:room:delete eizxmt7m
In RequestException.php line 111:
  Client error: `POST https://turn.xxx.de/standalone-signaling/api/v1/room/eizxmt7m` resulted in a `403 Forbidden` response:  
  Authentication check failed                                                            
talk:room:delete <token>

I made the admin member of the room, promoted him to manager (talk:room:promote)
and deleted the room from the talk app, to no avail. After deleting the room comes back under a different ID, but with the same name.

Is this the first time you’ve seen this error? Yes, but it goes on since weeks.

Steps to replicate it:

  1. Have your own signaling and turn server, but insert a wrong secret on the web interface of nextcloud.

  2. Open a new room, find out that it doesn’t work, delete it.

  3. Correct the secret.

The output of your Nextcloud log in Admin > Logging or errors in nextcloud.log in /var/www/:

The output of your Apache/nginx/system log in /var/log/____:

ClientException Client error: `POST https://turn.xxxx.de/standalone-signaling/api/v1/room/eizxmt7m` resulted in a `403 Forbidden` response: Authentication check failed
28.11.2025, 03:40:08
	
Fehler
	spreed
	
ClientException Client error: `POST https://turn.xxxx.de/standalone-signaling/api/v1/room/eizxmt7m` resulted in a `403 Forbidden` response: Authentication check failed
28.11.2025, 03:40:08
	
Fehler
	core
	
ClientException Client error: `POST https://turn.xxxx.de/standalone-signaling/api/v1/room/eizxmt7m` resulted in a `403 Forbidden` response: Authentication check failed
28.11.2025, 03:30:05
	
Fehler
	spreed
	
ClientException Client error: `POST https://turn.xxxx.de/standalone-signaling/api/v1/room/eizxmt7m` resulted in a `403 Forbidden` response: Authentication check failed
28.11.2025, 03:30:05
	
Fehler
	core
	
ClientException Client error: `POST https://turn.xxxx.de/standalone-signaling/api/v1/room/eizxmt7m` resulted in a `403 Forbidden` response: Authentication check failed
28.11.2025, 03:20:03
	
Fehler
	spreed
	
ClientException Client error: `POST https://turn.xxxx.de/standalone-signaling/api/v1/room/eizxmt7m` resulted in a `403 Forbidden` response: Authentication check failed
28.11.2025, 03:20:03
	
Fehler
	core
	
ClientException Client error: `POST https://turn.xxxx.de/standalone-signaling/api/v1/room/eizxmt7m` resulted in a `403 Forbidden` response: Authentication check failed
28.11.2025, 03:10:02
	
Fehler
	spreed
	
ClientException Client error: `POST https://turn.xxxx.de/standalone-signaling/api/v1/room/eizxmt7m` resulted in a `403 Forbidden` response: Authentication check failed
28.11.2025, 03:10:02
	
Warnung
	updatenotification
	
Cleared old `updater.secret` that was created 1764295210 seconds ago
28.11.2025, 03:00:10
	
Fehler
	core
	
ClientException Client error: `POST https://turn.xxxx.de/standalone-signaling/api/v1/room/eizxmt7m` resulted in a `403 Forbidden` response: Authentication check failed
28.11.2025, 03:00:02
	
Fehler
	spreed
	
ClientException Client error: `POST https://turn.xxxx.de/standalone-signaling/api/v1/room/eizxmt7m` resulted in a `403 Forbidden` response: Authentication check failed
28.11.2025, 03:00:02
	
Warnung
	updatenotification
	
Cleared old `updater.secret` that was created 1764291601 seconds ago

Any ideas how to get rid of hundreds of error messages?

2

»Most likely this is because your overwrite.cli.url is wrong and not reachable by the HPB correctly«

And probably true, Instead of the real address there was something like “http://nextcloudpi”

After a correction I was able to delete the room.