Closed goNeuland closed 1 year ago
Potential causes:
coturn | 0: : WARNING: cannot find certificate file: turn_server_cert.pem (1)
coturn | 0: : WARNING: cannot start TLS and DTLS listeners because certificate file is not set properly
coturn | 0: : WARNING: cannot find private key file: turn_server_pkey.pem (1)
coturn | 0: : WARNING: cannot start TLS and DTLS listeners because private key file is not set properly
Some clients could publish successfully, for example this one:
janus | Creating new handle in session 3367089151431510: 8965206604290618; 0x7ff1cd8f0ed0 0x7ff1cc2ee670
spreed | mcu_janus.go:729: Attached video as publisher 8965206604290618 to plugin janus.plugin.videoroom in session 3367089151431510
spreed | mcu_janus.go:767: Created room 5565699418641624 {janus.plugin.videoroom map[permanent:false room:5565699418641624 videoroom:created]}
spreed | mcu_janus.go:825: Publisher MuigdFDlMzfUsM3uTBeU4EwJ_L5UflwIE4YJuL_b02d8TmZkUDd4YUkzM2dNQXlhMGFUTDNlM0JfU3RvdkdyVWdsSkNWSVpwMEZ1VnV3b25sclBKak92NVVkc3RmSEdRSi1kLUpOTFlxXzVQOUNBMjRTQ1RPd3hneEhmNXFCUk9CWGk2UHNpYmdHN2o0OUlkeV9uVVRQMEJoN05yVEFBUW1yamN1anV4OVduX0Juc0VVeEQwRy02US1Gbi1oWXdMRXBOMHNOb2ljdXg1b3wyNzQ1NjQ0NjYx is using handle 8965206604290618
spreed | clientsession.go:876: Publishing video as 2 for session MuigdFDlMzfUsM3uTBeU4EwJ_L5UflwIE4YJuL_b02d8TmZkUDd4YUkzM2dNQXlhMGFUTDNlM0JfU3RvdkdyVWdsSkNWSVpwMEZ1VnV3b25sclBKak92NVVkc3RmSEdRSi1kLUpOTFlxXzVQOUNBMjRTQ1RPd3hneEhmNXFCUk9CWGk2UHNpYmdHN2o0OUlkeV9uVVRQMEJoN05yVEFBUW1yamN1anV4OVduX0Juc0VVeEQwRy02US1Gbi1oWXdMRXBOMHNOb2ljdXg1b3wyNzQ1NjQ0NjYx
janus | [8965206604290618] Creating ICE agent (ICE Full mode, controlled)
janus | [8965206604290618] The DTLS handshake has been completed
janus | [janus.plugin.videoroom-0x7ff1cc2fb550] WebRTC media is now available
spreed | mcu_janus.go:864: Publisher 8965206604290618 received connected
janus | [janus.plugin.videoroom-0x7ff1cc2fb550] Data channel available
In any case this looks like a coturn configuration / clientside connection problem and is most likely not related to the signaling server.
Another thing: Janus is only running on a private address:
janus | [WARN] Janus is deployed on a private address (172.18.0.5) but you didn't specify any STUN server! Expect trouble if this is supposed to work over the internet and not just in a LAN...
The Janus server should be directly reachable by clients, i.e. either run on a public IP or behind a 1-1 firewall.
Closing as this seems to be a networking / firewall / configuration issue. Feel free to reopen with more details if you think this is a problem of the signaling server.
Enviroment One Server for NC and nextcloud spreed signaling for testing
Nextcloud GUI Everything looks good in the gui
Problem: Users cannot connect. I have already tried several browsers and devices.
Server Logs