Steps to reproduce: 0. Gentoo??? 1. ??? Expected: No error Actual: Error prosodyctl check turn -v --ping=stun.conversations.im Identified 1 TURN services. Testing TURN service turn.example.com:3478... lua5.4: /usr/bin/prosodyctl:635: /usr/lib64/prosody/util/prosodyctl/check.lua:88: calling 'send' on bad self (udp{connected} expected) stack traceback: [C]: in method 'send' /usr/lib64/prosody/util/prosodyctl/check.lua:88: in upvalue 'check_turn_service' /usr/lib64/prosody/util/prosodyctl/check.lua:1286: in function 'util.prosodyctl.check.check' /usr/bin/prosodyctl:751: in upvalue 'func' /usr/lib64/prosody/util/async.lua:144: in function </usr/lib64/prosody/util/async.lua:142> stack traceback: [C]: in function 'error' /usr/bin/prosodyctl:635: in local 'handler' /usr/lib64/prosody/util/async.lua:232: in method 'run' /usr/bin/prosodyctl:754: in main chunk [C]: in ? Theories: Uncaught timeout or other socket error meets lack of error handling in this code. Prosody Version: 0.12.1

To be clear, we don't know how this happens. More details needed.

• tags Status-NeedInfo Milestone-0.12

https://hg.prosody.im/trunk/rev/836efad8483c will be in the next release and should hopefully get us more information.