nickvergessen
commented
5 years ago @fancycode any idea?
Closed zicklag closed 5 years ago
nickvergessen
commented
5 years ago @fancycode any idea?
fancycode
commented
5 years ago Please provide additional information from about:webrtc (Firefox) or chrome://webrtc-internals/ (Chrome). This should contain the candidates payload that has been transmitted and will help with further looking into the issue.
zicklag
commented
5 years ago Thank you for looking into this. I just finished doing another test so I could get some logs:
fancycode
commented
5 years ago Your log doesn't show any relay candidates. Are you sure the TURN settings are correct and the server is reachable? You can test the TURN settings in the latest version of the Nextcloud Talk app.
zicklag
commented
5 years ago The Nextcloud Talk app version is 3.2.6 and it doesn't show any available updates. I can't find a test button or anything in the Talk configuration page, though.
Also, I just realized that in my TURN server logs say that it is binding my custom listening port and the listening port + 1. Are both of those ports used for the nextcloud setup? I am running the TURN server in a Docker container and I was only binding the one listening port.
nickvergessen
commented
5 years ago Please update to the newest Nextcloud + Talk version and see if that solves your problem.
vxq9e7bx
commented
4 years ago can this be reopened? I have the same issue with nextcloud 18.0.0 and talk 8.0.1 udp is explicitly deactivated
150: session 000000000000000001: realm <domain.tld> user <xxx>: incoming packet ALLOCATE processed, error 442: UDP Transport is not allowed by the TURN Server configuration
Name : coturn
Version : 4.5.1.1
Release : 1.el8
Architecture : x86_64
Size : 1.2 M
Source : coturn-4.5.1.1-1.el8.src.rpm
Repository : @System
From repo : epel
Summary : TURN/STUN & ICE Server
URL : https://github.com/coturn/coturn/cat /etc/coturn/turnserver.conf | grep -v "#" | grep -vE "^$"
listening-port=3478
listening-ip=IPv4
listening-ip=IPv6
relay-ip=IPv4
relay-ip=IPv6
verbose
fingerprint
use-auth-secret
static-auth-secret=XXXXXXXXXX
realm=domain.tld
total-quota=100
bps-capacity=0
no-udp
no-tls
no-dtls
no-udp-relay
stale-nonce=600
log-file=/var/log/coturn/turnserver.log
simple-log
no-multicast-peers
no-cli
EasyNetDev
commented
6 months ago Hi all,
Any updates? Even with Nextcloud 28 I'm noticing the same issue. Even if in Nextcloud I selected TCP Only for Turn Server.
nickvergessen
commented
6 months ago Please don't comment on a 6 year old issue. If you have an issue the code is mostlikely no longer the same, so create a new one.
Steps to reproduce
--no-udp-relayoptionExpected behaviour
I should be able to join a meeting behind a strict firewall that only allows allows the TURN server TCP port out. All meeting traffic should go over that one allowed port.
Actual behaviour
Browser
Microphone available: yes
Camera available: yes
Operating system: Ubuntu
Browser name: Firefox
Browser version: 63.0
Browser log
Spreed app
Spreed app version: 3.2.6
Custom TURN server configured: yes
Custom STUN server configured: no
Server configuration
My server is running the
nextcloud:13.0.6-apacheofficial Docker image.Operating system: Linux 4.4.0-1070-aws #80-Ubuntu SMP Thu Oct 4 13:56:07 UTC 2018 x86_64
Web server: Apache/2.4.25 (Debian) (apache2handler)
Database: pgsql PostgreSQL 10.4 on x86_64-pc-linux-musl, compiled by gcc (Alpine 6.4.0) 6.4.0, 64-bit
PHP version: 7.2.10 Modules loaded: Core, date, libxml, openssl, pcre, sqlite3, zlib, ctype, curl, dom, fileinfo, filter, ftp, hash, iconv, json, mbstring, SPL, PDO, session, posix, Reflection, standard, SimpleXML, pdo_sqlite, Phar, tokenizer, xml, xmlreader, xmlwriter, mysqlnd, apache2handler, apcu, exif, gd, intl, ldap, memcached, pcntl, pdo_mysql, pdo_pgsql, redis, sodium, zip, Zend OPcache
Nextcloud Version: 13.0.6 - 13.0.6.1
List of activated apps:
Nextcloud configuration: