Closed NK0D1NG closed 6 months ago
The Nextcloud Talk settings are all correct and working:
I notice there is no shared secret configured here. Was this removed for the screenshot or is it really empty? There should be something configured here and match the backend configuration in the signaling server.
@NK0D1NG , were you able to resolve this? I face same issue, only with NC 27. I have NC 25 instance pointed to same signaling server that works. Both 25 and 27 are behind identical haproxy configurations. Provisioned three signaling servers in different networks to test, NC 25 works on all, NC 27 works on none
Closing due to the lack of feedback, feel free to reopen if you have more information.
I set up the high performance backend including nextcloud-spreed according to this article: https://www.dogado.de/vps/vserver-anwendungsfaelle/nextcloud-talk-auf-vserver-installieren
Everything seems to work just fine. These are my docker logs:
The Nextcloud Talk settings are all correct and working:
But if I join a conversation I can't chat or start a call (button disabled). Also get errors about problems with the signalling server. If I look into the browser dev tools I see this in the websocket connection request/response cycle:
So there is something wrong about the request coming from the nextcloud and spreed refuses to authenticate? But I just don't know why. I am logged in and I created the conversation by myself. It doesn't matter which conversation I try - I always get errors about the signaling server connection and always the same result in the browser dev console / network tab.
Can someone help me out what's going wrong or is this a bug? I did not find any authentication settings for nextcloud talk and I triple-checked the (shared) secrets. Also the connection seems to work just fine and Nextcloud gives positive feedback about the TURN/STUN and HPB Settings..