Problem configuring talk and turn

Hello there,
after many tries, (tcp only, stun only, etc…) I didn’t succeed making talk working with turn. I succeeded with a stand alone webrtc, out of nextcloud but never with spreed or talk app. I think my problem happens to other persons, I hope find a solution.

I read that the message 401 is not relevant because of the assumption to not use a user name and password, so I’m blocked now in my investigations.

Thanks for help !

Here are relevant informations :

Nextcloud version (eg, 12.0.2): 13.0.5
Operating system and version (eg, Ubuntu 17.04): ubuntu 16.04 up to date
Apache or nginx version (eg, Apache 2.4.25): nginx
PHP version (eg, 7.1): 7.0

the turn server and nextcloud/nginx are on the same virtual machine, hosted by Infomaniak. The public ip is not listed in the log, so I think there’s no problem of binding local ip with public ip. I’m using the domain name

the domain name of turn server has been replaced by “mydomain”, local ip of server by and clients ips by and

here is the configuration for talk app :

“spreed”: {
“types”: “prevent_group_restriction”,
“installed_version”: “3.2.5”,
“enabled”: “yes”,
“turn_servers”: “[{"server":"turn-nc.mydomain.eu:9443","secret":"","protocols":"udp,tcp"}]”,
“stun_servers”: “["turn-nc.mydomain.eu:5349"]”
},

here is the /etc//turnserver.conf

log-file=/mnt/vdb/log/turn/turn.log
simple-log
listening-port=5349
tls-listening-port=9443

fingerprint
lt-cred-mech

use-auth-secret
static-auth-secret=

realm=turn-nc.mydomain.eu
total-quota=100
bps-capacity=0
stale-nonce

cert=/etc/letsencrypt/live/turn-nc.mydomain.eu/fullchain.pem
pkey=/etc/letsencrypt/live/turn-nc.mydomain.eu/privkey.pem
cipher-list=“ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AES:RSA+3DES:!ADH:!AECDH:!MD5”

no-loopback-peers
no-multicast-peers

and here a par of turn log file 'sorry, it’s a bit long but : I suppose it clarifies the situation for someone who knows coturn server :

109: handle_udp_packet: New UDP endpoint: local addr :5349, remote addr :35205
109: session 000000000000000001: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
109: handle_udp_packet: New UDP endpoint: local addr :9443, remote addr :35205
109: session 001000000000000001: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
109: IPv4. tcp or tls connected to: :34853
109: IPv4. tcp or tls connected to: :36681
109: IPv4. tcp or tls connected to: :37915
109: IPv4. tcp or tls connected to: :43043
109: IPv4. tcp or tls connected to: :33239
109: session 001000000000000002: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
109: IPv4. Local relay addr: :57612
109: session 001000000000000001: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
109: session 001000000000000001: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
109: handle_udp_packet: New UDP endpoint: local addr :5349, remote addr :36082
109: session 000000000000000004: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
109: IPv4. Local relay addr: :62093
109: session 001000000000000002: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
109: session 001000000000000002: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
109: handle_udp_packet: New UDP endpoint: local addr :9443, remote addr :36082
109: session 000000000000000005: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
110: session 000000000000000002: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
110: handle_udp_packet: New UDP endpoint: local addr :5349, remote addr :36586
110: session 000000000000000006: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
110: IPv4. Local relay addr: :65463
110: session 000000000000000005: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
110: session 000000000000000005: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
110: handle_udp_packet: New UDP endpoint: local addr :9443, remote addr :36586
110: session 001000000000000005: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
110: IPv4. Local relay addr: :57266
110: session 000000000000000002: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
110: session 000000000000000002: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
110: session 001000000000000003: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
110: IPv4. Local relay addr: :53279
110: session 001000000000000005: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
110: session 001000000000000005: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
110: handle_udp_packet: New UDP endpoint: local addr :5349, remote addr :56604
110: session 000000000000000007: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
110: handle_udp_packet: New UDP endpoint: local addr :9443, remote addr :56604
110: session 000000000000000008: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
110: IPv4. Local relay addr: :60913
110: session 001000000000000003: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
110: session 001000000000000003: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
110: session 001000000000000004: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
110: IPv4. Local relay addr: :59999
110: session 000000000000000008: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
110: session 000000000000000008: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
110: handle_udp_packet: New UDP endpoint: local addr :5349, remote addr :58595
110: session 000000000000000009: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
110: IPv4. Local relay addr: :51083
110: session 001000000000000004: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
110: session 001000000000000004: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
110: handle_udp_packet: New UDP endpoint: local addr :9443, remote addr :58595
110: session 000000000000000010: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
110: session 000000000000000003: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
110: IPv4. Local relay addr: :58962
110: session 000000000000000010: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
110: session 000000000000000010: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
110: IPv4. Local relay addr: :53200
110: session 000000000000000003: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
110: session 000000000000000003: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
111: handle_udp_packet: New UDP endpoint: local addr :5349, remote addr :49667
111: session 000000000000000011: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
111: handle_udp_packet: New UDP endpoint: local addr :5349, remote addr :49668
111: session 001000000000000006: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
111: handle_udp_packet: New UDP endpoint: local addr :9443, remote addr :49667
111: session 001000000000000007: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
111: handle_udp_packet: New UDP endpoint: local addr :9443, remote addr :49668
111: session 001000000000000008: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
111: IPv4. tcp or tls connected to: :49666
111: session 000000000000000011: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
111: session 000000000000000012: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
111: IPv4. Local relay addr: :65397
111: session 001000000000000008: new, realm=<turn-nc.mydomain.eu>, username=<1533661292>, lifetime=3600
111: session 001000000000000008: realm <turn-nc.mydomain.eu> user <1533661292>: incoming packet ALLOCATE processed, success
111: session 001000000000000007: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
111: IPv4. Local relay addr: :54695
111: session 000000000000000012: new, realm=<turn-nc.mydomain.eu>, username=<1533661292>, lifetime=3600
111: session 000000000000000012: realm <turn-nc.mydomain.eu> user <1533661292>: incoming packet ALLOCATE processed, success
111: session 000000000000000011: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
111: session 001000000000000007: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
112: session 000000000000000011: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
112: session 001000000000000007: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
112: session 001000000000000005: refreshed, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=0
112: session 001000000000000005: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet REFRESH processed, success
112: session 000000000000000008: refreshed, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=0
112: session 000000000000000008: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet REFRESH processed, success
112: session 000000000000000010: refreshed, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=0
112: session 000000000000000010: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet REFRESH processed, success
112: session 001000000000000003: refreshed, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=0
112: session 001000000000000003: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet REFRESH processed, success
112: session 001000000000000004: refreshed, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=0
112: session 001000000000000004: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet REFRESH processed, success
112: session 000000000000000003: refreshed, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=0
112: session 000000000000000003: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet REFRESH processed, success
112: session 000000000000000003: TCP socket closed remotely :43043
112: session 000000000000000003: closed (2nd stage), user <1533661344> realm <turn-nc.mydomain.eu> origin <>, local :9443, remote :43043, reason: TCP connection closed by client (callback)
112: session 000000000000000003: delete: realm=<turn-nc.mydomain.eu>, username=<1533661344>
112: session 001000000000000003: TCP socket closed remotely :37915
112: session 001000000000000003: closed (2nd stage), user <1533661344> realm <turn-nc.mydomain.eu> origin <>, local :9443, remote :37915, reason: TCP connection closed by client (callback)
112: session 001000000000000003: delete: realm=<turn-nc.mydomain.eu>, username=<1533661344>
112: session 001000000000000004: TCP socket closed remotely :33239
112: session 001000000000000004: closed (2nd stage), user <1533661344> realm <turn-nc.mydomain.eu> origin <>, local :9443, remote :33239, reason: TCP connection closed by client (callback)
112: session 001000000000000004: delete: realm=<turn-nc.mydomain.eu>, username=<1533661344>
112: session 001000000000000007: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
112: session 000000000000000011: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
113: session 001000000000000005: closed (2nd stage), user <1533661344> realm <turn-nc.mydomain.eu> origin <>, local :9443, remote :36586, reason: allocation timeout
113: session 001000000000000005: delete: realm=<turn-nc.mydomain.eu>, username=<1533661344>
113: session 000000000000000008: closed (2nd stage), user <1533661344> realm <turn-nc.mydomain.eu> origin <>, local :9443, remote :56604, reason: allocation timeout
113: session 000000000000000008: delete: realm=<turn-nc.mydomain.eu>, username=<1533661344>
113: session 000000000000000010: closed (2nd stage), user <1533661344> realm <turn-nc.mydomain.eu> origin <>, local :9443, remote :58595, reason: allocation timeout
113: session 000000000000000010: delete: realm=<turn-nc.mydomain.eu>, username=<1533661344>
113: session 001000000000000001: peer lifetime updated: 300
113: session 001000000000000001: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet CREATE_PERMISSION processed, success
113: session 001000000000000001: peer lifetime updated: 300
113: session 001000000000000001: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet CREATE_PERMISSION processed, success
113: session 001000000000000002: peer lifetime updated: 300
113: session 001000000000000002: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet CREATE_PERMISSION processed, success
113: session 001000000000000002: peer lifetime updated: 300
113: session 001000000000000002: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet CREATE_PERMISSION processed, success
114: session 000000000000000011: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
114: session 001000000000000007: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
117: session 000000000000000011: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
117: session 001000000000000007: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
124: handle_udp_packet: New UDP endpoint: local addr :5349, remote addr :58530
124: session 001000000000000009: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
124: handle_udp_packet: New UDP endpoint: local addr :9443, remote addr :58530
124: session 000000000000000013: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
124: IPv4. tcp or tls connected to: :40531
124: IPv4. tcp or tls connected to: :39863
124: IPv4. tcp or tls connected to: :42423
124: IPv4. tcp or tls connected to: :33105
124: IPv4. tcp or tls connected to: :46837
124: session 001000000000000010: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
124: IPv4. Local relay addr: :62115
124: session 000000000000000013: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
124: session 000000000000000013: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
124: handle_udp_packet: New UDP endpoint: local addr :5349, remote addr :42826
124: session 000000000000000016: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
124: IPv4. Local relay addr: :65278
124: session 001000000000000010: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
124: session 001000000000000010: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
124: handle_udp_packet: New UDP endpoint: local addr :9443, remote addr :42826
124: session 001000000000000013: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
124: session 001000000000000012: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
124: IPv4. Local relay addr: :56411
124: session 001000000000000013: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
124: session 001000000000000013: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
124: handle_udp_packet: New UDP endpoint: local addr :5349, remote addr :44050
124: session 000000000000000017: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
124: IPv4. Local relay addr: :61786
124: session 001000000000000012: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
124: session 001000000000000012: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
124: handle_udp_packet: New UDP endpoint: local addr :9443, remote addr :44050
124: session 001000000000000014: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
124: session 001000000000000011: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
124: IPv4. Local relay addr: :56111
124: session 001000000000000014: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
124: session 001000000000000014: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
124: handle_udp_packet: New UDP endpoint: local addr :5349, remote addr :55523
124: session 001000000000000015: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
124: IPv4. Local relay addr: :50056
124: session 001000000000000011: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
124: session 001000000000000011: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
124: handle_udp_packet: New UDP endpoint: local addr :9443, remote addr :55523
124: session 000000000000000018: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
124: session 000000000000000014: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
124: IPv4. Local relay addr: :58480
124: session 000000000000000018: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
124: session 000000000000000018: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
124: handle_udp_packet: New UDP endpoint: local addr :5349, remote addr :44216
124: session 001000000000000016: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
124: IPv4. Local relay addr: :53224
124: session 000000000000000014: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
124: session 000000000000000014: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
124: handle_udp_packet: New UDP endpoint: local addr :9443, remote addr :44216
124: session 000000000000000019: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
124: session 000000000000000015: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
124: IPv4. Local relay addr: :58872
124: session 000000000000000019: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
124: session 000000000000000019: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
125: IPv4. Local relay addr: :52681
125: session 000000000000000015: new, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=3600
125: session 000000000000000015: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet ALLOCATE processed, success
126: handle_udp_packet: New UDP endpoint: local addr :5349, remote addr :49671
126: session 000000000000000020: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
126: handle_udp_packet: New UDP endpoint: local addr :9443, remote addr :49671
126: session 001000000000000017: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
126: handle_udp_packet: New UDP endpoint: local addr :5349, remote addr :49672
126: session 000000000000000021: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
126: IPv4. tcp or tls connected to: :49670
126: handle_udp_packet: New UDP endpoint: local addr :9443, remote addr :49672
126: session 000000000000000022: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
126: session 001000000000000018: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
126: session 000000000000000020: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
126: session 001000000000000017: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
126: IPv4. Local relay addr: :51557
126: session 000000000000000022: new, realm=<turn-nc.mydomain.eu>, username=<1533661292>, lifetime=3600
126: session 000000000000000022: realm <turn-nc.mydomain.eu> user <1533661292>: incoming packet ALLOCATE processed, success
126: IPv4. Local relay addr: :49303
126: session 001000000000000018: new, realm=<turn-nc.mydomain.eu>, username=<1533661292>, lifetime=3600
126: session 001000000000000018: realm <turn-nc.mydomain.eu> user <1533661292>: incoming packet ALLOCATE processed, success
126: session 000000000000000020: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
126: session 001000000000000017: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
127: session 000000000000000020: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
127: session 001000000000000017: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
128: session 000000000000000020: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
128: session 001000000000000017: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
128: session 001000000000000014: refreshed, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=0
128: session 001000000000000014: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet REFRESH processed, success
128: session 000000000000000018: refreshed, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=0
128: session 000000000000000018: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet REFRESH processed, success
128: session 000000000000000019: refreshed, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=0
128: session 000000000000000019: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet REFRESH processed, success
128: session 001000000000000011: refreshed, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=0
128: session 001000000000000011: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet REFRESH processed, success
128: session 000000000000000014: refreshed, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=0
128: session 000000000000000014: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet REFRESH processed, success
128: session 000000000000000015: refreshed, realm=<turn-nc.mydomain.eu>, username=<1533661344>, lifetime=0
128: session 000000000000000015: realm <turn-nc.mydomain.eu> user <1533661344>: incoming packet REFRESH processed, success
128: session 000000000000000014: TCP socket closed remotely :33105
128: session 001000000000000011: TCP socket closed remotely :39863
128: session 000000000000000014: closed (2nd stage), user <1533661344> realm <turn-nc.mydomain.eu> origin <>, local :9443, remote :33105, reason: TCP connection closed by client (callback)
128: session 000000000000000014: delete: realm=<turn-nc.mydomain.eu>, username=<1533661344>
128: session 000000000000000015: TCP socket closed remotely :46837
128: session 001000000000000011: closed (2nd stage), user <1533661344> realm <turn-nc.mydomain.eu> origin <>, local :9443, remote :39863, reason: TCP connection closed by client (callback)
128: session 001000000000000011: delete: realm=<turn-nc.mydomain.eu>, username=<1533661344>
128: session 000000000000000015: closed (2nd stage), user <1533661344> realm <turn-nc.mydomain.eu> origin <>, local :9443, remote :46837, reason: TCP connection closed by client (callback)
128: session 000000000000000015: delete: realm=<turn-nc.mydomain.eu>, username=<1533661344>
129: session 000000000000000020: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
129: session 001000000000000017: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized
129: session 001000000000000014: closed (2nd stage), user <1533661344> realm <turn-nc.mydomain.eu> origin <>, local :9443, remote :44050, reason: allocation timeout
129: session 001000000000000014: delete: realm=<turn-nc.mydomain.eu>, username=<1533661344>
129: session 000000000000000018: closed (2nd stage), user <1533661344> realm <turn-nc.mydomain.eu> origin <>, local :9443, remote :55523, reason: allocation timeout
129: session 000000000000000018: delete: realm=<turn-nc.mydomain.eu>, username=<1533661344>
129: session 000000000000000019: closed (2nd stage), user <1533661344> realm <turn-nc.mydomain.eu> origin <>, local :9443, remote :44216, reason: allocation timeout
129: session 000000000000000019: delete: realm=<turn-nc.mydomain.eu>, username=<1533661344>
133: session 000000000000000020: realm <turn-nc.mydomain.eu> user <>: incoming packet BINDING processed, success
133: session 001000000000000017: realm <turn-nc.mydomain.eu> user <>: incoming packet message processed, error 401: Unauthorized

Here is a ste-by-step installation guide:

https://www.allerstorfer.at/install-jsxc-javascript-xmpp-chat-on-nextcloud/

Thanks Sanook
There’s nothing more in this how-to, except xmpp that could be fine to set up :slight_smile:)
I’ve already configured a spreed.me instance out of nextcloud. I’d like to configure the Talk app even if I suppose spreed.Me is a good solution.
I post my log in coturn github repo to have their advice

problem still persists, here is an interesting information, it could be a firefox problem…