search

coturn / coturn

coturn TURN server project
Other
11.37k stars 2.02k forks source link

How to solve this error? #1573

Open udhayNuk opened 1 month ago

udhayNuk commented 1 month ago

i have configured the turnserver with listening-ip=0.0.0.0 relay-ip=0.0.0.0 listening-port=5349 tls-listening-port=5349

fingerprint min-port=49152 max-port=65535 no-loopback-peers no-multicast-peers total-quota=100 stale-nonce lt-cred-mech user=ridsys:ridsys no-tls no-dtls

realm=182.79.216.106 no-cli server-name=ipcamturnserver max-bps=0

please solve this relay mode is not working @misi

session 006000000000000003: realm <182.79.216.106> user : incoming packet BINDING processed, success 188: handle_udp_packet: New UDP endpoint: local addr 0.0.0.0:5349, remote addr 103.183.46.180:35027 188: session 017000000000000009: realm <182.79.216.106> user <>: incoming packet BINDING processed, success 188: handle_udp_packet: New UDP endpoint: local addr 0.0.0.0:5349, remote addr 103.183.46.180:51542 188: session 034000000000000005: realm <182.79.216.106> user <>: incoming packet message processed, error 401: Unauthorized 188: handle_udp_packet: New UDP endpoint: local addr 0.0.0.0:5349, remote addr 103.183.46.180:53933 188: handle_udp_packet: New UDP endpoint: local addr 0.0.0.0:5349, remote addr 103.183.46.180:36810 188: session 005000000000000002: realm <182.79.216.106> user <>: incoming packet BINDING processed, success 188: session 004000000000000003: realm <182.79.216.106> user <>: incoming packet BINDING processed, success 188: handle_udp_packet: New UDP endpoint: local addr 0.0.0.0:5349, remote addr 103.183.46.180:57480 188: handle_udp_packet: New UDP endpoint: local addr 0.0.0.0:5349, remote addr 103.183.46.180:40166 188: session 036000000000000009: realm <182.79.216.106> user <>: incoming packet message processed, error 401: Unauthorized 188: session 027000000000000004: realm <182.79.216.106> user <>: incoming packet message processed, error 401: Unauthorized 189: session 024000000000000002: usage: realm=<182.79.216.106>, username=<>, rp=7, rb=252, sp=7, sb=840 189: session 031000000000000002: usage: realm=<182.79.216.106>, username=<>, rp=1, rb=20, sp=1, sb=96 189: session 019000000000000006: usage: realm=<182.79.216.106>, username=<>, rp=1, rb=20, sp=1, sb=96 189: session 024000000000000002: closed (2nd stage), user <> realm <182.79.216.106> origin <>, local 0.0.0.0:5349, remote 103.183.46.180:45057, reason: allocation watchdog determined stale session state 189: session 028000000000000001: usage: realm=<182.79.216.106>, username=<>, rp=7, rb=252, sp=7, sb=840 189: session 019000000000000006: closed (2nd stage), user <> realm <182.79.216.106> origin <>, local 0.0.0.0:5349, remote 103.183.46.180:50552, reason: allocation watchdog determined stale session state 189: session 031000000000000002: closed (2nd stage), user <> realm <182.79.216.106> origin <>, local 0.0.0.0:5349, remote 103.183.46.180:33401, reason: allocation watchdog determined stale session state 189: session 028000000000000001: closed (2nd stage), user <> realm <182.79.216.106> origin <>, local 0.0.0.0:5349, remote 103.183.46.180:40769, reason: allocation watchdog determined stale session state 189: session 037000000000000001: usage: realm=<182.79.216.106>, username=<>, rp=7, rb=252, sp=7, sb=840 189: session 037000000000000001: closed (2nd stage), user <> realm <182.79.216.106> origin <>, local 0.0.0.0:5349, remote 103.183.46.180:39108, reason: allocation watchdog determined stale session state 189: session 016000000000000001: usage: realm=<182.79.216.106>, username=<>, rp=1, rb=20, sp=1, sb=96 189: session 016000000000000001: closed (2nd stage), user <> realm <182.79.216.106> origin <>, local 0.0.0.0:5349, remote 103.183.46.180:43865, reason: allocation watchdog determined stale session state 189: session 034000000000000005: realm <182.79.216.106> user <>: incoming packet message processed, error 401: Unauthorized 189: session 036000000000000009: realm <182.79.216.106> user <>: incoming packet message processed, error 401: Unauthorized 189: session 027000000000000004: realm <182.79.216.106> user <>: incoming packet message processed, error 401: Unauthorized 189: session 034000000000000005: realm <182.79.216.106> user <>: incoming packet message processed, error 401: Unauthorized 189: session 036000000000000009: realm <182.79.216.106> user <>: incoming packet message processed, error 401: Unauthorized 189: session 027000000000000004: realm <182.79.216.106> user <>: incoming packet message processed, error 401: Unauthorized 190: session 034000000000000005: realm <182.79.216.106> user <>: incoming packet message processed, error 401: Unauthorized 190: session 027000000000000004: realm <182.79.216.106> user <>: incoming packet message processed, error 401: Unauthorized 190: session 036000000000000009: realm <182.79.216.106> user <>: incoming packet message processed, error 401: Unauthorized 190: session 033000000000000002: usage: realm=<182.79.216.106>, username=<>, rp=7, rb=252, sp=7, sb=840 190: session 016000000000000002: usage: realm=<182.79.216.106>, username=<>, rp=1, rb=20, sp=1, sb=96 190: session 033000000000000002: closed (2nd stage), user <> realm <182.79.216.106> origin <>, local 0.0.0.0:5349, remote 103.183.46.200:57200, reason: allocation watchdog determined stale session state 190: session 016000000000000002: closed (2nd stage), user <> realm <182.79.216.106> origin <>, local 0.0.0.0:5349, remote 103.183.46.200:57202, reason: allocation watchdog determined stale session state 190: session 018000000000000001: usage: realm=<182.79.216.106>, username=<>, rp=1, rb=20, sp=1, sb=96 190: session 018000000000000001: closed (2nd stage), user <> realm <182.79.216.106> origin <>, local 0.0.0.0:5349, remote 103.183.46.200:57207, reason: allocation watchdog determined stale session state 190: session 028000000000000002: usage: realm=<182.79.216.106>, username=<>, rp=7, rb=252, sp=7, sb=840 190: session 028000000000000002: closed (2nd stage), user <> realm <182.79.216.106> origin <>, local 0.0.0.0:5349, remote 103.183.46.200:57205, reason: allocation watchdog determined stale session state 190: handle_udp_packet: New UDP endpoint: local addr 0.0.0.0:5349, remote addr 103.183.46.200:56088 190: session 005000000000000003: realm <182.79.216.106> user <>: incoming packet message processed, error 401: Unauthorized 190: handle_udp_packet: New UDP endpoint: local addr 0.0.0.0:5349, remote addr 103.183.46.200:56091 190: handle_udp_packet: New UDP endpoint: local addr 0.0.0.0:5349, remote addr 103.183.46.200:56090 190: session 019000000000000010: realm <182.79.216.106> user <>: incoming packet BINDING processed, success 190: session 015000000000000005: realm <182.79.216.106> user <>: incoming packet BINDING processed, success 190: session 025000000000000002: usage: realm=<182.79.216.106>, username=<>, rp=14, rb=504, sp=14, sb=1680 190: session 025000000000000002: closed (2nd stage), user <> realm <182.79.216.106> origin <>, local 0.0.0.0:5349, remote 103.183.46.200:57210, reason: allocation watchdog determined stale session state 190: handle_udp_packet: New UDP endpoint: local addr 0.0.0.0:5349, remote addr 103.183.46.200:59449 190: handle_udp_packet: New UDP endpoint: local addr 0.0.0.0:5349, remote addr 103.183.46.200:59450 190: session 025000000000000004: realm <182.79.216.106> user <>: incoming packet message processed, error 401: Unauthorized 190: handle_udp_packet: New UDP endpoint: local addr 0.0.0.0:5349, remote addr 103.183.46.200:59452 190: session 027000000000000005: realm <182.79.216.106> user <>: incoming packet message processed, error 401: Unauthorized 190: session 019000000000000011: realm <182.79.216.106> user <>: incoming packet BINDING processed, success 190: session 020000000000000001: usage: realm=<182.79.216.106>, username=<>, rp=1, rb=20, sp=1, sb=96 190: session 020000000000000001: closed (2nd stage), user <> realm <182.79.216.106> origin <>, local 0.0.0.0:5349, remote 103.183.46.200:57212, reason: allocation watchdog determined stale session state 191: session 005000000000000003: realm <182.79.216.106> user <>: incoming packet message processed, error 401: Unauthorized

GuenKainto commented 3 weeks ago

i have error 401: Unauthorized when call in different network too. I tried adding a relay to the config turn, but when creating a peer connection, I couldn't find any ice with the type "relay"

eakraly commented 3 weeks ago

It looks like your credentials do not match

Also, I suggest not using listening-ip=0.0.0.0 relay-ip=0.0.0.0 - you can just omit this config option or leave it empty