coturn / coturn

coturn TURN server project
Other
11.42k stars 2.03k forks source link

coturn turn test works fine on firefox but fails with timeout error on chrome #1183

Open sherif2928 opened 1 year ago

sherif2928 commented 1 year ago

Hello there,

I think I have something wrong, but I don't know what it is. while using https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/ on Firefox everything works perfectly, but on chrome, edge or opera it gives me this: The server stun:stun.domain.name:5349 returned an error with code=701: STUN binding request timed out. The server turn:turn.domain.name:5349?transport=udp returned an error with code=701: TURN allocate request timed out.

when I tried to use it through my app it works only through the local lan network

and on the nat it doesn't work, and shows no errors at all the only error that appear is under one condition (in firefox console if the call was between pc firefox and android chrome) "WebRTC: ICE failed, see about:webrtc for more details"

I'm using ubuntu 22 plesk from the digitalocean's marketplace

have already ssl and a domain name

any help?

eakraly commented 1 year ago

Hi @sherif2928

Starting with Chrome 110 having transport=udp in STUN URL will fail validation You can still use it for TURN though (even though having transport=udp is not required as it is the default)

See PSA here https://groups.google.com/g/discuss-webrtc/c/L0qDWipd7VE/m/KKfmlY08AgAJ

sherif2928 commented 1 year ago

hello @eakraly thank you for your reply.

the issue is that in my app the call only happens properly if we're on the same network, but if we were on separate networks, it just never links, most of time without showing any errors.

that's why I thought that the issue may be caused by the TURN server configuration. And that's why I posted an issue here in first place seeking for help,

Govind10g commented 1 year ago

Hi @sherif2928 , Try to use this tool - https://icetest.info/

Btw in Chrome, Are you able to get "srflx" when testing STUN and "relay" while testing TURN ?

sherif2928 commented 1 year ago

Hello @Govind10g the tool gives me this

Results IceGatheringState: complete # # # #
host udp 091f32af-adbf-4b9d-9392-a3a63c55fdc7.local:55580 N/A
srflx udp my.pc.public.ip:45178 0.0.0.0:0
relay udp turn.server.ip:58979 my.pc.public.ip:45178
and about your second question, if u r talking about trickle ice on firefox, this is what I get: Time Type Foundation Protocol Address Port Priority URL (if present) relayProtocol (if present)
0.210 srflx 4 udp my.pc.public.ip 42519 100 - 32285 - 255
0.211 relay 5 udp turn.server.ip 49434 5 - 32285 - 255
0.215 srflx 4 udp my.pc.public.ip 42519 100 - 32287 - 255
0.262 srflx 4 udp my.pc.public.ip 42083 100 - 32285 - 254
0.263 relay 5 udp turn.server.ip 57858 5 - 32285 - 254

and it ends with no problems.

but in chrome it's like this: Time Type Foundation Protocol Address Port Priority URL (if present) relayProtocol (if present)
0.100 srflx 4216026645 udp my.pc.public.ip 44919 100 - 32286 - 255 stun:stun.my.stun/turn.domain:5349
0.212 relay 833366752 udp turn.server.ip 52989 2 - 32287 - 255 turn:turn.my.stun/turn.domain:5349?transport=udp udp

but on relay step it takes a lot of time and ends up with this error

Note: errors from onicecandidateerror above are not neccessarily fatal. For example an IPv6 DNS lookup may fail but relay candidates can still be gathered via IPv4.
The server stun:stun.my.stun/turn.domain:5349 returned an error with code=701:
STUN binding request timed out.
The server turn:stun.my.stun/turn.domain:5349?transport=udp returned an error with code=701:
TURN allocate request timed out.

The only thing I need to know is "Is my STUN/TURN server works properly that way?"

Govind10g commented 1 year ago

Hi @sherif2928 ,

I had seen this error in my case as well - The server stun:stun.domain.name:5349 returned an error with code=701: It is bug in that tool to throw such error info log.

But as per the above output I can say that your coturn is working. To further validate it, you can check the coturn log when you hit the Gather candidate button.

It will show the client IP address in the log if you used the turn and turns (tls). But for STUN, you will NOT get any logs in the log file.

@eakraly Sir, Any Idea why STUN method is not printing any logs in COTURN log file ?

sherif2928 commented 1 year ago

hello @Govind10g

I just figured out that my logging doesn't print any logs in log file after startup logs... on the other hand, when I try my turn/stun server credentials in my app, the audio/video only works in-between devices on the same server.

fippo commented 1 year ago

The only thing I need to know is "Is my STUN/TURN server works properly that way?"

Please read the note on the trickle-ice page:

Note: errors from onicecandidateerror above are not neccessarily fatal.
For example an IPv6 DNS lookup may fail but relay candidates can still be gathered via IPv4.

Your connection does not support IPv6 but you still get IPv4 candidates.

Firefox does not show any errors in that case since it is not an "error" and it doesn't support the API used for reporting this yet.

sherif2928 commented 1 year ago

hello @fippo

Actually NAT type is not the issue. It's not only on my PC, I've tried it from several countries - using friends' devices - and it still the same.

eakraly commented 1 year ago

@sherif2928 you can test the turnserver installation with turnutils_uclient

sherif2928 commented 1 year ago

Hello @eakraly Thanks for your reply.

https://drive.google.com/drive/folders/1qKzkGm7SjGqcQpeCv2Fh31---D7VmMCN

Here're 4 screenshots for my console testing my turnserver with turnutils_uclient on (TLS, DTLS, TCP and UDP)

Unfortunately, I couldn't understand what the output means but it was always ends up with "forbidden" as you can see in the screenshots.

Govind10g commented 1 year ago

@sherif2928 - Did you get any break through on this issue ?

sherif2928 commented 1 year ago

@Govind10g Unfortunately, no still stuck at this point with no progress since the last month I even put topics on reddit, Quora, and google groups but not a single response.

testpassword commented 1 year ago

@sherif2928 , hello. I have the same issue with coturn and chrome. Have you found a solution to the problem?

sherif2928 commented 1 year ago

@testpassword unfortunately no, had to use Jitsi at last after trying literally everything.

testpassword commented 1 year ago

@sherif2928 , that's sad. Thx for answering

docjojo commented 1 year ago

New ICE Test Tool https://icetest.atec-systems.com/

asvanberg commented 11 months ago

Still a problem in Chrome 119 and coturn 4.6.1

Attaching the verbose logs from the coturn server for a working Firefox test and a broken Chrome test

Coturn

Firefox

Trickle ICE output

Time Type Foundation Protocol Address Port Priority URL (if present) relayProtocol (if present)
0.001 host 0 udp 130.local.ip.0 58810 126 | 32512 | 255
0.001 host 3 udp 192.168.96.1 45167 126 | 32256 | 255
0.001 host 6 udp 172.17.0.1 53727 126 | 32000 | 255
0.001 host 9 tcp 130.local.ip.0 9 125 | 32704 | 255
0.001 host 10 tcp 192.168.96.1 9 125 | 32448 | 255
0.002 host 11 tcp 172.17.0.1 9 125 | 32192 | 255
0.002 host 0 udp 130.local.ip.0 46006 126 | 32512 | 254
0.002 host 3 udp 192.168.96.1 50249 126 | 32256 | 254
0.002 host 6 udp 172.17.0.1 40933 126 | 32000 | 254
0.002 host 9 tcp 130.local.ip.0 9 125 | 32704 | 254
0.003 host 10 tcp 192.168.96.1 9 125 | 32448 | 254
0.003 host 11 tcp 172.17.0.1 9 125 | 32192 | 254
0.005 relay 2 udp 130.turn.server.0 65021 5 | 32543 | 255
0.024 srflx 4 udp 130.local.ip.0 45167 100 | 32287 | 255
0.024 relay 5 udp 130.turn.server.0 53751 5 | 32287 | 255
0.048 srflx 7 udp 130.local.ip.0 53727 100 | 32031 | 255
0.048 relay 8 udp 130.turn.server.0 60181 5 | 32031 | 255
0.065 relay 2 udp 130.turn.server.0 54936 5 | 32543 | 254
0.084 srflx 4 udp 130.local.ip.0 50249 100 | 32287 | 254
0.084 relay 5 udp 130.turn.server.0 56246 5 | 32287 | 254
0.104 Done

The 172.17.0.1 is just a local Docker interface.

Logs from coturn

2023-11-27T10:12:38.781571+01:00 coturn-test turnserver: 384753: : session 051000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:12:38.783219+01:00 coturn-test turnserver: 384753: : IPv4. Local relay addr: 130.turn.server.0:65021
2023-11-27T10:12:38.783315+01:00 coturn-test turnserver: 384753: : session 051000000000000001: new, realm=<>, username=<alice:1701079935>, lifetime=3600
2023-11-27T10:12:38.783371+01:00 coturn-test turnserver: 384753: : session 051000000000000001: realm <> user <alice:1701079935>: incoming packet ALLOCATE processed, success
2023-11-27T10:12:38.800819+01:00 coturn-test turnserver: 384753: : session 125000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:12:38.803114+01:00 coturn-test turnserver: 384753: : IPv4. Local relay addr: 130.turn.server.0:53751
2023-11-27T10:12:38.803229+01:00 coturn-test turnserver: 384753: : session 125000000000000001: new, realm=<>, username=<alice:1701079935>, lifetime=3600
2023-11-27T10:12:38.803273+01:00 coturn-test turnserver: 384753: : session 125000000000000001: realm <> user <alice:1701079935>: incoming packet ALLOCATE processed, success
2023-11-27T10:12:38.821503+01:00 coturn-test turnserver: 384753: : session 067000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:12:38.823369+01:00 coturn-test turnserver[28400]: 193427: : session 019000000000000001: usage: realm=<>, username=<>, rp=1, rb=20, sp=1, sb=64
2023-11-27T10:12:38.823465+01:00 coturn-test turnserver[28400]: 193427: : session 019000000000000001: peer usage: realm=<>, username=<>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:38.823491+01:00 coturn-test turnserver[28400]: 193427: : session 019000000000000001: closed (2nd stage), user <> realm <> origin <>, local 130.turn.server.0:3478, remote 65.x.x.x:30274, reason: allocation watchdog determined stale session state
2023-11-27T10:12:38.823513+01:00 coturn-test turnserver[28400]: 238797: : session 058000000000000001: usage: realm=<>, username=<>, rp=1, rb=20, sp=1, sb=64
2023-11-27T10:12:38.823540+01:00 coturn-test turnserver[28400]: 238797: : session 058000000000000001: peer usage: realm=<>, username=<>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:38.823578+01:00 coturn-test turnserver[28400]: 238797: : session 058000000000000001: closed (2nd stage), user <> realm <> origin <>, local 130.turn.server.0:3478, remote 207.x.x.x:25835, reason: allocation watchdog determined stale session state
2023-11-27T10:12:38.823619+01:00 coturn-test turnserver[28400]: 279210: : session 105000000000000001: usage: realm=<>, username=<>, rp=1, rb=20, sp=1, sb=64
2023-11-27T10:12:38.823650+01:00 coturn-test turnserver[28400]: 279210: : session 105000000000000001: peer usage: realm=<>, username=<>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:38.823677+01:00 coturn-test turnserver[28400]: 279210: : session 105000000000000001: closed (2nd stage), user <> realm <> origin <>, local 130.turn.server.0:3478, remote 65.x.x.x:25616, reason: allocation watchdog determined stale session state
2023-11-27T10:12:38.823698+01:00 coturn-test turnserver[28400]: 301809: : session 080000000000000001: usage: realm=<>, username=<>, rp=1, rb=20, sp=1, sb=64
2023-11-27T10:12:38.823725+01:00 coturn-test turnserver[28400]: 301809: : session 080000000000000001: peer usage: realm=<>, username=<>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:38.823755+01:00 coturn-test turnserver[28400]: 301809: : session 080000000000000001: closed (2nd stage), user <> realm <> origin <>, local 130.turn.server.0:3478, remote 185.x.x.x:22458, reason: allocation watchdog determined stale session state
2023-11-27T10:12:38.823782+01:00 coturn-test turnserver[28400]: 335149: : IPv4. tcp or tls connected to: 79.x.x.x:51202
2023-11-27T10:12:38.823803+01:00 coturn-test turnserver[28400]: 335209: : session 050000000000000001: usage: realm=<>, username=<>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:38.823831+01:00 coturn-test turnserver[28400]: 335209: : session 050000000000000001: peer usage: realm=<>, username=<>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:38.823852+01:00 coturn-test turnserver[28400]: 335209: : session 050000000000000001: closed (2nd stage), user <> realm <> origin <>, local 130.turn.server.0:3478, remote 79.x.x.x:51202, reason: allocation watchdog determined stale session state
2023-11-27T10:12:38.823892+01:00 coturn-test turnserver: 384753: : IPv4. Local relay addr: 130.turn.server.0:60181
2023-11-27T10:12:38.823933+01:00 coturn-test turnserver[28400]: 357689: : IPv4. tcp or tls connected to: 104.x.x.x:49255
2023-11-27T10:12:38.823960+01:00 coturn-test turnserver[28400]: 357749: : session 076000000000000002: usage: realm=<>, username=<>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:38.823992+01:00 coturn-test turnserver[28400]: 357749: : session 076000000000000002: peer usage: realm=<>, username=<>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:38.824018+01:00 coturn-test turnserver[28400]: 357749: : session 076000000000000002: closed (2nd stage), user <> realm <> origin <>, local 130.turn.server.0:3478, remote 104.x.x.x:49255, reason: allocation watchdog determined stale session state
2023-11-27T10:12:38.824039+01:00 coturn-test turnserver[28400]: 360207: : session 055000000000000001: usage: realm=<>, username=<>, rp=1, rb=20, sp=1, sb=64
2023-11-27T10:12:38.824060+01:00 coturn-test turnserver[28400]: 360207: : session 055000000000000001: peer usage: realm=<>, username=<>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:38.824083+01:00 coturn-test turnserver[28400]: 360207: : session 055000000000000001: closed (2nd stage), user <> realm <> origin <>, local 130.turn.server.0:3478, remote 64.x.x.x:5855, reason: allocation watchdog determined stale session state
2023-11-27T10:12:38.824105+01:00 coturn-test turnserver[28400]: 365709: : session 011000000000000002: usage: realm=<>, username=<>, rp=1, rb=20, sp=1, sb=64
2023-11-27T10:12:38.824132+01:00 coturn-test turnserver[28400]: 365709: : session 011000000000000002: peer usage: realm=<>, username=<>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:38.824154+01:00 coturn-test turnserver[28400]: 365709: : session 011000000000000002: closed (2nd stage), user <> realm <> origin <>, local 130.turn.server.0:3478, remote 146.x.x.x:49701, reason: allocation watchdog determined stale session state
2023-11-27T10:12:38.824178+01:00 coturn-test turnserver[28400]: 384753: : session 051000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:12:38.824200+01:00 coturn-test turnserver[28400]: 384753: : IPv4. Local relay addr: 130.turn.server.0:65021
2023-11-27T10:12:38.824220+01:00 coturn-test turnserver[28400]: 384753: : session 051000000000000001: new, realm=<>, username=<alice:1701079935>, lifetime=3600
2023-11-27T10:12:38.824241+01:00 coturn-test turnserver[28400]: 384753: : session 051000000000000001: realm <> user <alice:1701079935>: incoming packet ALLOCATE processed, success
2023-11-27T10:12:38.824268+01:00 coturn-test turnserver[28400]: 384753: : session 125000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:12:38.824289+01:00 coturn-test turnserver[28400]: 384753: : IPv4. Local relay addr: 130.turn.server.0:53751
2023-11-27T10:12:38.824310+01:00 coturn-test turnserver[28400]: 384753: : session 125000000000000001: new, realm=<>, username=<alice:1701079935>, lifetime=3600
2023-11-27T10:12:38.824331+01:00 coturn-test turnserver[28400]: 384753: : session 125000000000000001: realm <> user <alice:1701079935>: incoming packet ALLOCATE processed, success
2023-11-27T10:12:38.824363+01:00 coturn-test turnserver[28400]: 384753: : session 067000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:12:38.825420+01:00 coturn-test turnserver: 384753: : session 067000000000000001: new, realm=<>, username=<alice:1701079935>, lifetime=3600
2023-11-27T10:12:38.825682+01:00 coturn-test turnserver: 384753: : session 067000000000000001: realm <> user <alice:1701079935>: incoming packet ALLOCATE processed, success
2023-11-27T10:12:38.840767+01:00 coturn-test turnserver: 384753: : session 117000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:12:38.842441+01:00 coturn-test turnserver: 384753: : IPv4. Local relay addr: 130.turn.server.0:54936
2023-11-27T10:12:38.842690+01:00 coturn-test turnserver: 384753: : session 117000000000000001: new, realm=<>, username=<alice:1701079935>, lifetime=3600
2023-11-27T10:12:38.842953+01:00 coturn-test turnserver: 384753: : session 117000000000000001: realm <> user <alice:1701079935>: incoming packet ALLOCATE processed, success
2023-11-27T10:12:38.861084+01:00 coturn-test turnserver: 384753: : session 006000000000000002: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:12:38.862506+01:00 coturn-test turnserver: 384753: : IPv4. Local relay addr: 130.turn.server.0:56246
2023-11-27T10:12:38.862778+01:00 coturn-test turnserver: 384753: : session 006000000000000002: new, realm=<>, username=<alice:1701079935>, lifetime=3600
2023-11-27T10:12:38.863003+01:00 coturn-test turnserver: 384753: : session 006000000000000002: realm <> user <alice:1701079935>: incoming packet ALLOCATE processed, success
2023-11-27T10:12:38.880491+01:00 coturn-test turnserver: 384753: : session 067000000000000002: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:12:38.881936+01:00 coturn-test turnserver: 384753: : IPv4. Local relay addr: 130.turn.server.0:59952
2023-11-27T10:12:38.882175+01:00 coturn-test turnserver: 384753: : session 067000000000000002: new, realm=<>, username=<alice:1701079935>, lifetime=3600
2023-11-27T10:12:38.882376+01:00 coturn-test turnserver: 384753: : session 067000000000000002: realm <> user <alice:1701079935>: incoming packet ALLOCATE processed, success
2023-11-27T10:12:38.884566+01:00 coturn-test turnserver: 384753: : session 067000000000000001: refreshed, realm=<>, username=<alice:1701079935>, lifetime=0
2023-11-27T10:12:38.884816+01:00 coturn-test turnserver: 384753: : session 051000000000000001: refreshed, realm=<>, username=<alice:1701079935>, lifetime=0
2023-11-27T10:12:38.885042+01:00 coturn-test turnserver: 384753: : session 051000000000000001: realm <> user <alice:1701079935>: incoming packet REFRESH processed, success
2023-11-27T10:12:38.885248+01:00 coturn-test turnserver: 384753: : session 125000000000000001: refreshed, realm=<>, username=<alice:1701079935>, lifetime=0
2023-11-27T10:12:38.885438+01:00 coturn-test turnserver: 384753: : session 125000000000000001: realm <> user <alice:1701079935>: incoming packet REFRESH processed, success
2023-11-27T10:12:38.885615+01:00 coturn-test turnserver: 384753: : session 117000000000000001: refreshed, realm=<>, username=<alice:1701079935>, lifetime=0
2023-11-27T10:12:38.885815+01:00 coturn-test turnserver: 384753: : session 117000000000000001: realm <> user <alice:1701079935>: incoming packet REFRESH processed, success
2023-11-27T10:12:38.886012+01:00 coturn-test turnserver: 384753: : session 006000000000000002: refreshed, realm=<>, username=<alice:1701079935>, lifetime=0
2023-11-27T10:12:38.886198+01:00 coturn-test turnserver: 384753: : session 006000000000000002: realm <> user <alice:1701079935>: incoming packet REFRESH processed, success
2023-11-27T10:12:38.886376+01:00 coturn-test turnserver: 384753: : session 067000000000000001: realm <> user <alice:1701079935>: incoming packet REFRESH processed, success
2023-11-27T10:12:38.886561+01:00 coturn-test turnserver: 384753: : session 067000000000000002: refreshed, realm=<>, username=<alice:1701079935>, lifetime=0
2023-11-27T10:12:38.886741+01:00 coturn-test turnserver: 384753: : session 067000000000000002: realm <> user <alice:1701079935>: incoming packet REFRESH processed, success
2023-11-27T10:12:39.884039+01:00 coturn-test turnserver: 384754: : session 006000000000000002: usage: realm=<>, username=<alice:1701079935>, rp=3, rb=260, sp=3, sb=288
2023-11-27T10:12:39.884595+01:00 coturn-test turnserver[28400]: 384753: : IPv4. Local relay addr: 130.turn.server.0:60181
2023-11-27T10:12:39.884856+01:00 coturn-test turnserver[28400]: 384753: : session 067000000000000001: new, realm=<>, username=<alice:1701079935>, lifetime=3600
2023-11-27T10:12:39.885047+01:00 coturn-test turnserver[28400]: 384753: : session 067000000000000001: realm <> user <alice:1701079935>: incoming packet ALLOCATE processed, success
2023-11-27T10:12:39.885252+01:00 coturn-test turnserver[28400]: 384753: : session 117000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:12:39.885447+01:00 coturn-test turnserver[28400]: 384753: : IPv4. Local relay addr: 130.turn.server.0:54936
2023-11-27T10:12:39.885675+01:00 coturn-test turnserver[28400]: 384753: : session 117000000000000001: new, realm=<>, username=<alice:1701079935>, lifetime=3600
2023-11-27T10:12:39.885941+01:00 coturn-test turnserver[28400]: 384753: : session 117000000000000001: realm <> user <alice:1701079935>: incoming packet ALLOCATE processed, success
2023-11-27T10:12:39.886132+01:00 coturn-test turnserver[28400]: 384753: : session 006000000000000002: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:12:39.886290+01:00 coturn-test turnserver[28400]: 384753: : IPv4. Local relay addr: 130.turn.server.0:56246
2023-11-27T10:12:39.886449+01:00 coturn-test turnserver[28400]: 384753: : session 006000000000000002: new, realm=<>, username=<alice:1701079935>, lifetime=3600
2023-11-27T10:12:39.886629+01:00 coturn-test turnserver[28400]: 384753: : session 006000000000000002: realm <> user <alice:1701079935>: incoming packet ALLOCATE processed, success
2023-11-27T10:12:39.886804+01:00 coturn-test turnserver[28400]: 384753: : session 067000000000000002: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:12:39.886957+01:00 coturn-test turnserver[28400]: 384753: : IPv4. Local relay addr: 130.turn.server.0:59952
2023-11-27T10:12:39.887137+01:00 coturn-test turnserver[28400]: 384753: : session 067000000000000002: new, realm=<>, username=<alice:1701079935>, lifetime=3600
2023-11-27T10:12:39.887297+01:00 coturn-test turnserver[28400]: 384753: : session 067000000000000002: realm <> user <alice:1701079935>: incoming packet ALLOCATE processed, success
2023-11-27T10:12:39.887487+01:00 coturn-test turnserver[28400]: 384753: : session 067000000000000001: refreshed, realm=<>, username=<alice:1701079935>, lifetime=0
2023-11-27T10:12:39.887709+01:00 coturn-test turnserver[28400]: 384753: : session 051000000000000001: refreshed, realm=<>, username=<alice:1701079935>, lifetime=0
2023-11-27T10:12:39.887908+01:00 coturn-test turnserver[28400]: 384753: : session 051000000000000001: realm <> user <alice:1701079935>: incoming packet REFRESH processed, success
2023-11-27T10:12:39.888063+01:00 coturn-test turnserver[28400]: 384753: : session 125000000000000001: refreshed, realm=<>, username=<alice:1701079935>, lifetime=0
2023-11-27T10:12:39.888229+01:00 coturn-test turnserver[28400]: 384753: : session 125000000000000001: realm <> user <alice:1701079935>: incoming packet REFRESH processed, success
2023-11-27T10:12:39.888381+01:00 coturn-test turnserver[28400]: 384753: : session 117000000000000001: refreshed, realm=<>, username=<alice:1701079935>, lifetime=0
2023-11-27T10:12:39.888589+01:00 coturn-test turnserver: 384754: : session 006000000000000002: peer usage: realm=<>, username=<alice:1701079935>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:39.888810+01:00 coturn-test turnserver[28400]: 384753: : session 117000000000000001: realm <> user <alice:1701079935>: incoming packet REFRESH processed, success
2023-11-27T10:12:39.889010+01:00 coturn-test turnserver[28400]: 384753: : session 006000000000000002: refreshed, realm=<>, username=<alice:1701079935>, lifetime=0
2023-11-27T10:12:39.889179+01:00 coturn-test turnserver[28400]: 384753: : session 006000000000000002: realm <> user <alice:1701079935>: incoming packet REFRESH processed, success
2023-11-27T10:12:39.889355+01:00 coturn-test turnserver[28400]: 384753: : session 067000000000000001: realm <> user <alice:1701079935>: incoming packet REFRESH processed, success
2023-11-27T10:12:39.889531+01:00 coturn-test turnserver[28400]: 384753: : session 067000000000000002: refreshed, realm=<>, username=<alice:1701079935>, lifetime=0
2023-11-27T10:12:39.889680+01:00 coturn-test turnserver[28400]: 384753: : session 067000000000000002: realm <> user <alice:1701079935>: incoming packet REFRESH processed, success
2023-11-27T10:12:39.889962+01:00 coturn-test turnserver[28400]: 384754: : session 006000000000000002: usage: realm=<>, username=<alice:1701079935>, rp=3, rb=260, sp=3, sb=288
2023-11-27T10:12:39.890130+01:00 coturn-test turnserver[28400]: 384754: : session 006000000000000002: peer usage: realm=<>, username=<alice:1701079935>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:39.890295+01:00 coturn-test turnserver[28400]: 384754: : session 006000000000000002: closed (2nd stage), user <alice:1701079935> realm <> origin <>, local 130.turn.server.0:3478, remote 130.x.x.x:50249, reason: allocation timeout
2023-11-27T10:12:39.890462+01:00 coturn-test turnserver[28400]: 384754: : session 006000000000000002: delete: realm=<>, username=<alice:1701079935>
2023-11-27T10:12:39.890629+01:00 coturn-test turnserver[28400]: 384754: : session 117000000000000001: usage: realm=<>, username=<alice:1701079935>, rp=3, rb=260, sp=3, sb=288
2023-11-27T10:12:39.890781+01:00 coturn-test turnserver[28400]: 384754: : session 117000000000000001: peer usage: realm=<>, username=<alice:1701079935>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:39.890933+01:00 coturn-test turnserver[28400]: 384754: : session 117000000000000001: closed (2nd stage), user <alice:1701079935> realm <> origin <>, local 130.turn.server.0:3478, remote 130.x.x.x:46006, reason: allocation timeout
2023-11-27T10:12:39.891106+01:00 coturn-test turnserver[28400]: 384754: : session 117000000000000001: delete: realm=<>, username=<alice:1701079935>
2023-11-27T10:12:39.891263+01:00 coturn-test turnserver[28400]: 384754: : session 125000000000000001: usage: realm=<>, username=<alice:1701079935>, rp=3, rb=260, sp=3, sb=288
2023-11-27T10:12:39.891403+01:00 coturn-test turnserver[28400]: 384754: : session 125000000000000001: peer usage: realm=<>, username=<alice:1701079935>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:39.891573+01:00 coturn-test turnserver[28400]: 384754: : session 125000000000000001: closed (2nd stage), user <alice:1701079935> realm <> origin <>, local 130.turn.server.0:3478, remote 130.x.x.x:45167, reason: allocation timeout
2023-11-27T10:12:39.891751+01:00 coturn-test turnserver: 384754: : session 006000000000000002: closed (2nd stage), user <alice:1701079935> realm <> origin <>, local 130.turn.server.0:3478, remote 130.x.x.x:50249, reason: allocation timeout
2023-11-27T10:12:39.891992+01:00 coturn-test turnserver: 384754: : session 006000000000000002: delete: realm=<>, username=<alice:1701079935>
2023-11-27T10:12:39.892216+01:00 coturn-test turnserver: 384754: : session 117000000000000001: usage: realm=<>, username=<alice:1701079935>, rp=3, rb=260, sp=3, sb=288
2023-11-27T10:12:39.892393+01:00 coturn-test turnserver: 384754: : session 117000000000000001: peer usage: realm=<>, username=<alice:1701079935>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:39.892576+01:00 coturn-test turnserver: 384754: : session 117000000000000001: closed (2nd stage), user <alice:1701079935> realm <> origin <>, local 130.turn.server.0:3478, remote 130.x.x.x:46006, reason: allocation timeout
2023-11-27T10:12:39.892830+01:00 coturn-test turnserver: 384754: : session 117000000000000001: delete: realm=<>, username=<alice:1701079935>
2023-11-27T10:12:39.893030+01:00 coturn-test turnserver: 384754: : session 125000000000000001: usage: realm=<>, username=<alice:1701079935>, rp=3, rb=260, sp=3, sb=288
2023-11-27T10:12:39.893244+01:00 coturn-test turnserver: 384754: : session 125000000000000001: peer usage: realm=<>, username=<alice:1701079935>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:39.893434+01:00 coturn-test turnserver: 384754: : session 125000000000000001: closed (2nd stage), user <alice:1701079935> realm <> origin <>, local 130.turn.server.0:3478, remote 130.x.x.x:45167, reason: allocation timeout
2023-11-27T10:12:39.893620+01:00 coturn-test turnserver: 384754: : session 125000000000000001: delete: realm=<>, username=<alice:1701079935>
2023-11-27T10:12:39.893797+01:00 coturn-test turnserver: 384754: : session 051000000000000001: usage: realm=<>, username=<alice:1701079935>, rp=3, rb=260, sp=3, sb=288
2023-11-27T10:12:39.893970+01:00 coturn-test turnserver: 384754: : session 051000000000000001: peer usage: realm=<>, username=<alice:1701079935>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:39.894219+01:00 coturn-test turnserver: 384754: : session 051000000000000001: closed (2nd stage), user <alice:1701079935> realm <> origin <>, local 130.turn.server.0:3478, remote 130.x.x.x:58810, reason: allocation timeout
2023-11-27T10:12:39.894407+01:00 coturn-test turnserver: 384754: : session 051000000000000001: delete: realm=<>, username=<alice:1701079935>
2023-11-27T10:12:39.894593+01:00 coturn-test turnserver: 384754: : session 067000000000000001: usage: realm=<>, username=<alice:1701079935>, rp=3, rb=260, sp=3, sb=288
2023-11-27T10:12:39.894759+01:00 coturn-test turnserver: 384754: : session 067000000000000001: peer usage: realm=<>, username=<alice:1701079935>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:39.894949+01:00 coturn-test turnserver: 384754: : session 067000000000000001: closed (2nd stage), user <alice:1701079935> realm <> origin <>, local 130.turn.server.0:3478, remote 130.x.x.x:53727, reason: allocation timeout
2023-11-27T10:12:39.895129+01:00 coturn-test turnserver: 384754: : session 067000000000000001: delete: realm=<>, username=<alice:1701079935>
2023-11-27T10:12:39.895331+01:00 coturn-test turnserver: 384754: : session 067000000000000002: usage: realm=<>, username=<alice:1701079935>, rp=3, rb=260, sp=3, sb=288
2023-11-27T10:12:39.895506+01:00 coturn-test turnserver: 384754: : session 067000000000000002: peer usage: realm=<>, username=<alice:1701079935>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:12:39.895689+01:00 coturn-test turnserver: 384754: : session 067000000000000002: closed (2nd stage), user <alice:1701079935> realm <> origin <>, local 130.turn.server.0:3478, remote 130.x.x.x:40933, reason: allocation timeout
2023-11-27T10:12:39.895877+01:00 coturn-test turnserver: 384754: : session 067000000000000002: delete: realm=<>, username=<alice:1701079935>

Lots of correctly authenticated requests which is in contrast to what Chrome outputs below.

Chrome

Trickle ICE output

Time Type Foundation Protocol Address Port Priority URL (if present) relayProtocol (if present)
0.005 host 1679026937 udp 192.168.151.200 64548 126 | 32542 | 255
0.126 host 2595831405 tcp 192.168.151.200 9 90 | 32542 | 255

The trickle ICE hangs at this point

Coturn logs

2023-11-27T10:20:08.458142+01:00 coturn-test turnserver: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.479600+01:00 coturn-test turnserver: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.525586+01:00 coturn-test turnserver: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.540775+01:00 coturn-test turnserver: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.567235+01:00 coturn-test turnserver: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.580773+01:00 coturn-test turnserver: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.618068+01:00 coturn-test turnserver: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.651206+01:00 coturn-test turnserver: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.683629+01:00 coturn-test turnserver: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.726035+01:00 coturn-test turnserver: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.762596+01:00 coturn-test turnserver: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.804321+01:00 coturn-test turnserver: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.825554+01:00 coturn-test turnserver: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.850202+01:00 coturn-test turnserver: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.872916+01:00 coturn-test turnserver[28400]: 385080: : session 048000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.873204+01:00 coturn-test turnserver[28400]: 385081: : session 048000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.873293+01:00 coturn-test turnserver[28400]: 385081: : session 048000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.873358+01:00 coturn-test turnserver[28400]: 385081: : session 085000000000000002: usage: realm=<>, username=<>, rp=18, rb=496, sp=18, sb=1696
2023-11-27T10:20:08.873422+01:00 coturn-test turnserver[28400]: 385081: : session 085000000000000002: peer usage: realm=<>, username=<>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:20:08.873485+01:00 coturn-test turnserver[28400]: 385081: : session 085000000000000002: closed (2nd stage), user <> realm <> origin <>, local 130.turn.server.0:3478, remote 192.x.x.x:56186, reason: allocation watchdog determined stale ses
sion state
2023-11-27T10:20:08.873555+01:00 coturn-test turnserver[28400]: 385081: : session 048000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.873618+01:00 coturn-test turnserver[28400]: 385081: : session 048000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.873678+01:00 coturn-test turnserver[28400]: 385081: : session 048000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.873738+01:00 coturn-test turnserver[28400]: 385081: : session 048000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.873796+01:00 coturn-test turnserver[28400]: 385081: : session 048000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.873855+01:00 coturn-test turnserver[28400]: 385081: : session 048000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.873928+01:00 coturn-test turnserver[28400]: 385081: : session 048000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.873989+01:00 coturn-test turnserver[28400]: 385081: : session 048000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.874048+01:00 coturn-test turnserver[28400]: 385096: : session 048000000000000001: usage: realm=<>, username=<>, rp=719, rb=20084, sp=719, sb=68832
2023-11-27T10:20:08.874111+01:00 coturn-test turnserver[28400]: 385096: : session 048000000000000001: peer usage: realm=<>, username=<>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:20:08.874191+01:00 coturn-test turnserver: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.874285+01:00 coturn-test turnserver[28400]: 385096: : session 048000000000000001: closed (2nd stage), user <> realm <> origin <>, local 130.turn.server.0:3478, remote 192.x.x.x:55466, reason: allocation watchdog determined stale session state
2023-11-27T10:20:08.874344+01:00 coturn-test turnserver[28400]: 385156: : session 048000000000000002: usage: realm=<>, username=<>, rp=6, rb=120, sp=6, sb=384
2023-11-27T10:20:08.874413+01:00 coturn-test turnserver[28400]: 385156: : session 048000000000000002: peer usage: realm=<>, username=<>, rp=0, rb=0, sp=0, sb=0
2023-11-27T10:20:08.874485+01:00 coturn-test turnserver[28400]: 385156: : session 048000000000000002: closed (2nd stage), user <> realm <> origin <>, local 130.turn.server.0:3478, remote 192.x.x.x:55466, reason: allocation watchdog determined stale session state
2023-11-27T10:20:08.874547+01:00 coturn-test turnserver[28400]: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.874613+01:00 coturn-test turnserver[28400]: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.874673+01:00 coturn-test turnserver[28400]: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
2023-11-27T10:20:08.874732+01:00 coturn-test turnserver[28400]: 385203: : session 009000000000000001: realm <> user <>: incoming packet message processed, error 401: Unauthorized
...

Every request comes in is unauthorized. A total of 1626 failed attempts are made.

OpenRelay from Metered

Using their free TURN server for testing there is at least one UDP relay coming up reliably from Chrome but Firefox lists a total of 5 relays and 2 srflex candidates so there's still some problems on the Chrome side. However since their server is protected with credentials it would appear that they are sent and parsed correctly between them and Chrome.

Hope this helps in diagnosing what goes wrong between Coturn and Chrome.