Turn server port

Hallo,

ich habe einen raspberry pi 4 mit ncpi, und einer dns über noip.

ich versuche seit tagen einen stun server für nextcloud talk zum laufen zu bekommen aber irgendwie funktioniert es nicht und ich finde oder vll verstehe den fehler nicht.

Wenn ich in der ios app nur meine domain eingebe auf einem android gerät funktioniert es aber sobald ich den port dazu eingebe sagt er server nicht gefunden.

nun habe ich google ein wenig befragt und einen befehl gefunden der mir ein wenig mehr sagen soll.

sudo turnserver -L meine.domain -a -b /usr/local/etc/turnuserdb.conf -f -r meine.domain

dann wirft er das aus

0: log file opened: /var/log/turn_28636_2021-08-10.log
0: Listener address to use: 192.168.178.32
0: 0 bytes per second allowed, combined server capacity
error resolving 'meine.domain' hostname: No address associated with hostname
1: ERROR: Cannot add a listener address: meine.domain
1: ERROR: 
CONFIG ERROR: Empty cli-password, and so telnet cli interface is disabled! Please set a non empty cli-password!

Meine turnserver.conf sieht wie folgt aus

    tls-listening-port=5349
    fingerprint
    use-auth-secret
    static-auth-secret=<secret>
    realm=meinedomain.de
    total-quota=100
    bps-capacity=0
    stale-nonce=600
    cipher-list=“ECDHE-RSA-AES256-GCM-SHA512:DHE-RSA-AES256-GCM-SHA512:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384″
    no-multicast-peers
    dh-file=/etc/nginx/dhparams/dhparams.pem
    no-tlsv1
    no-tlsv1_1
    no-stdout-log

und in nc wird mir auch der haken angezeigt das er läuft.

Ich niutze das nicht. Trotzdem ein paar Anmerkungen:

Eine Kombination besteht eigentlich aus einem Socket als IP und Port.
Irgendwie ist die Meldung nichts aussagend. Welcher Port soll denn benutzt werden?

Vielleicht läuft da ja schon was.

Was sagt denn z. B.:

netstat -an |grep 5349
lsof -i |grep 5349

“lsof” musst du evtl. nachinstallieren. Lohnt sich aber.

danke für deine hilfe schonmal.

ich hab davon leider auch nicht so die ahnung . erst wollte ich 5349 aber jetzt hab ich 3478 gewählt:sweat_smile:

da kommt:

ps:nicht wundern ich habe den port jetzt auf 3478

root@nextcloudpi:/home/pi# netstat -an |grep 3478
tcp        0      0 192.168.178.32:3478     0.0.0.0:*               LISTEN     
tcp        0      0 192.168.178.32:3478     0.0.0.0:*               LISTEN     
tcp        0      0 192.168.178.32:3478     0.0.0.0:*               LISTEN     
tcp        0      0 192.168.178.32:3478     0.0.0.0:*               LISTEN     
sctp                192.168.178.32:3478                             LISTEN     
sctp                192.168.178.32:3478                             LISTEN     
sctp                192.168.178.32:3478                             LISTEN     
sctp                192.168.178.32:3478                             LISTEN     
udp        0      0 192.168.178.32:3478     0.0.0.0:*                          
udp        0      0 192.168.178.32:3478     0.0.0.0:*                          
udp        0      0 192.168.178.32:3478     0.0.0.0:*                          
udp        0      0 192.168.178.32:3478     0.0.0.0:*                          
root@nextcloudpi:/home/pi# lsof -i |grep 3478
turnserve  1756     root   18u  IPv4 494556      0t0  TCP 192.168.178.32:3478 (LISTEN)
turnserve  1756     root   19u  IPv4 495908      0t0  TCP 192.168.178.32:3478 (LISTEN)
turnserve  1756     root   28u  IPv4 495236      0t0  UDP 192.168.178.32:3478 
turnserve  1756     root   31u  IPv4 493431      0t0  TCP 192.168.178.32:3478 (LISTEN)
turnserve  1756     root   32u  IPv4 494559      0t0  TCP 192.168.178.32:3478 (LISTEN)
turnserve  1756     root   33u  IPv4 495237      0t0  UDP 192.168.178.32:3478 
turnserve  1756     root   34u  IPv4 495238      0t0  UDP 192.168.178.32:3478 
turnserve  1756     root   35u  IPv4 495239      0t0  UDP 192.168.178.32:3478

Ok kommen wir zum Namen.
Was steht denn bei “meine.domain” wirklich. Voll qualifiziert, nur ein Name, …
Versuche es auch mal lokal aufzulösen.

host 192.168.178.32
host meine.domain

Geht das?

1 Like

meine.domain habe ich natürlich zensiert was jetzt nicht mehr zensiert ist :sweat_smile:

root@nextcloudpi:/home/pi# host cr-cloudy.ddns.net
cr-cloudy.ddns.net has address 192.168.178.32
root@nextcloudpi:/home/pi# host 192.168.178.32
Host 32.178.168.192.in-addr.arpa. not found: 3(NXDOMAIN)

komisch finde ich schonmal das die ip so verdreht wird :sweat_smile:

ich glaube ich hatte vorhin einen tipfehler in meiner domain weil jetzte spuckt er noch das aus:

root@nextcloudpi:/home/pi# sudo turnserver -L cr-cloudy.ddns.net -a -b /usr/local/etc/turnuserdb.conf -f -r cr-cloudy.ddns.net
0: log file opened: /var/log/turn_2473_2021-08-10.log
0: Listener address to use: 192.168.178.32
0: 0 bytes per second allowed, combined server capacity

Meiner Ansicht nach muß es heißen

realm=meinnextcloud.meinedomain.de

im log steht das da. daraus werd ich aber auch nicht schlauer:

Aug 10 15:39:00 nextcloudpi turnserver: 0: Config file found: /etc/turnserver.conf
Aug 10 15:39:00 nextcloudpi turnserver: 0: #012RFC 3489/5389/5766/5780/6062/6156 STUN/TURN Server#012Version Coturn-4.5.1.1 'dan Eider'
Aug 10 15:39:00 nextcloudpi turnserver: 0: #012Max number of open files/sockets allowed for this process: 1048576
Aug 10 15:39:00 nextcloudpi turnserver: 0: #012Due to the open files/sockets limitation,#012max supported number of TURN Sessions possible is: 524000 (approximately)
Aug 10 15:39:00 nextcloudpi turnserver: 0: #012#012==== Show him the instruments, Practical Frost: ====#012
Aug 10 15:39:00 nextcloudpi turnserver: 0: TLS supported
Aug 10 15:39:00 nextcloudpi turnserver: 0: DTLS supported
Aug 10 15:39:00 nextcloudpi turnserver: 0: DTLS 1.2 supported
Aug 10 15:39:00 nextcloudpi turnserver: 0: TURN/STUN ALPN supported
Aug 10 15:39:00 nextcloudpi turnserver: 0: Third-party authorization (oAuth) supported
Aug 10 15:39:00 nextcloudpi turnserver: 0: GCM (AEAD) supported
Aug 10 15:39:00 nextcloudpi turnserver: 0: OpenSSL compile-time version: OpenSSL 1.1.1d  10 Sep 2019 (0x1010104f)
Aug 10 15:39:00 nextcloudpi turnserver: 0: 
Aug 10 15:39:00 nextcloudpi turnserver: 0: SQLite supported, default database location is /var/lib/turn/turndb
Aug 10 15:39:00 nextcloudpi turnserver: 0: Redis supported
Aug 10 15:39:00 nextcloudpi turnserver: 0: PostgreSQL supported
Aug 10 15:39:00 nextcloudpi turnserver: 0: MySQL supported
Aug 10 15:39:00 nextcloudpi turnserver: 0: MongoDB is not supported
Aug 10 15:39:00 nextcloudpi turnserver: 0: 
Aug 10 15:39:00 nextcloudpi turnserver: 0: Default Net Engine version: 3 (UDP thread per CPU core)#012#012=====================================================#012
Aug 10 15:39:00 nextcloudpi turnserver: 0: Domain name: 
Aug 10 15:39:00 nextcloudpi turnserver: 0: Default realm: cr-cloudy.ddns.net
Aug 10 15:39:00 nextcloudpi turnserver: 0: #012CONFIGURATION ALERT: You specified --lt-cred-mech and --use-auth-secret in the same time.#012Be aware that you could not mix the username/password and the shared secret based auth methohds. #012Shared secret overrides username/password based auth method. Check your configuration!
Aug 10 15:39:00 nextcloudpi turnserver: 0: #012CONFIG ERROR: Empty cli-password, and so telnet cli interface is disabled! Please set a non empty cli-password!
Aug 10 15:39:00 nextcloudpi turnserver: 0: WARNING: cannot find certificate file: turn_server_cert.pem (1)
Aug 10 15:39:00 nextcloudpi turnserver: 0: WARNING: cannot start TLS and DTLS listeners because certificate file is not set properly
Aug 10 15:39:00 nextcloudpi turnserver: 0: WARNING: cannot find private key file: turn_server_pkey.pem (1)
Aug 10 15:39:00 nextcloudpi turnserver: 0: WARNING: cannot start TLS and DTLS listeners because private key file is not set properly
Aug 10 15:39:00 nextcloudpi turnserver: 0: Relay address to use: 192.168.178.32
Aug 10 15:39:00 nextcloudpi turnserver: 0: pid file created: /var/run/turnserver.pid
Aug 10 15:39:00 nextcloudpi turnserver: 0: IO method (main listener thread): epoll (with changelist)
Aug 10 15:39:00 nextcloudpi turnserver: 0: WARNING: I cannot support STUN CHANGE_REQUEST functionality because only one IP address is provided
Aug 10 15:39:00 nextcloudpi turnserver: 0: Wait for relay ports initialization...
Aug 10 15:39:00 nextcloudpi turnserver: 0:   relay 192.168.178.32 initialization...
Aug 10 15:39:00 nextcloudpi turnserver: 0:   relay 192.168.178.32 initialization done
Aug 10 15:39:00 nextcloudpi turnserver: 0: Relay ports initialization done
Aug 10 15:39:00 nextcloudpi turnserver: 0: IO method (general relay thread): epoll (with changelist)
Aug 10 15:39:00 nextcloudpi turnserver: 0: IO method (general relay thread): epoll (with changelist)
Aug 10 15:39:00 nextcloudpi turnserver: 0: turn server id=0 created
Aug 10 15:39:00 nextcloudpi turnserver: 0: turn server id=1 created
Aug 10 15:39:00 nextcloudpi turnserver: 0: IO method (general relay thread): epoll (with changelist)
Aug 10 15:39:00 nextcloudpi turnserver: 0: turn server id=2 created
Aug 10 15:39:00 nextcloudpi turnserver: 0: IO method (general relay thread): epoll (with changelist)
Aug 10 15:39:00 nextcloudpi turnserver: 0: turn server id=3 created
Aug 10 15:39:00 nextcloudpi turnserver: 0: Total General servers: 4
Aug 10 15:39:00 nextcloudpi turnserver: 0: IO method (auth thread): epoll (with changelist)
Aug 10 15:39:00 nextcloudpi turnserver: 0: IO method (auth thread): epoll (with changelist)
Aug 10 15:39:00 nextcloudpi turnserver: 0: SQLite DB connection success: /usr/local/etc/turnuserdb.conf
Aug 10 15:39:00 nextcloudpi turnserver: 0: IO method (admin thread): epoll (with changelist)
Aug 10 15:39:33 nextcloudpi turnserver: 166: IPv4. tcp or tls connected to: 87.142.192.143:55725
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 001000000000000001: realm <cr-cloudy.ddns.net> user <>: incoming packet message processed, error 401: Unauthorized
Aug 10 15:39:33 nextcloudpi turnserver: 166: IPv4. tcp or tls connected to: 87.142.192.143:55726
Aug 10 15:39:33 nextcloudpi turnserver: 166: IPv4. Local relay addr: 192.168.178.32:50315
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 001000000000000001: new, realm=<cr-cloudy.ddns.net>, username=<1628606674:turn-test-user>, lifetime=3600
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 001000000000000001: realm <cr-cloudy.ddns.net> user <1628606674:turn-test-user>: incoming packet ALLOCATE processed, success
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 001000000000000002: realm <cr-cloudy.ddns.net> user <>: incoming packet message processed, error 401: Unauthorized
Aug 10 15:39:33 nextcloudpi turnserver: 166: IPv4. Local relay addr: 192.168.178.32:65377
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 001000000000000002: new, realm=<cr-cloudy.ddns.net>, username=<1628606674:turn-test-user>, lifetime=3600
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 001000000000000002: realm <cr-cloudy.ddns.net> user <1628606674:turn-test-user>: incoming packet ALLOCATE processed, success
Aug 10 15:39:33 nextcloudpi turnserver: 166: handle_udp_packet: New UDP endpoint: local addr 192.168.178.32:3478, remote addr 87.142.192.143:52616
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 003000000000000002: realm <cr-cloudy.ddns.net> user <>: incoming packet message processed, error 401: Unauthorized
Aug 10 15:39:33 nextcloudpi turnserver: 166: IPv4. Local relay addr: 192.168.178.32:64019
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 003000000000000002: new, realm=<cr-cloudy.ddns.net>, username=<1628606674:turn-test-user>, lifetime=3600
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 003000000000000002: realm <cr-cloudy.ddns.net> user <1628606674:turn-test-user>: incoming packet ALLOCATE processed, success
Aug 10 15:39:33 nextcloudpi turnserver: 166: handle_udp_packet: New UDP endpoint: local addr 192.168.178.32:3478, remote addr 87.142.192.143:56154
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 002000000000000002: realm <cr-cloudy.ddns.net> user <>: incoming packet message processed, error 401: Unauthorized
Aug 10 15:39:33 nextcloudpi turnserver: 166: IPv4. Local relay addr: 192.168.178.32:52151
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 002000000000000002: new, realm=<cr-cloudy.ddns.net>, username=<1628606674:turn-test-user>, lifetime=3600
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 002000000000000002: realm <cr-cloudy.ddns.net> user <1628606674:turn-test-user>: incoming packet ALLOCATE processed, success
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 001000000000000001: refreshed, realm=<cr-cloudy.ddns.net>, username=<1628606674:turn-test-user>, lifetime=0
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 001000000000000001: realm <cr-cloudy.ddns.net> user <1628606674:turn-test-user>: incoming packet REFRESH processed, success
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 003000000000000002: refreshed, realm=<cr-cloudy.ddns.net>, username=<1628606674:turn-test-user>, lifetime=0
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 003000000000000002: realm <cr-cloudy.ddns.net> user <1628606674:turn-test-user>: incoming packet REFRESH processed, success
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 002000000000000002: refreshed, realm=<cr-cloudy.ddns.net>, username=<1628606674:turn-test-user>, lifetime=0
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 002000000000000002: realm <cr-cloudy.ddns.net> user <1628606674:turn-test-user>: incoming packet REFRESH processed, success
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 001000000000000001: TCP socket closed remotely 87.142.192.143:55725
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 001000000000000001: usage: realm=<cr-cloudy.ddns.net>, username=<1628606674:turn-test-user>, rp=3, rb=324, sp=3, sb=332
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 001000000000000001: closed (2nd stage), user <1628606674:turn-test-user> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:3478, remote 87.142.192.143:55725, reason: TCP connection closed by client (callback)
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 001000000000000001: delete: realm=<cr-cloudy.ddns.net>, username=<1628606674:turn-test-user>
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 001000000000000002: TCP socket closed remotely 87.142.192.143:55726
Aug 10 15:39:33 nextcloudpi turnserver: 166: session 001000000000000002: usage: realm=<cr-cloudy.ddns.net>, username=<1628606674:turn-test-user>, rp=2, rb=188, sp=2, sb=240
Aug 10 15:39:34 nextcloudpi turnserver: 166: session 001000000000000002: closed (2nd stage), user <1628606674:turn-test-user> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:3478, remote 87.142.192.143:55726, reason: TCP connection closed by client (callback)
Aug 10 15:39:34 nextcloudpi turnserver: 166: session 001000000000000002: delete: realm=<cr-cloudy.ddns.net>, username=<1628606674:turn-test-user>
Aug 10 15:39:34 nextcloudpi turnserver: 167: session 003000000000000002: usage: realm=<cr-cloudy.ddns.net>, username=<1628606674:turn-test-user>, rp=3, rb=324, sp=3, sb=332
Aug 10 15:39:34 nextcloudpi turnserver: 167: session 003000000000000002: closed (2nd stage), user <1628606674:turn-test-user> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:3478, remote 87.142.192.143:52616, reason: allocation timeout
Aug 10 15:39:34 nextcloudpi turnserver: 167: session 003000000000000002: delete: realm=<cr-cloudy.ddns.net>, username=<1628606674:turn-test-user>
Aug 10 15:39:34 nextcloudpi turnserver: 167: session 002000000000000002: usage: realm=<cr-cloudy.ddns.net>, username=<1628606674:turn-test-user>, rp=3, rb=324, sp=3, sb=332
Aug 10 15:39:34 nextcloudpi turnserver: 167: session 002000000000000002: closed (2nd stage), user <1628606674:turn-test-user> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:3478, remote 87.142.192.143:56154, reason: allocation timeout
Aug 10 15:39:34 nextcloudpi turnserver: 167: session 002000000000000002: delete: realm=<cr-cloudy.ddns.net>, username=<1628606674:turn-test-user>
Aug 10 15:41:25 nextcloudpi turnserver: 278: IPv4. tcp or tls connected to: 87.142.192.143:58543
Aug 10 15:42:10 nextcloudpi turnserver: 323: session 002000000000000003: TCP socket closed remotely 87.142.192.143:58543
Aug 10 15:42:10 nextcloudpi turnserver: 323: session 002000000000000003: usage: realm=<cr-cloudy.ddns.net>, username=<>, rp=0, rb=0, sp=0, sb=0
Aug 10 15:42:10 nextcloudpi turnserver: 323: session 002000000000000003: closed (2nd stage), user <> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:3478, remote 87.142.192.143:58543, reason: TCP connection closed by client (callback)
Aug 10 15:42:10 nextcloudpi turnserver: 323: IPv4. tcp or tls connected to: 87.142.192.143:58545
Aug 10 15:42:10 nextcloudpi turnserver: 323: session 001000000000000003: client socket to be closed in client handler: ss=0x7fa002a510
Aug 10 15:42:10 nextcloudpi turnserver: 323: session 001000000000000003: usage: realm=<cr-cloudy.ddns.net>, username=<>, rp=1, rb=212, sp=0, sb=0
Aug 10 15:42:10 nextcloudpi turnserver: 323: session 001000000000000003: closed (2nd stage), user <> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:3478, remote 87.142.192.143:58545, reason: general

was du meinst das meinenextcloud muss davor?

Du mußt Deine Subdomain Deiner Nextcloud-Installation davor setzen.
Also Deine
Subdomain ist z.B. meineCloud
Deine
Domain ist z.B. meineDomain
dann ist
realm=meineCloud.meineDomain.de

1 Like

Vielleicht hilft Dir ja das auch weiter:

https://adminforge.de/nextcloud/nextcloud-talk-mit-eigenem-turn-server/

1 Like

Ja nach der hab ich es ja gemacht.

Aber da steht nix von

Aber ich teste es dann mal und gebe rückmeldung.

Ich poste Dir hier mal eine Konfiguration, die funktioniert (Du mußt natürlich Deine Subdomain und Domain eintragen und cert und pkey):

tls-listening-port=5349
fingerprint
lt-cred-mech
use-auth-secret
static-auth-secret=<secret>
realm=yournextcloud.yourdomain.de
total-quota=100
bps-capacity=0
stale-nonce=600
cert=/etc/letsencrypt/live/yournextcloud.yourdomain.de/fullchain.pem
pkey=/etc/letsencrypt/live/yournextcloud.yourdomain.de/privkey.pem
cipher-list=“ECDHE-RSA-AES256-GCM-SHA512:DHE-RSA-AES256-GCM-SHA512:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384”
dh-file=/etc/ssl/private/dhparam.pem
no-stdout-log
log-file=/var/log/turn.log
syslog
no-loopback-peers
no-multicast-peers
no-tlsv1
no-tlsv1_1

1 Like

Hm also die domain ändern hat bei mir schonmal nichts geändert.

Ist das vielleicht das problem? Ich hab kein cert und pkey?

Könntest du evtl. dein syslog mal posten das ich es mal vergleichen kann wie es aussehen muss? Weil ich weis nicht wo der fehler noch liegt.

Und muss ich dann im dashboard der nc im stun auch meinecloud.meinedomain.de nehmen?

ich hab nochmal ein wenig rumgespielt aber irgendwie werd ich nicht schlauer aus den logs

Aug 11 00:31:03 nextcloudpi turnserver: 2921: session 000000000000000007: SSL shutdown received, socket to be closed (local 192.168.178.32:5349, remote 80.187.116.78:8490)
Aug 11 00:31:14 nextcloudpi turnserver: 2932: IPv4. tcp or tls connected to: 80.187.116.78:8563
Aug 11 00:31:14 nextcloudpi turnserver: 2932: IPv4. tcp or tls connected to: 80.187.116.78:8564
Aug 11 00:31:14 nextcloudpi turnserver: 2932: IPv4. tcp or tls connected to: 80.187.116.78:8567
Aug 11 00:31:14 nextcloudpi turnserver: 2932: session 003000000000000006: client socket to be closed in client handler: ss=0x7f70007500
Aug 11 00:31:14 nextcloudpi turnserver: 2932: session 003000000000000006: usage: realm=<cr-cloudy.ddns.net>, username=<>, rp=1, rb=742, sp=0, sb=0
Aug 11 00:31:14 nextcloudpi turnserver: 2932: session 003000000000000006: closed (2nd stage), user <> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:5349, remote 80.187.116.78:8567, reason: general
Aug 11 00:31:14 nextcloudpi turnserver: 2932: session 003000000000000006: SSL shutdown received, socket to be closed (local 192.168.178.32:5349, remote 80.187.116.78:8567)
Aug 11 00:31:14 nextcloudpi turnserver: 2932: session 000000000000000008: client socket to be closed in client handler: ss=0x7f800177c0
Aug 11 00:31:14 nextcloudpi turnserver: 2932: session 000000000000000008: usage: realm=<cr-cloudy.ddns.net>, username=<>, rp=1, rb=742, sp=0, sb=0
Aug 11 00:31:14 nextcloudpi turnserver: 2932: session 000000000000000008: closed (2nd stage), user <> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:5349, remote 80.187.116.78:8563, reason: general
Aug 11 00:31:14 nextcloudpi turnserver: 2932: session 000000000000000008: SSL shutdown received, socket to be closed (local 192.168.178.32:5349, remote 80.187.116.78:8563)
Aug 11 00:31:14 nextcloudpi turnserver: 2932: session 000000000000000009: client socket to be closed in client handler: ss=0x7f8004a5d0
Aug 11 00:31:14 nextcloudpi turnserver: 2932: session 000000000000000009: usage: realm=<cr-cloudy.ddns.net>, username=<>, rp=1, rb=742, sp=0, sb=0
Aug 11 00:31:14 nextcloudpi turnserver: 2932: session 000000000000000009: closed (2nd stage), user <> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:5349, remote 80.187.116.78:8564, reason: general
Aug 11 00:31:14 nextcloudpi turnserver: 2932: session 000000000000000009: SSL shutdown received, socket to be closed (local 192.168.178.32:5349, remote 80.187.116.78:8564)
Aug 11 00:31:17 nextcloudpi turnserver: 2935: IPv4. tcp or tls connected to: 87.142.192.143:60781
Aug 11 00:31:17 nextcloudpi turnserver: 2935: IPv4. tcp or tls connected to: 87.142.192.143:60782
Aug 11 00:31:17 nextcloudpi turnserver: 2935: session 003000000000000007: client socket to be closed in client handler: ss=0x7f70007500
Aug 11 00:31:17 nextcloudpi turnserver: 2935: session 003000000000000007: usage: realm=<cr-cloudy.ddns.net>, username=<>, rp=1, rb=742, sp=0, sb=0
Aug 11 00:31:17 nextcloudpi turnserver: 2935: session 003000000000000007: closed (2nd stage), user <> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:5349, remote 87.142.192.143:60782, reason: general
Aug 11 00:31:17 nextcloudpi turnserver: 2935: session 003000000000000007: SSL shutdown received, socket to be closed (local 192.168.178.32:5349, remote 87.142.192.143:60782)
Aug 11 00:31:17 nextcloudpi turnserver: 2935: session 002000000000000009: client socket to be closed in client handler: ss=0x7f7c01ed10
Aug 11 00:31:17 nextcloudpi turnserver: 2935: session 002000000000000009: usage: realm=<cr-cloudy.ddns.net>, username=<>, rp=1, rb=742, sp=0, sb=0
Aug 11 00:31:17 nextcloudpi turnserver: 2935: session 002000000000000009: closed (2nd stage), user <> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:5349, remote 87.142.192.143:60781, reason: general
Aug 11 00:31:17 nextcloudpi turnserver: 2935: session 002000000000000009: SSL shutdown received, socket to be closed (local 192.168.178.32:5349, remote 87.142.192.143:60781)
Aug 11 00:31:17 nextcloudpi turnserver: 2935: IPv4. tcp or tls connected to: 87.142.192.143:60783
Aug 11 00:31:17 nextcloudpi turnserver: 2935: session 001000000000000004: client socket to be closed in client handler: ss=0x7f78007b90
Aug 11 00:31:17 nextcloudpi turnserver: 2935: session 001000000000000004: usage: realm=<cr-cloudy.ddns.net>, username=<>, rp=1, rb=742, sp=0, sb=0
Aug 11 00:31:17 nextcloudpi turnserver: 2935: session 001000000000000004: closed (2nd stage), user <> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:5349, remote 87.142.192.143:60783, reason: general
Aug 11 00:31:17 nextcloudpi turnserver: 2935: session 001000000000000004: SSL shutdown received, socket to be closed (local 192.168.178.32:5349, remote 87.142.192.143:60783)
Aug 11 00:31:18 nextcloudpi turnserver: 2936: IPv4. tcp or tls connected to: 87.142.192.143:60784
Aug 11 00:31:18 nextcloudpi turnserver: 2936: IPv4. tcp or tls connected to: 87.142.192.143:60785
Aug 11 00:31:18 nextcloudpi turnserver: 2936: session 002000000000000011: client socket to be closed in client handler: ss=0x7f7c04b0f0
Aug 11 00:31:18 nextcloudpi turnserver: 2936: session 002000000000000011: usage: realm=<cr-cloudy.ddns.net>, username=<>, rp=1, rb=742, sp=0, sb=0
Aug 11 00:31:18 nextcloudpi turnserver: 2936: session 002000000000000011: closed (2nd stage), user <> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:5349, remote 87.142.192.143:60785, reason: general
Aug 11 00:31:18 nextcloudpi turnserver: 2936: session 002000000000000011: SSL shutdown received, socket to be closed (local 192.168.178.32:5349, remote 87.142.192.143:60785)
Aug 11 00:31:18 nextcloudpi turnserver: 2936: session 002000000000000010: client socket to be closed in client handler: ss=0x7f7c01ed10
Aug 11 00:31:18 nextcloudpi turnserver: 2936: session 002000000000000010: usage: realm=<cr-cloudy.ddns.net>, username=<>, rp=1, rb=742, sp=0, sb=0
Aug 11 00:31:18 nextcloudpi turnserver: 2936: session 002000000000000010: closed (2nd stage), user <> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:5349, remote 87.142.192.143:60784, reason: general
Aug 11 00:31:18 nextcloudpi turnserver: 2936: session 002000000000000010: SSL shutdown received, socket to be closed (local 192.168.178.32:5349, remote 87.142.192.143:60784)
Aug 11 00:31:18 nextcloudpi turnserver: 2936: IPv4. tcp or tls connected to: 87.142.192.143:60788
Aug 11 00:31:18 nextcloudpi turnserver: 2936: session 002000000000000012: client socket to be closed in client handler: ss=0x7f7c01ed10
Aug 11 00:31:18 nextcloudpi turnserver: 2936: session 002000000000000012: usage: realm=<cr-cloudy.ddns.net>, username=<>, rp=1, rb=742, sp=0, sb=0
Aug 11 00:31:18 nextcloudpi turnserver: 2936: session 002000000000000012: closed (2nd stage), user <> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:5349, remote 87.142.192.143:60788, reason: general
Aug 11 00:31:18 nextcloudpi turnserver: 2936: session 002000000000000012: SSL shutdown received, socket to be closed (local 192.168.178.32:5349, remote 87.142.192.143:60788)
Aug 11 00:31:18 nextcloudpi turnserver: 2937: IPv4. tcp or tls connected to: 87.142.192.143:60790
Aug 11 00:31:18 nextcloudpi turnserver: 2937: IPv4. tcp or tls connected to: 87.142.192.143:60791
Aug 11 00:31:18 nextcloudpi turnserver: 2937: session 003000000000000008: client socket to be closed in client handler: ss=0x7f70007500
Aug 11 00:31:18 nextcloudpi turnserver: 2937: session 003000000000000008: usage: realm=<cr-cloudy.ddns.net>, username=<>, rp=1, rb=742, sp=0, sb=0
Aug 11 00:31:18 nextcloudpi turnserver: 2937: session 003000000000000008: closed (2nd stage), user <> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:5349, remote 87.142.192.143:60791, reason: general
Aug 11 00:31:18 nextcloudpi turnserver: 2937: session 003000000000000008: SSL shutdown received, socket to be closed (local 192.168.178.32:5349, remote 87.142.192.143:60791)
Aug 11 00:31:19 nextcloudpi turnserver: 2937: session 001000000000000005: client socket to be closed in client handler: ss=0x7f78007b90
Aug 11 00:31:19 nextcloudpi turnserver: 2937: session 001000000000000005: usage: realm=<cr-cloudy.ddns.net>, username=<>, rp=1, rb=742, sp=0, sb=0
Aug 11 00:31:19 nextcloudpi turnserver: 2937: session 001000000000000005: closed (2nd stage), user <> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:5349, remote 87.142.192.143:60790, reason: general
Aug 11 00:31:19 nextcloudpi turnserver: 2937: session 001000000000000005: SSL shutdown received, socket to be closed (local 192.168.178.32:5349, remote 87.142.192.143:60790)
Aug 11 00:31:19 nextcloudpi turnserver: 2937: IPv4. tcp or tls connected to: 87.142.192.143:60792
Aug 11 00:31:19 nextcloudpi turnserver: 2937: session 000000000000000010: client socket to be closed in client handler: ss=0x7f8002fa30
Aug 11 00:31:19 nextcloudpi turnserver: 2937: session 000000000000000010: usage: realm=<cr-cloudy.ddns.net>, username=<>, rp=1, rb=742, sp=0, sb=0
Aug 11 00:31:19 nextcloudpi turnserver: 2937: session 000000000000000010: closed (2nd stage), user <> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:5349, remote 87.142.192.143:60792, reason: general
Aug 11 00:31:19 nextcloudpi turnserver: 2937: session 000000000000000010: SSL shutdown received, socket to be closed (local 192.168.178.32:5349, remote 87.142.192.143:60792)
Aug 11 00:34:00 nextcloudpi turnserver: 3099: IPv4. tcp or tls connected to: 87.142.192.143:52287
Aug 11 00:34:00 nextcloudpi turnserver: 3099: session 003000000000000009: client socket to be closed in client handler: ss=0x7f70007500
Aug 11 00:34:00 nextcloudpi turnserver: 3099: session 003000000000000009: usage: realm=<cr-cloudy.ddns.net>, username=<>, rp=1, rb=212, sp=0, sb=0
Aug 11 00:34:00 nextcloudpi turnserver: 3099: session 003000000000000009: closed (2nd stage), user <> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:5349, remote 87.142.192.143:52287, reason: general
Aug 11 00:34:00 nextcloudpi turnserver: 3099: session 003000000000000009: SSL shutdown received, socket to be closed (local 192.168.178.32:5349, remote 87.142.192.143:52287)
Aug 11 00:34:01 nextcloudpi turnserver: 3099: IPv4. tcp or tls connected to: 87.142.192.143:52288
Aug 11 00:34:01 nextcloudpi turnserver: 3099: session 001000000000000006: client socket to be closed in client handler: ss=0x7f78007b90
Aug 11 00:34:01 nextcloudpi turnserver: 3099: session 001000000000000006: usage: realm=<cr-cloudy.ddns.net>, username=<>, rp=1, rb=212, sp=0, sb=0
Aug 11 00:34:01 nextcloudpi turnserver: 3099: session 001000000000000006: closed (2nd stage), user <> realm <cr-cloudy.ddns.net> origin <>, local 192.168.178.32:5349, remote 87.142.192.143:52288, reason: general

aussser das er irgendwie den port nicht and die domain vergibt aber an alles andre.

und

root@nextcloudpi:/home/pi# sudo turnserver -L cr-cloudy.myddns.net -a -b /usr/local/etc/turnuserdb.conf -f -r cr-cloudy.myddns.net
0: log file opened: /var/log/turn_10323_2021-08-11.log
0: 0 bytes per second allowed, combined server capacity
error resolving 'cr-cloudy.myddns.net' hostname: No address associated with hostname
0: ERROR: Cannot add a listener address: cr-cloudy.myddns.net
0: ERROR: 
CONFIG ERROR: Empty cli-password, and so telnet cli interface is disabled! Please set a non empty cli-password!
0: ERROR: set_ctx: ERROR: cannot set DH

Ich habe erst mal nur bis hier gelesen.
Es ist nicht Sinn und Zweck DynDNS-Dienste für interne IP-Adressen zu verwenden.
Mindestens wird Talk nicht aus dem Internet so funktionieren. Egal was du machst.
Und im lokalen Netz brauchst du - soweit ich mich erinnere - TURN nicht :wink:

Ich will es ja auch nicht für intern haben sondern für extern :sweat_smile:

Ja. Dann fängt der Fehler schon weit vorher an.
Du musst deinen DSL-Router so konfigurieren, dass er den DynDNS-Dienst nutzt und am Ende über den Namen eine externe IP-Adresse ( also diese: https://ifconfig.me/ip ) aufgelöst werden. Danach kannst du dich um die anderen Probleme kümmern.

Die ports sind frei gegebn. Aber ich werds auch aufgeben :sweat_smile: über die domain ist es ja erreichbar dann lass ich das mit dem port halt. Danke trotzdem.

Ok. Ich habe noch mal geschaut. Scheinbar verwendet

cr-cloudy.ddns.net

von außen eine weltweite IP und von innen eine interne IP-Adresse.

Also bei meiner internen Nextcloud ist es nicht so. Da verwende ich von außen und innen einen weltweiten DynDNS-Namen mit gleicher externer IP siehe NAT-Loopback bzw. Hairpinning.