Nextcloud Talk High Performance Backend -Call not available

Hi all. I used this guide How to Install Nextcloud Talk High Performance Backend with Stun/Turnserver on Ubuntu – Markus' Blog to set up.
My system. Nexcloud server behind NAT. Server signaling external IP address.
The systems on both servers are Ubuntu 20.04.4 LTS.
The signaling server is registered in the Nexcloud settings, the check is passing, there is a response from standalone-signaling/api/v1/welcome.
When creating chats in talk, an error pops up “Failed to join the conversation. Try to reload the page.”
Also, the call button is not active. In the output of the systemctl status signaling command, I see
Jun 27 13:48:16 hbs signaling[8528]: hub.go:822: Invalid message {Marshaler: Unmarshaler: Id: Type: Hello: Bye: Room: Message: Control: Internal: TransientDat>
Jun 27 13:48:19 hbs signaling[8528]: client.go:303: Error reading from 176.59.15.184: read tcp 127.0.0.1:8080->127.0.0.1:39734: use of closed network connection
Jun 27 13:48:20 hbs signaling[8528]: client.go:282: Client from 176.59.15.184 has RTT of 48 ms (48.501612ms)
Jun 27 13:48:20 hbs signaling[8528]: hub.go:822: Invalid message {Marshaler: Unmarshaler: Id: Type: Hello: Bye: Room: Message: Control: Internal: TransientDat>
Jun 27 13:48:23 hbs signaling[8528]: client.go:303: Error reading from 176.59.15.184: read tcp 127.0.0.1:8080->127.0.0.1:39736: use of closed network connection
Jun 27 13:48:24 hbs signaling[8528]: client.go:282: Client from 176.59.15.184 has RTT of 45 ms (45.339979ms)
Jun 27 13:48:24 hbs signaling[8528]: hub.go:822: Invalid message {Marshaler: Unmarshaler: Id: Type: Hello: Bye: Room: Message: Control: Internal: TransientDat>
Jun 27 13:48:27 hbs signaling[8528]: client.go:303: Error reading from 176.59.15.184: read tcp 127.0.0.1:8080->127.0.0.1:39738: use of closed network connection
Jun 27 13:48:29 hbs signaling[8528]: client.go:282: Client from 176.59.15.184 has RTT of 159 ms (159.249484ms)
Jun 27 13:48:29 hbs signaling[8528]: hub.go:822: Invalid message {Marshaler: Unmarshaler: Id: Type: Hello: Bye: Room: Message: Control: Internal: TransientDat>
lines 1-19/19 (END)

I’m at a loss. What to do?

Hey @NoS

please add some details to your problem description: Nextcloud version, Talk version, HPB version, Go version etc.

Other than that, please try to rebuild the signaling server (use make clean before doing so).

Also see Version 0.5.0 does not work as update from 0.4.1 (Periodic errors: "use of closed network connection") · Issue #271 · strukturag/nextcloud-spreed-signaling · GitHub

Hey.
Версия nextcloud 24.0.2, Go 1.1.7, Talk 14.0.2
Я удалил signaling и установил по новой версию 0.5.0 и так же пробовал версию 0.4.1. Теперь я получаю следующую ошибку:
backend_client.go:355: Could not send request {“type”:“auth”,“auth”:{“version”:“1.0”,“params”:{“userid”:"",“ticket”:“vZLiCz7ydu9+K1kg:1656364815:sbadmin:df06ee1db0a044e300be6517f451d30251a628bd86ff3ad2ef7b0f3a501882a2”}}} to https://nexttest../ocs/v2.php/apps/spreed/api/v3/signaling/backend: Post “https://nexttest.****.**/ocs/v2.php/apps/spreed/api/v3/signaling/backend”: dial tcp 178.170.230.121:443: connect: no route to host

178.170.230.121:443 - my nextcloud server

Вот мой конфиг signaling
[http]
listen = 127.0.0.1:8080
[app]
debug = false

[sessions]
hashkey = 0ebb979d49ca26eeb87d167b0f1c7f1e
blockkey = 4ed0e71d3ffcd3143f2cfe68f70509cf

[backend]
backends = backend-1 #here you can add more backends commaseparated backend-1, backend-2, backend-3
allowall = false
timeout = 10
connectionsperhost = 8

[backend-1]
url = https://nexttest.****.**
secret = 892a2b8b5979bb1628b32858678f4a28

#[backend-2]
#url = https://nextcloud2.example.com
#secret = openssl rand -hex 16

#[backend-3]
#url = https://nextcloud3.example.com
#secret = openssl rand -hex 16

[nats]
url = nats://localhost:4222

[mcu]
type = janus
url = ws://127.0.0.1:8188

[turn]
apikey = zIiR3bPElNnzROuorF0aIw==
secret = 6ed2db2d36ed6d5569d92537a6577c00e80301f69d065d8d542ba9e8eb68f1b0
servers = turn:signaling..**:5349?transport=udp,turn:signaling..**:5349?transport=tcp