Dual stack cannot be used
Author: StephenJose-DaiCreated Jul 31, 2026Updated Aug 23, 2026
My current version is 4.15.0-r0. I found that it takes a long time to connect after using dual-stack. I showed the logs to the AI, and the AI told me it's a bug; Coturn doesn't support dual-stack. I have no problems using IPv4. Does Coturn currently support dual-stack? Does it support IPv6?
0: (1): INFO: Listener address to use: 0.0.0.0
0: (1): INFO: log file opened: /var/tmp/turnserver_2026-07-31.log
0: (1): INFO: Listener address to use: ::
0: (1): INFO: Whitelisting external-ip private part: 172.16.227.1
0: (1): INFO: Relay address to use: 172.16.227.1
0: (1): INFO: Relay address to use: 2408:8249:4e01:2580:2e0:1bff:fe33:3098
0: (1): INFO: System cpu num is 2
0: (1): INFO: System enable num is 2
0: (1): INFO: Configured cpu num is 2
0: (1): INFO: Coturn Version Coturn-4.15.0 'Gorst'
0: (1): INFO: Max number of open files/sockets allowed for this process: 1048576
0: (1): INFO: Due to the open files/sockets limitation, max supported number of TURN Sessions possible is: 524000 (approximately)
0: (1): INFO:
==== Show him the instruments, Practical Frost: ====
0: (1): INFO: OpenSSL compile-time version: OpenSSL 3.5.6 7 Apr 2026 (0x30500060)
0: (1): INFO: TLS 1.2 supported
0: (1): INFO: TLS 1.3 supported
0: (1): INFO: DTLS 1.2 supported
0: (1): INFO: TURN/STUN ALPN supported
0: (1): INFO: Third-party authorization (oAuth) supported
0: (1): INFO: GCM (AEAD) supported
0: (1): INFO: SQLite supported, default database location is /var/lib/coturn/turndb
0: (1): INFO: Redis supported
0: (1): INFO: PostgreSQL supported
0: (1): INFO: MySQL supported
0: (1): INFO: MongoDB supported
0: (1): INFO: Net Engine: UDP thread per CPU core
0: (1): INFO: Domain name:
0: (1): INFO: Default realm: coturn.baidu.com
0: (1): INFO: Certificate file found: /etc/coturn/coturn.baidu.com.crt
0: (1): INFO: Private key file found: /etc/coturn/coturn.baidu.com.key
0: (1): INFO: TLS cipher suite: ALL:!COMPLEMENTOFDEFAULT:!eNULL:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256
0: (1): INFO: DTLS cipher suite: ALL:!COMPLEMENTOFDEFAULT:!eNULL:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256
0: (1): INFO: pid file created: /var/run/turnserver.pid
0: (1): INFO: IO method: epoll (with changelist)
0: (1): INFO: RFC5780 disabled! /NAT behavior discovery/
0: (1): INFO: Wait for relay ports initialization...
0: (1): INFO: relay 172.16.227.1 initialization...
0: (1): INFO: relay 172.16.227.1 initialization done
0: (1): INFO: relay 2408:8249:4e01:2580:2e0:1bff:fe33:3098 initialization...
0: (1): INFO: relay 2408:8249:4e01:2580:2e0:1bff:fe33:3098 initialization done
0: (1): INFO: Relay ports initialization done
0: (1): INFO: Total relay threads: 2
8: (10): INFO: IPv4. TLS/TCP listener opened on : 0.0.0.0:3478
8: (11): INFO: IPv4. TLS/TCP listener opened on : 0.0.0.0:3478
8: (10): INFO: IPv4. TLS/TCP listener opened on : 0.0.0.0:5349
8: (11): INFO: IPv4. TLS/TCP listener opened on : 0.0.0.0:5349
8: (10): INFO: IPv6. TLS/TCP listener opened on : :::3478
8: (11): INFO: IPv6. TLS/TCP listener opened on : :::3478
8: (10): INFO: IPv6. TLS/TCP listener opened on : :::5349
8: (11): INFO: IPv6. TLS/TCP listener opened on : :::5349
8: (1): INFO: IPv4. DTLS/UDP listener opened on: 0.0.0.0:3478
8: (1): INFO: IPv4. DTLS/UDP listener opened on: 0.0.0.0:5349
8: (1): INFO: IPv6. DTLS/UDP listener opened on: :::3478
8: (1): INFO: IPv6. DTLS/UDP listener opened on: :::5349
8: (1): INFO: Total auth threads: 2
8: (1): INFO: prometheus collector disabled, not started
27: (11): INFO: session 001000000000000001: realm <coturn.baidu.com> user <>: incoming packet message processed, error 401: Unauthorized
27: (10): INFO: IPv4. tcp or tls connected to: 172.16.227.254:19843
27: (10): INFO: session 000000000000000001: realm <coturn.baidu.com> user <>: incoming packet message processed, error 401: Unauthorized
27: (11): INFO: IPv4. Local relay addr: 172.16.227.1:61457
27: (11): INFO: session 001000000000000001: new, realm=<coturn.baidu.com>, username=<1785558815:@stephenjose_dai:chat.baidu.com>, lifetime=600
27: (11): DEBUG: Global turn allocation count incremented, now 1
27: (11): INFO: session 001000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet ALLOCATE processed, success
27: (10): INFO: IPv4. tcp or tls connected to: 172.16.227.254:37203
27: (10): INFO: IPv4. tcp or tls connected to: 172.16.227.254:37204
27: (10): INFO: IPv4. Local relay addr: 172.16.227.1:55319
27: (10): INFO: session 000000000000000001: new, realm=<coturn.baidu.com>, username=<1785558815:@stephenjose_dai:chat.baidu.com>, lifetime=600
27: (10): DEBUG: Global turn allocation count incremented, now 2
27: (10): INFO: session 000000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet ALLOCATE processed, success
27: (10): INFO: session 000000000000000002: TLS/TCP socket disconnected: 172.16.227.254:37203
27: (10): INFO: session 000000000000000002: usage: realm=<coturn.baidu.com>, username=<>, rp=0, rb=0, sp=0, sb=0
27: (10): INFO: session 000000000000000002: peer usage: realm=<coturn.baidu.com>, username=<>, rp=0, rb=0, sp=0, sb=0
27: (10): INFO: session 000000000000000002: closed (2nd stage), user <> realm <coturn.baidu.com> origin <>, local 0.0.0.0:5349, remote 172.16.227.254:37203, reason: TLS/TCP socket buffer operation error (callback)
27: (10): INFO: session 000000000000000003: TLS/TCP socket disconnected: 172.16.227.254:37204
27: (10): INFO: session 000000000000000003: usage: realm=<coturn.baidu.com>, username=<>, rp=0, rb=0, sp=0, sb=0
27: (10): INFO: session 000000000000000003: peer usage: realm=<coturn.baidu.com>, username=<>, rp=0, rb=0, sp=0, sb=0
27: (10): INFO: session 000000000000000003: closed (2nd stage), user <> realm <coturn.baidu.com> origin <>, local 0.0.0.0:5349, remote 172.16.227.254:37204, reason: TLS/TCP socket buffer operation error (callback)
32: (10): INFO: session 000000000000000004: realm <coturn.baidu.com> user <>: incoming packet message processed, error 401: Unauthorized
32: (10): INFO: IPv4. Local relay addr: 172.16.227.1:60463
32: (10): INFO: session 000000000000000004: new, realm=<coturn.baidu.com>, username=<1785558819:@ceshi:chat.baidu.com>, lifetime=600
32: (10): DEBUG: Global turn allocation count incremented, now 3
32: (10): INFO: session 000000000000000004: realm <coturn.baidu.com> user <1785558819:@ceshi:chat.baidu.com>: incoming packet ALLOCATE processed, success
32: (10): INFO: IPv4. tcp or tls connected to: 172.16.227.254:17950
32: (10): INFO: IPv4. tcp or tls connected to: 172.16.227.254:17949
32: (10): INFO: session 000000000000000006: realm <coturn.baidu.com> user <>: incoming packet message processed, error 401: Unauthorized
32: (10): INFO: IPv4. tcp or tls connected to: 172.16.227.254:17954
32: (10): INFO: session 000000000000000004: realm <coturn.baidu.com> user <1785558819:@ceshi:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
32: (10): INFO: session 000000000000000004: realm <coturn.baidu.com> user <1785558819:@ceshi:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
32: (10): INFO: IPv4. Local relay addr: 172.16.227.1:61890
32: (10): INFO: session 000000000000000006: new, realm=<coturn.baidu.com>, username=<1785558819:@ceshi:chat.baidu.com>, lifetime=600
32: (10): DEBUG: Global turn allocation count incremented, now 4
32: (10): INFO: session 000000000000000006: realm <coturn.baidu.com> user <1785558819:@ceshi:chat.baidu.com>: incoming packet ALLOCATE processed, success
32: (10): INFO: session 000000000000000005: TLS/TCP socket disconnected: 172.16.227.254:17950
32: (10): INFO: session 000000000000000005: usage: realm=<coturn.baidu.com>, username=<>, rp=0, rb=0, sp=0, sb=0
32: (10): INFO: session 000000000000000005: peer usage: realm=<coturn.baidu.com>, username=<>, rp=0, rb=0, sp=0, sb=0
32: (10): INFO: session 000000000000000005: closed (2nd stage), user <> realm <coturn.baidu.com> origin <>, local 0.0.0.0:5349, remote 172.16.227.254:17950, reason: TLS/TCP socket buffer operation error (callback)
32: (10): INFO: session 000000000000000006: realm <coturn.baidu.com> user <1785558819:@ceshi:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
32: (10): INFO: session 000000000000000006: realm <coturn.baidu.com> user <1785558819:@ceshi:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
32: (10): INFO: session 000000000000000007: TLS/TCP socket disconnected: 172.16.227.254:17954
32: (10): INFO: session 000000000000000007: usage: realm=<coturn.baidu.com>, username=<>, rp=0, rb=0, sp=0, sb=0
32: (10): INFO: session 000000000000000007: peer usage: realm=<coturn.baidu.com>, username=<>, rp=0, rb=0, sp=0, sb=0
32: (10): INFO: session 000000000000000007: closed (2nd stage), user <> realm <coturn.baidu.com> origin <>, local 0.0.0.0:5349, remote 172.16.227.254:17954, reason: TLS/TCP socket buffer operation error (callback)
33: (10): INFO: session 000000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
33: (10): INFO: session 000000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
33: (11): INFO: session 001000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
33: (11): INFO: session 001000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
33: (11): INFO: session 001000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
33: (11): INFO: session 001000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
33: (11): INFO: session 001000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
33: (11): INFO: session 001000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
33: (11): INFO: session 001000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
33: (11): INFO: session 001000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
33: (10): INFO: session 000000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
33: (10): INFO: session 000000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
33: (10): INFO: session 000000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
33: (10): INFO: session 000000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
33: (10): INFO: session 000000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
33: (10): INFO: session 000000000000000001: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
47: (10): INFO: session 000000000000000008: realm <coturn.baidu.com> user <>: incoming packet message processed, error 401: Unauthorized
47: (11): INFO: IPv4. tcp or tls connected to: 172.16.227.254:20505
47: (11): INFO: session 001000000000000002: realm <coturn.baidu.com> user <>: incoming packet message processed, error 401: Unauthorized
47: (11): INFO: IPv4. tcp or tls connected to: 172.16.227.254:20506
47: (11): INFO: IPv4. tcp or tls connected to: 172.16.227.254:20509
47: (10): INFO: IPv4. Local relay addr: 172.16.227.1:50498
47: (10): INFO: session 000000000000000008: new, realm=<coturn.baidu.com>, username=<1785558819:@ceshi:chat.baidu.com>, lifetime=600
47: (10): DEBUG: Global turn allocation count incremented, now 5
47: (10): INFO: session 000000000000000008: realm <coturn.baidu.com> user <1785558819:@ceshi:chat.baidu.com>: incoming packet ALLOCATE processed, success
47: (10): INFO: session 000000000000000008: realm <coturn.baidu.com> user <1785558819:@ceshi:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
47: (10): INFO: session 000000000000000008: realm <coturn.baidu.com> user <1785558819:@ceshi:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
47: (11): INFO: IPv4. Local relay addr: 172.16.227.1:58649
47: (11): INFO: session 001000000000000002: new, realm=<coturn.baidu.com>, username=<1785558819:@ceshi:chat.baidu.com>, lifetime=600
47: (11): DEBUG: Global turn allocation count incremented, now 6
47: (11): INFO: session 001000000000000002: realm <coturn.baidu.com> user <1785558819:@ceshi:chat.baidu.com>: incoming packet ALLOCATE processed, success
47: (11): INFO: session 001000000000000003: TLS/TCP socket disconnected: 172.16.227.254:20506
47: (11): INFO: session 001000000000000003: usage: realm=<coturn.baidu.com>, username=<>, rp=0, rb=0, sp=0, sb=0
47: (11): INFO: session 001000000000000003: peer usage: realm=<coturn.baidu.com>, username=<>, rp=0, rb=0, sp=0, sb=0
47: (11): INFO: session 001000000000000003: closed (2nd stage), user <> realm <coturn.baidu.com> origin <>, local 0.0.0.0:5349, remote 172.16.227.254:20506, reason: TLS/TCP socket buffer operation error (callback)
47: (11): INFO: session 001000000000000004: TLS/TCP socket disconnected: 172.16.227.254:20509
47: (11): INFO: session 001000000000000004: usage: realm=<coturn.baidu.com>, username=<>, rp=0, rb=0, sp=0, sb=0
47: (11): INFO: session 001000000000000004: peer usage: realm=<coturn.baidu.com>, username=<>, rp=0, rb=0, sp=0, sb=0
47: (11): INFO: session 001000000000000004: closed (2nd stage), user <> realm <coturn.baidu.com> origin <>, local 0.0.0.0:5349, remote 172.16.227.254:20509, reason: TLS/TCP socket buffer operation error (callback)
47: (11): INFO: session 001000000000000002: realm <coturn.baidu.com> user <1785558819:@ceshi:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
47: (11): INFO: session 001000000000000002: realm <coturn.baidu.com> user <1785558819:@ceshi:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
48: (11): INFO: session 001000000000000005: realm <coturn.baidu.com> user <>: incoming packet message processed, error 401: Unauthorized
48: (11): INFO: IPv4. tcp or tls connected to: 172.16.227.254:37205
48: (10): INFO: IPv4. tcp or tls connected to: 172.16.227.254:19844
48: (11): INFO: IPv4. tcp or tls connected to: 172.16.227.254:37206
48: (11): INFO: IPv4. Local relay addr: 172.16.227.1:57084
48: (11): INFO: session 001000000000000005: new, realm=<coturn.baidu.com>, username=<1785558815:@stephenjose_dai:chat.baidu.com>, lifetime=600
48: (11): DEBUG: Global turn allocation count incremented, now 7
48: (11): INFO: session 001000000000000005: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet ALLOCATE processed, success
48: (10): INFO: session 000000000000000009: realm <coturn.baidu.com> user <>: incoming packet message processed, error 401: Unauthorized
48: (11): INFO: session 001000000000000005: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
48: (11): INFO: session 001000000000000005: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
48: (11): INFO: session 001000000000000005: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
48: (11): INFO: session 001000000000000005: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
48: (11): INFO: session 001000000000000005: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
48: (11): INFO: session 001000000000000005: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
48: (11): INFO: session 001000000000000005: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
48: (11): INFO: session 001000000000000005: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
48: (10): INFO: IPv4. Local relay addr: 172.16.227.1:50902
48: (10): INFO: session 000000000000000009: new, realm=<coturn.baidu.com>, username=<1785558815:@stephenjose_dai:chat.baidu.com>, lifetime=600
48: (10): DEBUG: Global turn allocation count incremented, now 8
48: (10): INFO: session 000000000000000009: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet ALLOCATE processed, success
48: (11): INFO: session 001000000000000006: TLS/TCP socket disconnected: 172.16.227.254:37205
48: (11): INFO: session 001000000000000006: usage: realm=<coturn.baidu.com>, username=<>, rp=0, rb=0, sp=0, sb=0
48: (11): INFO: session 001000000000000006: peer usage: realm=<coturn.baidu.com>, username=<>, rp=0, rb=0, sp=0, sb=0
48: (11): INFO: session 001000000000000006: closed (2nd stage), user <> realm <coturn.baidu.com> origin <>, local 0.0.0.0:5349, remote 172.16.227.254:37205, reason: TLS/TCP socket buffer operation error (callback)
48: (10): INFO: session 000000000000000009: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet CREATE_PERMISSION processed, error 443: Peer Address Family Mismatch (4)
48: (10): INFO: session 000000000000000009: realm <coturn.baidu.com> user <1785558815:@stephenjose_dai:chat.baidu.com>: incoming packet message processed, error 443: Peer Address Family Mismatch (4)
48: (11): INFO: session 001000000000000007: TLS/TCP socket disconnected: 172.16.227.254:37206
48: (11): INFO: session 001000000000000007: usage: realm=<coturn.baidu.com>, username=<>, rp=0, rb=0, sp=0, sb=0
48: (11): INFO: session 001000000000000007: peer usage: realm=<coturn.baidu.com>, username=<>, rp=0, rb=0, sp=0, sb=0
48: (11): INFO: session 001000000000000007: closed (2nd stage), user <> realm <coturn.baidu.com> orSource: coturn/coturn