Error set remote description when use stun #304
Comments
|
Actually the error is really related to this fix: [0] [1] error Error set remote description {
[0] [1] e: 'The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received undefined',
[0] [1] stack: 'TypeError [ERR_INVALID_ARG_TYPE]: The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received undefined\n' +
[0] [1] ' at new NodeError (node:internal/errors:372:5)\n' +
[0] [1] ' at Function.from (node:buffer:323:9)\n' +
[0] [1] ' at packString (/home/user/Projects/werift-sfu-react/node_modules/werift/lib/ice/src/stun/attributes.js:111:38)\n' +
[0] [1] ' at Message.get bytes [as bytes] (/home/user/Projects/werift-sfu-react/node_modules/werift/lib/ice/src/stun/message.js:77:19)\n' +
[0] [1] ' at Message.messageIntegrity (/home/user/Projects/werift-sfu-react/node_modules/werift/lib/ice/src/stun/message.js:99:46)\n' +
[0] [1] ' at Message.addMessageIntegrity (/home/user/Projects/werift-sfu-react/node_modules/werift/lib/ice/src/stun/message.js:95:53)\n' +
[0] [1] ' at TurnClient.request (/home/user/Projects/werift-sfu-react/node_modules/werift/lib/ice/src/turn/protocol.js:181:18)\n' +
[0] [1] ' at TurnClient.connect (/home/user/Projects/werift-sfu-react/node_modules/werift/lib/ice/src/turn/protocol.js:154:39)\n' +
[0] [1] ' at async createTurnEndpoint (/home/user/Projects/werift-sfu-react/node_modules/werift/lib/ice/src/turn/protocol.js:232:5)\n' +
[0] [1] ' at async Connection.getComponentCandidates (/home/user/Projects/werift-sfu-react/node_modules/werift/lib/ice/src/ice.js:284:30)',
[0] [1] }
|
That is, if you fix it as in the PR, then the error described above appears |
|
It seems that something is starting to clear up, I output it to the console from this file getAttributeValue(key) {
const attribute = this.attributes.find((a) => a[0] === key);
if (!attribute) {
console.log(key, this.attributes);
return undefined;
}
return attribute[1];
}And I see that an exception is thrown due to an error in the message: DATA [
[
'ERROR-CODE',
[ 437, 'Mismatched allocation: wrong transaction ID\x00' ]
],
[ 'SOFTWARE', "Coturn-4.5.2 'dan Eider'" ],
[ 'FINGERPRINT', 4171264430 ]
]
NONCE [
[
'ERROR-CODE',
[ 437, 'Mismatched allocation: wrong transaction ID\x00' ]
],
[ 'SOFTWARE', "Coturn-4.5.2 'dan Eider'" ],
[ 'FINGERPRINT', 4171264430 ]
]
REALM [
[
'ERROR-CODE',
[ 437, 'Mismatched allocation: wrong transaction ID\x00' ]
],
[ 'SOFTWARE', "Coturn-4.5.2 'dan Eider'" ],
[ 'FINGERPRINT', 4171264430 ]
]
error Error set remote description {
e: 'The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received undefined',
stack: 'TypeError [ERR_INVALID_ARG_TYPE]: The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received undefined\n' +
' at new NodeError (node:internal/errors:387:5)\n' +
' at Function.from (node:buffer:328:9)\n' +
' at packString (/usr/local/share/applications/werift-sfu-react/node_modules/werift/lib/ice/src/stun/attributes.js:111:38)\n' +
' at Message.get bytes [as bytes] (/usr/local/share/applications/werift-sfu-react/node_modules/werift/lib/ice/src/stun/message.js:77:19)\n' +
' at Message.messageIntegrity (/usr/local/share/applications/werift-sfu-react/node_modules/werift/lib/ice/src/stun/message.js:99:46)\n' +
' at Message.addMessageIntegrity (/usr/local/share/applications/werift-sfu-react/node_modules/werift/lib/ice/src/stun/message.js:95:53)\n' +
' at TurnClient.request (/usr/local/share/applications/werift-sfu-react/node_modules/werift/lib/ice/src/turn/protocol.js:181:18)\n' +
' at TurnClient.connect (/usr/local/share/applications/werift-sfu-react/node_modules/werift/lib/ice/src/turn/protocol.js:154:39)\n' +
' at processTicksAndRejections (node:internal/process/task_queues:96:5)\n' +
' at async createTurnEndpoint (/usr/local/share/applications/werift-sfu-react/node_modules/werift/lib/ice/src/turn/protocol.js:232:5)',
roomId: '1667350895708',
userId: '1',
target: 0,
connId: 'b0aa26d5-9f5e-493c-a5e5-257bf7b2b6a1',
peerId: '1_0_b0aa26d5-9f5e-493c-a5e5-257bf7b2b6a1',
peers: undefined,
is: 'new',
cs: 'new',
ss: 'stable'
}
warn Skipping set local description for answer {
error: true,
roomId: '1667350895708',
userId: '1',
target: 0,
connId: 'b0aa26d5-9f5e-493c-a5e5-257bf7b2b6a1',
peerId: '1_0_b0aa26d5-9f5e-493c-a5e5-257bf7b2b6a1',
peers: undefined,
is: 'new',
cs: 'new',
ss: 'stable',
sendersLength: 2
}
DATA [
[
'ERROR-CODE',
[ 437, 'Mismatched allocation: wrong transaction ID\x00' ]
],
[ 'SOFTWARE', "Coturn-4.5.2 'dan Eider'" ],
[ 'FINGERPRINT', 1518249910 ]
]
NONCE [
[
'ERROR-CODE',
[ 437, 'Mismatched allocation: wrong transaction ID\x00' ]
],
[ 'SOFTWARE', "Coturn-4.5.2 'dan Eider'" ],
[ 'FINGERPRINT', 1518249910 ]
]
REALM [
[
'ERROR-CODE',
[ 437, 'Mismatched allocation: wrong transaction ID\x00' ]
],
[ 'SOFTWARE', "Coturn-4.5.2 'dan Eider'" ],
[ 'FINGERPRINT', 1518249910 ]
]
Most likely, you need to process this error, as well as find out and, if possible, eliminate its cause. @shinyoshiaki Do you have any thoughts on this? |
|
I checked this issue coturn/coturn#267 , it did not fit. Since my error happens even when the firewall is turned off. |
|
Here's what I was able to find out. First, when everything is working fine, i.e. when there is no 437 error and the connections work as expected, then DATA [
[ 'ERROR-CODE', [ 401, 'Unauthorized' ] ],
[ 'NONCE', <Buffer 39 32 66 35 37 35 62 37 61 38 64 35 30 39 39 62> ],
[ 'REALM', 'uyem.ru' ],
[ 'SOFTWARE', "Coturn-4.5.2 'dan Eider'" ],
[ 'FINGERPRINT', 3705723979 ]
] 92f575b7a8d5099b
DATA [
[ 'ERROR-CODE', [ 401, 'Unauthorized' ] ],
[ 'NONCE', <Buffer 39 66 32 37 37 62 65 31 62 31 64 31 37 32 34 35> ],
[ 'REALM', 'uyem.ru' ],
[ 'SOFTWARE', "Coturn-4.5.2 'dan Eider'" ],
[ 'FINGERPRINT', 3961840218 ]
] 9f277be1b1d17245
DATA [
[ 'XOR-RELAYED-ADDRESS', [ '176.124.206.161', 57030 ] ],
[ 'XOR-MAPPED-ADDRESS', [ '127.0.0.1', 20007 ] ],
[ 'LIFETIME', 600 ],
[ 'SOFTWARE', "Coturn-4.5.2 'dan Eider'" ],
[
'MESSAGE-INTEGRITY',
<Buffer e2 44 b8 7a c2 b7 99 58 4c 90 5b 8c bc d7 7f 63 d6 d4 63 d8>
],
[ 'FINGERPRINT', 3672353448 ]
] 127.0.0.1,20007
DATA [
[ 'XOR-RELAYED-ADDRESS', [ '176.124.206.161', 54211 ] ],
[ 'XOR-MAPPED-ADDRESS', [ '127.0.0.1', 20008 ] ],
[ 'LIFETIME', 600 ],
[ 'SOFTWARE', "Coturn-4.5.2 'dan Eider'" ],
[
'MESSAGE-INTEGRITY',
<Buffer 67 7b b2 33 4d 13 44 fd 1e f4 38 fb e1 91 81 75 99 21 93 9d>
],
[ 'FINGERPRINT', 729170023 ]
] 127.0.0.1,20008
DATA [
[ 'SOFTWARE', "Coturn-4.5.2 'dan Eider'" ],
[
'MESSAGE-INTEGRITY',
<Buffer 46 9a 8d 7b 6f 89 0f eb 03 05 b5 92 b3 f9 d3 a3 bb c2 9e e8>
],
[ 'FINGERPRINT', 3316151783 ]
] F��{o������ӣ�'SOFTWARE', "Coturn-4.5.2 'dan Eider'" ],
[
'MESSAGE-INTEGRITY',
<Buffer 85 c3 3b e4 bd 62 44 19 13 9d 7d 83 6c c7 a1 5a c3 31 cf af>
],
[ 'FINGERPRINT', 3522850246 ]
] ��;�bD�}�lǡZ�1ϯIt doesn't bother me too much, since the connections still work fine. But I'm sharing it here anyway just in case this behavior could be indicative of The main thing I noticed today is that after rebooting coturn everything works fine. But as soon as I restart my app and run the tests, I get a 437 error every time until I restart coturn again. On a freshly restarted coturn everything works fine until I restart my application again. I will appreciate any of your help. |
The reason for this behavior seems to be that Based on logic, I want to assume that the problem can only be in the work of the I don’t have a simple example of how to reproduce the problem, I can only make a description of the launch of my application on which I observe this problem https://github.com/kolserdav/werift-sfu-react , but there you will need to configure the connection to the database, I think that you have there will be no time for this action. However, if your configuration is something like this https://github.com/kolserdav/werift-sfu-react/blob/master/docs/resources/coturn.conf , then you can try to pass |
|
Based on this answer coturn/coturn#1138 (comment) . It can be concluded that error 437 can be thrown by the turn server within 600 seconds after restarting applications running on |
|
@kolserdav i have the same issue with werift, for now my temp fix is // comment this while loop
while (run) {
// refresh before expire
await setTimeout((5 / 6) * this.lifetime * 1000);
const request = new Message(methods.REFRESH, classes.REQUEST);
request.setAttribute("LIFETIME", this.lifetime);
await this.request(request, this.server);
} |
|
@kolserdav UPDATE on the issue so if don't use our own coturn turn on SFU server side, no more issues. |
@Codefa you are right, thank you. |
When working through a stun, a critical error often occurs that prevents a connection from being established:
The top line of the stack refers to this line:
werift-webrtc/packages/ice/src/stun/message.ts
Line 120 in f916e89
I figured out that undefined is the value of the
NONCEattribute. While at other times it is a normal numerical value.I have a hunch that
getAttributeValueis being called there withthis.attributesalready changed, but I don't have enough experience withweriftyet to check that.The text was updated successfully, but these errors were encountered: