Nextcloud AIO changing settings for external signaling server after restart

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

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

The issue I am facing:

Whenever I restart Nextcloud AIO, the internal Signaling server and its secret are being added to the configuration. There is a warning “Defining multiple High-performance backends is deprecated and will no longer be supported …”. The bigger problem is, that the secret of the external signaling server is being overridden and a successful talk connection is not possible anymore. After deleting the internal signaling server and correcting the secret, everything works fine again until the next restart.

Steps to replicate it:

  1. configure an external signaling server
  2. restart Nextcloud AIO
2

Hi, you need to disable the talk container in the aio interface and use this setting to use a custom hpb in talk https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-keep-disabled-apps

1 Like
3

Unfortunately, this only results in a “Error: Cannot connect to server”. But the internal address is still returning and the shared secret ist still overwritten after a reboot.

When I delete the internal address and correct the shared secret, everything works fine until the next reboot.

Edit: I didn’t disable the Talk container in the AIO interface. I thought that Talk would be completely disabled, but that was not the case.

image
image897Ă—404 42.7 KB

4

Sorry, you were right. What I have not done was disabling the talk container in the AIO interface. That was it!

Thank you so much!

1 Like