Talk not able to start (error talking to Server)

Hello John Here:

I am having a small problem here and hoping someone here can help me out of it. i have been running (AIO 24.0.8) with not problem’s other than TALK not working :roll_eyes:

I just installed (Auto-updated - Loved that part) to
( Nextcloud AIO v4.0.0 ) And Again All ie wirking very good
thanks to whomever came up with the MASTER Docker doing all the work of updating.

But guest what TALK still does not work…Anyone help me to get the TALK app working… here is the Error Log i keep ggetting
i know it is aomething i done wrong if more info need just ask…

Computer 16gb / 2 16GB drives / dell desktop

here is the Talk Boot then Error:

+ sed -i 's|#turn_rest_api_key.*|turn_rest_api_key = "112b7d2ff8afdadb17386e659fa25b1860907d9d841a3317"|' /etc/janus/janus.jcfg
+ sed -i 's|#full_trickle.*|full_trickle = true|g' /etc/janus/janus.jcfg
+ sed -i 's|#stun_server.*|stun_server = "127.0.0.1"|g' /etc/janus/janus.jcfg
+ sed -i 's|#stun_port.*|stun_port = 3478|g' /etc/janus/janus.jcfg
+ sed -i 's|#turn_port.*|turn_port = 3478|g' /etc/janus/janus.jcfg
+ sed -i 's|#turn_server.*|turn_server = "127.0.0.1"|g' /etc/janus/janus.jcfg
+ sed -i 's|#turn_type .*|turn_type = "udp"|g' /etc/janus/janus.jcfg
+ sed -i 's|#ice_ignore_list .*|ice_ignore_list = "udp"|g' /etc/janus/janus.jcfg
+ sed -i 's|#interface.*|interface = "lo"|g' /etc/janus/janus.transport.websockets.jcfg
+ sed -i 's|#ws_interface.*|ws_interface = "lo"|g' /etc/janus/janus.transport.websockets.jcfg
+ sed -i 's|certfile =|#certfile =|g' /etc/janus/janus.transport.mqtt.jcfg
+ sed -i 's|keyfile =|#keyfile =|g' /etc/janus/janus.transport.mqtt.jcfg
+ set +x
[26] 2022/12/20 10:02:05.264024 [INF] Starting nats-server
[26] 2022/12/20 10:02:05.264083 [INF]   Version:  2.9.9
[26] 2022/12/20 10:02:05.264086 [INF]   Git:      [825949b]
[26] 2022/12/20 10:02:05.264090 [INF]   Name:     NAAFJWE7S323FH6P6YS46F36KNUHPDRH7Z3VUSULW2NMW3V23MZR7T3I
[26] 2022/12/20 10:02:05.264094 [INF]   ID:       NAAFJWE7S323FH6P6YS46F36KNUHPDRH7Z3VUSULW2NMW3V23MZR7T3I
[26] 2022/12/20 10:02:05.264099 [INF] Using configuration file: /etc/nats/nats.conf
[26] 2022/12/20 10:02:05.264769 [INF] Listening for client connections on 127.0.0.1:4222
[26] 2022/12/20 10:02:05.264783 [INF] Server is ready
Janus version: 1101 (1.1.1)
Janus commit: not-a-git-repo
Compiled on:  Thu Dec  8 10:08:48 UTC 2022

Logger plugins folder: /usr/lib/x86_64-linux-gnu/janus/loggers
Loading logger plugin 'libjanus_jsonlog.so'...
[WARN] JSON logger disabled
Adding 1 external loggers
---------------------------------------------------
  Starting Meetecho Janus (WebRTC Server) v1.1.1
---------------------------------------------------

Checking command line arguments...
Debug/log level is 4
Debug/log timestamps are disabled
Debug/log colors are disabled
Adding 'vmnet' to the ICE ignore list...
Using 172.17.0.5 as local IP...
Token based authentication disabled
Initializing recorder code
Initializing ICE stuff (Full mode, ICE-TCP candidates disabled, full-trickle, IPv6 support disabled)
STUN server to use: 127.0.0.1:3478
  >> 127.0.0.1:3478 (IPv4)
Testing STUN server: message is of 20 bytes
main.go:133: Starting up version 33dc5a554b496bd253bedbecc6755de514a64867/go1.19 as pid 27
main.go:142: Using a maximum of 8 CPUs
natsclient.go:108: Connection established to nats://127.0.0.1:4222 (NAAFJWE7S323FH6P6YS46F36KNUHPDRH7Z3VUSULW2NMW3V23MZR7T3I)
grpc_common.go:167: WARNING: No GRPC server certificate and/or key configured, running unencrypted
grpc_common.go:169: WARNING: No GRPC CA configured, expecting unencrypted connections
backend_storage_static.go:72: Backend backend-1 added for https://n3ovo.org/
hub.go:201: Using a maximum of 8 concurrent backend connections per host
hub.go:208: Using a timeout of 10s for backend connections
hub.go:304: Not using GeoIP database
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 1s
0: log file opened: /var/tmp/turn_28_2022-12-20.log
0: 0 bytes per second allowed, combined server capacity
0: Config file found: //etc/turnserver.conf
0: 
RFC 3489/5389/5766/5780/6062/6156 STUN/TURN Server
Version Coturn-4.5.1.1 'dan Eider'
0: 
Max number of open files/sockets allowed for this process: 1073741816
0: 
Due to the open files/sockets limitation,
max supported number of TURN Sessions possible is: 536870500 (approximately)
0: 

==== Show him the instruments, Practical Frost: ====

0: TLS supported
0: DTLS supported
0: DTLS 1.2 supported
0: TURN/STUN ALPN supported
0: Third-party authorization (oAuth) supported
0: GCM (AEAD) supported
0: OpenSSL compile-time version: OpenSSL 1.1.1f  31 Mar 2020 (0x1010106f)
0: 
0: SQLite supported, default database location is /var/lib/turn/turndb
0: Redis supported
0: PostgreSQL supported
0: MySQL supported
0: MongoDB is not supported
0: 
0: Default Net Engine version: 3 (UDP thread per CPU core)

=====================================================

0: Domain name: 
0: Default realm: n3ovo.org
0: 
CONFIGURATION ALERT: You specified --lt-cred-mech and --use-auth-secret in the same time.
Be aware that you could not mix the username/password and the shared secret based auth methohds. 
Shared secret overrides username/password based auth method. Check your configuration!
0: ERROR: 
CONFIG ERROR: Empty cli-password, and so telnet cli interface is disabled! Please set a non empty cli-password!
0: WARNING: cannot find certificate file: turn_server_cert.pem (1)
0: WARNING: cannot start TLS and DTLS listeners because certificate file is not set properly
0: WARNING: cannot find private key file: turn_server_pkey.pem (1)
0: WARNING: cannot start TLS and DTLS listeners because private key file is not set properly
0: NO EXPLICIT LISTENER ADDRESS(ES) ARE CONFIGURED
0: ===========Discovering listener addresses: =========
0: Listener address to use: 127.0.0.1
0: Listener address to use: 172.17.0.5
0: Listener address to use: 172.18.0.5
0: =====================================================
0: Total: 2 'real' addresses discovered
0: =====================================================
0: NO EXPLICIT RELAY ADDRESS(ES) ARE CONFIGURED
0: ===========Discovering relay addresses: =============
0: Relay address to use: 172.17.0.5
0: Relay address to use: 172.18.0.5
0: =====================================================
0: Total: 2 relay addresses discovered
0: =====================================================
0: pid file created: /var/tmp/turnserver.pid
0: IO method (main listener thread): epoll (with changelist)
0: Wait for relay ports initialization...
0:   relay 172.17.0.5 initialization...
0:   relay 172.17.0.5 initialization done
0:   relay 172.18.0.5 initialization...
0:   relay 172.18.0.5 initialization done
0: Relay ports initialization done
0: IO method (general relay thread): epoll (with changelist)
0: IO method (general relay thread): epoll (with changelist)
0: IO method (general relay thread): epoll (with changelist)
0: turn server id=1 created
0: IO method (general relay thread): epoll (with changelist)
0: turn server id=0 created
0: turn server id=2 created
0: IO method (general relay thread): epoll (with changelist)
0: IO method (general relay thread): epoll (with changelist)
0: turn server id=3 created
0: turn server id=4 created
0: IO method (general relay thread): epoll (with changelist)
0: turn server id=5 created
0: turn server id=6 created
0: IO method (general relay thread): epoll (with changelist)
0: turn server id=7 created
0: Total General servers: 8
0: IO method (auth thread): epoll (with changelist)
0: IO method (auth thread): epoll (with changelist)
0: IO method (auth thread): epoll (with changelist)
0: IO method (auth thread): epoll (with changelist)
0: ERROR: Cannot open SQLite DB connection: </var/lib/turn/turndb>, runtime error:
  unable to open database file
  (If your intention is to use an SQLite database for the TURN server, then
  check and fix, if necessary, the effective permissions of the TURN server
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 2s
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 4s
  process and of the DB directory and then re-sta[FATAL] [ice.c:janus_ice_test_stun_server:1095] No response to our STUN BINDING test
[FATAL] [janus.c:main:5108] Invalid STUN address 127.0.0.1:3478
Janus version: 1101 (1.1.1)
Janus commit: not-a-git-repo
Compiled on:  Thu Dec  8 10:08:48 UTC 2022

Logger plugins folder: /usr/lib/x86_64-linux-gnu/janus/loggers
Loading logger plugin 'libjanus_jsonlog.so'...
[WARN] JSON logger disabled
Adding 1 external loggers
---------------------------------------------------
  Starting Meetecho Janus (WebRTC Server) v1.1.1
---------------------------------------------------

Checking command line arguments...
Debug/log level is 4
Debug/log timestamps are disabled
Debug/log colors are disabled
Adding 'vmnet' to the ICE ignore list...
Using 172.17.0.5 as local IP...
Token based authentication disabled
Initializing recorder code
Initializing ICE stuff (Full mode, ICE-TCP candidates disabled, full-trickle, IPv6 support disabled)
STUN server to use: 127.0.0.1:3478
  >> 127.0.0.1:3478 (IPv4)
Testing STUN server: message is of 20 bytes
  >> Our public address is 127.0.0.1
TURN server to use: 127.0.0.1:3478 (udp)
TURN REST API backend: (disabled)
Crypto: OpenSSL >= 1.1.0
No cert/key specified, autogenerating some...
Fingerprint of our certificate: C0:F6:05:24:4D:31:FA:7A:93:9A:C0:E2:91:0B:DC:C1:06:74:EE:F4:D7:23:0C:E1:2B:CA:0E:A1:5F:A3:99:BA
Event handlers support disabled
Plugins folder: /usr/lib/x86_64-linux-gnu/janus/plugins
Sessions watchdog started
Joining Janus requests handler thread
Loading plugin 'libjanus_audiobridge.so'...
JANUS AudioBridge plugin initialized!
Loading plugin 'libjanus_duktape.so'...
[e[36mechotest.jse[0m]  Loading script...
[e[36mechotest.jse[0m]  Modules folder: /usr/share/janus/duktape
[e[36mechotest.jse[0m]  Loading module: janus-sdp
[e[36mechotest.jse[0m]  Module loaded
[e[36mechotest.jse[0m]  Script loaded
[e[36mechotest.jse[0m]  Initializing...
[e[36mechotest.jse[0m]  Initialized
Janus JavaScript plugin (Duktape) initialized!
Loading plugin 'libjanus_echotest.so'...
JANUS EchoTest plugin initialized!
Loading plugin 'libjanus_lua.so'...
e[0m[e[34mechotest.luae[0m]e[0m Loading...
e[0m[e[34mechotest.luae[0m]e[0m Loaded
e[0m[e[34mechotest.luae[0m]e[0m Initializing...
e[0m[e[34mechotest.luae[0m]e[0m Initialized
Janus Lua plugin initialized!
Loading plugin 'libjanus_nosip.so'...
JANUS NoSIP plugin initialized!
Loading plugin 'libjanus_recordplay.so'...
JANUS Record&Play plugin initialized!
Loading plugin 'libjanus_sip.so'...
JANUS SIP plugin initialized!
Loading plugin 'libjanus_streaming.so'...
[ERR] [plugins/janus_streaming.c:janus_streaming_init:2492] Can't add 'live' mountpoint, no such file '/usr/share/janus/streams/radio.alaw'...
[ERR] [plugins/janus_streaming.c:janus_streaming_init:2566] Can't add 'ondemand' mountpoint, no such file '/usr/share/janus/streams/music.mulaw'...
JANUS Streaming plugin initialized!
Loading plugin 'libjanus_textroom.so'...
JANUS TextRoom plugin initialized!
Loading plugin 'libjanus_videocall.so'...
JANUS VideoCall plugin initialized!
Loading plugin 'libjanus_videoroom.so'...
JANUS VideoRoom plugin initialized!
Loading plugin 'libjanus_voicemail.so'...
JANUS VoiceMail plugin initialized!
Transport plugins folder: /usr/lib/x86_64-linux-gnu/janus/transports
Loading transport plugin 'libjanus_http.so'...
HTTP transport timer started
HTTP webserver started (port 8088, /janus path listener)...
JANUS REST (HTTP/HTTPS) transport plugin initialized!
Loading transport plugin 'libjanus_mqtt.so'...
MQTT SSL support disabled
[WARN] MQTT support disabled for both Janus and Admin API, giving up
JANUS MQTT transport plugin destroyed!
[WARN] The 'janus.transport.mqtt' plugin could not be initialized
Loading transport plugin 'libjanus_nanomsg.so'...
JANUS Nanomsg transport plugin initialized!
Loading transport plugin 'libjanus_pfunix.so'...
Nanomsg thread started
[WARN] No Unix Sockets server started, giving up...
[WARN] The 'janus.transport.pfunix' plugin could not be initialized
Loading transport plugin 'libjanus_rabbitmq.so'...
RabbitMQ SSL support disabled
[WARN] RabbitMQ support disabled for both Janus and Admin API, giving up
[WARN] The 'janus.transport.rabbitmq' plugin could not be initialized
Loading transport plugin 'libjanus_websockets.so'...
libwebsockets logging: 0
[ERR] [transports/janus_websockets.c:janus_websockets_init:737] Error creating libwebsockets context...
[WARN] The 'janus.transport.websockets' plugin could not be initialized
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 8s
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 16s
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 16s
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 16s
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 16s
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 16s
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 16s
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 16s
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 16s

I cur out about  500 lines of 
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 16s

just keeps going and going
Thank you for such a wonderful system
John G

Hi this seems to be the issue that you have. The question is now why this happens.

More issues…

Hi, I just created this PR which should hopefully fix your issues in the future. I’ll let you know when it is available in the beta channel.

1 Like

THANK YOU very much … your help here is very appreciated. :upside_down_face:

Let me know if there is anything more you need from me… I though that the new 25 update would had fixed all my problems that i might of done … but no … all the other stuff is working with no problems, It is just TALK, that’s why i waited so long to ASK…

Look forward to what you find

John G.

The fix is now released with v4.0.1 Beta. Testing and feedback is welcome! See GitHub - nextcloud/all-in-one: Nextcloud AIO stands for Nextcloud All In One and provides easy deployment and maintenance with most features included in this one Nextcloud instance.

Hello and thanks for trying to fix very quickly, And
Merry Christmas

still seem to be a problem>

  1. after the update 4.0.1 i keep getting a hung system not sur why yet going to test by passing some data base checks later to day. Will let you know.

  2. talk still not working. i seem to be locking up now. Not sure why at this point. i have save out the main log and the talk log and i screen showing the error.

again thanks for the help … it Christmas no big hurry :thinking:
let me know what if anything i can send that you might need to see

thanks again and to you and yours Merry Christmas :christmas_island: :christmas_tree:

log_File_12-25-2022_Now_crashing_after_update_to_4.0.1_AIO.pdf (50.3 KB)
Talk_Error_logfile_After_4.0.1-just_rebooted.pdf (21.9 KB)

i was playing some more and turned off

Matterbridge integration Beta
Installed version: version: 1.25.2 20f841c5

and got a diff message ( though it might help )
new_error message_after_off_ Matterbridge_integration_Screenshot_20221225_053451

thanks again

more info … web server might need looked at and turn server says it’s ok :thinking:


Hm… no idea sorry, I would need the complete error message for the "driver failed programming external connectivity on endpoint nextcloudaio-talk issue in order to be able to debug the issue.

This seems to be the issue now: [ERR] [transports/janus_websockets.c:janus_websockets_init:737] Error creating libwebsockets context.... Unfortunately I don’t have a clue what could cause this. And there is no further log entry which could point to a possible solution.

This is likely due to the talk container not starting correctly.

This is an issue of the talk app. Feel free to report it to Issues · nextcloud/spreed · GitHub if there is not an open issue about this already.

Ok I have never done that before. I will give it a try. Then the Last question i would have it there a problem with what version of linux you/everyone use’s … I am on fedora 36 to move to 37 soon … what would be the BEST OS/Version. if i am the only one have this problem could it be the OS? :upside_down_face:

thanks John

I would usually recommend Ubuntu 22.04 LTS :slight_smile:

Hi, I googled a bit and is it possible that ulimit for the docker service on systemd is set to infinity? Can you try to change this to a limited but still high value? This may resolve you issue with Janus.

I found this: libwebsockets issue with unlimitied file descriptors · Issue #22 · canyanio/janus-gateway-docker · GitHub

This happens if the ulimit is set to infinity on systemd for the docker service (or cgroups/whatever you are using) and because of how the code is written here.

Hi, I just released another fix with v4.1.0 Beta. Testing and feedback is welcome! See GitHub - nextcloud/all-in-one: Nextcloud AIO stands for Nextcloud All In One and provides easy deployment and maintenance with most features included in this one Nextcloud instance.

thanks i will look that up and see … thanks for searching for me.
I do have Another Problem :melting_face:

what do you think of this … Keep getting this looks like a Google address that keeps trying to login. any thoughts.

The login of user “john” with IP address “64.9.251.151” could not be checked due to problems with location service