What steps will reproduce the problem?
1. On debian 13 trixie
2. Follow https://prosody.im/doc/turn and https://prosody.im/doc/coturn to configure prosody to use coturn
3. Run "prosodyctl check turn"
What is the expected output?
No errors.
What do you see instead?
Testing TURN service xxxxxxxxx:yyyy...
lua5.4: /usr/bin/prosodyctl:629: /usr/lib/prosody/net/stun.lua:191: packet truncated in attribute value
stack traceback:
[C]: in function 'assert'
/usr/lib/prosody/net/stun.lua:191: in function </usr/lib/prosody/net/stun.lua:174>
(...tail calls...)
/usr/lib/prosody/util/prosodyctl/check.lua:132: in upvalue 'check_turn_service'
/usr/lib/prosody/util/prosodyctl/check.lua:1476: in field '?'
/usr/lib/prosody/util/prosodyctl/check.lua:1825: in function 'prosody.util.prosodyctl.check.check'
/usr/bin/prosodyctl:745: in upvalue 'func'
/usr/lib/prosody/util/async.lua:149: in function </usr/lib/prosody/util/async.lua:147>
stack traceback:
[C]: in function 'error'
/usr/bin/prosodyctl:629: in local 'handler'
/usr/lib/prosody/util/async.lua:244: in method 'run'
/usr/bin/prosodyctl:748: in main chunk
[C]: in ?
What version of the product are you using? On what operating system?
Debian 13 trixie
prosody 13.0.1-1
coturn 4.6.1-2
Please provide any additional information below.
Using tcpdump I can see that coturn returns "Unauthorized".
Menel
on
Hi Viger, the traceback isn't nice and a better error would be better from the prosody side I think, but the cause eill be likely a misconfiguration of coturn or the prosody module. I'm on debian too snd don't have such an issue.
If you like join the prosody channel and we'll figure it out.
What steps will reproduce the problem? 1. On debian 13 trixie 2. Follow https://prosody.im/doc/turn and https://prosody.im/doc/coturn to configure prosody to use coturn 3. Run "prosodyctl check turn" What is the expected output? No errors. What do you see instead? Testing TURN service xxxxxxxxx:yyyy... lua5.4: /usr/bin/prosodyctl:629: /usr/lib/prosody/net/stun.lua:191: packet truncated in attribute value stack traceback: [C]: in function 'assert' /usr/lib/prosody/net/stun.lua:191: in function </usr/lib/prosody/net/stun.lua:174> (...tail calls...) /usr/lib/prosody/util/prosodyctl/check.lua:132: in upvalue 'check_turn_service' /usr/lib/prosody/util/prosodyctl/check.lua:1476: in field '?' /usr/lib/prosody/util/prosodyctl/check.lua:1825: in function 'prosody.util.prosodyctl.check.check' /usr/bin/prosodyctl:745: in upvalue 'func' /usr/lib/prosody/util/async.lua:149: in function </usr/lib/prosody/util/async.lua:147> stack traceback: [C]: in function 'error' /usr/bin/prosodyctl:629: in local 'handler' /usr/lib/prosody/util/async.lua:244: in method 'run' /usr/bin/prosodyctl:748: in main chunk [C]: in ? What version of the product are you using? On what operating system? Debian 13 trixie prosody 13.0.1-1 coturn 4.6.1-2 Please provide any additional information below. Using tcpdump I can see that coturn returns "Unauthorized".
Hi Viger, the traceback isn't nice and a better error would be better from the prosody side I think, but the cause eill be likely a misconfiguration of coturn or the prosody module. I'm on debian too snd don't have such an issue. If you like join the prosody channel and we'll figure it out.