Open rafaelarcanjo opened 2 years ago
We have the exact same issues here with similar log-events, also on build 6865. Really can't comprehend what's going on
Same here... Reverting back to stable-6826 helped to avoid the socket exceptions.
Same here. After reverting back to 6826 seems to work
There are two different exceptions in this report. I don't know why the cause of the first one, but it's in ICE/TCP code. ICE/TCP has been deprecated in favor of TURN/TLS and isn't supposed to be enabled.
Edit: @saghul just disabled ICE/TCP in #1223
The second exception is harmless. A recent change in ice4j exposed it in the logs, but it has been thrown for a long time. It happens when ice4j tries to send a packet through the udp/10000 socket before it has received a packet from a client. As soon as it receives a packet from the client the socket is initialized and subsequent attempts are successful. We don't have an easy fix for now, so just ignore it.
JVB 2022-02-04 18:34:12.717 WARNING: [77] [confId=ca204e259aaf0e3f gid=130129 stats_id=Jamaal-XxH conf_name=teste@muc.meet.jitsi ufrag=bfmv11fr2u6j6c epId=d870d9de local_ufrag=bfmv11fr2u6j6c] ConnectivityCheckClient.startCheckForPair#374: Failed to send BINDING-REQUEST(0x1)[attrib.count=6 len=92 tranID=0x6CEB03C67E0168AB38476DD9] jvb_1 | java.lang.IllegalArgumentException: No socket found for 172.22.0.5:4443/tcp->172.93.178.20:38288/tcp jvb_1 | at org.ice4j.stack.NetAccessManager.sendMessage(NetAccessManager.java:631) jvb_1 | at org.ice4j.stack.NetAccessManager.sendMessage(NetAccessManager.java:581) jvb_1 | at org.ice4j.stack.StunClientTransaction.sendRequest0(StunClientTransaction.java:267) jvb_1 | at org.ice4j.stack.StunClientTransaction.sendRequest(StunClientTransaction.java:245) jvb_1 | at org.ice4j.stack.StunStack.sendRequest(StunStack.java:680) jvb_1 | at org.ice4j.ice.ConnectivityCheckClient.startCheckForPair(ConnectivityCheckClient.java:335) jvb_1 | at org.ice4j.ice.Agent$StunKeepAliveRunner.sendKeepAlive(Agent.java:2693) jvb_1 | at org.ice4j.ice.Agent$StunKeepAliveRunner.run(Agent.java:2671) jvb_1 | at org.ice4j.util.PeriodicRunnable.executeRun(PeriodicRunnable.java:206) jvb_1 | at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) jvb_1 | at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) jvb_1 | at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) jvb_1 | at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) jvb_1 | at java.base/java.lang.Thread.run(Thread.java:829)
Thanks Boris!
Ok, thank you. Then I will wait until the new release.
Hi,
I applied the changes described there https://github.com/jitsi/docker-jitsi-meet/pull/1223 and downgrade to version stable-6826 but the problems continued :(
@rafaelarcanjo You mean the unstable connection? I had this also some time ago. Couldn't find out what caused this issue. But I solved it by disabling P2P connections.
Simply add
ENABLE_P2P=false
to the .env
file.
@mammo0 Thanks! We will test.
@mammo0 same problem :(
OK, it was worth a try. But unfortunately I can't help you any further.
I have the same issue. It is the one wi-fi, and PC dropped connection, but mobile does not. Downgrade to 6826 does not solve the problem. jitsi run from docker-compose.yaml, 10000 expose without NAT.
Hi,
In 7210 release also exist this problem. Anybody found a solution for this?
Had the same issue, upgraded to 7287 and it seems fine so far
nope...
any solution for this?
Have you updated to the latest version?
no, not yet. is latest versiyon fixes this issue? if fixes, i missed the point
We don't see this problem in our testing.
There are too many moving parts here, so generally, being on the latest stable is the best option.
Hello Jitsi Community,
it’s my first message. I install an Jitsi-Meet to an Debian with Docker. The installation was fine and the web interface is also functional. It’s possible to meet with other participants in the session, but the connection will be closed after 5-30 minutes. In the jvb.log is something like: "[101] org.ice4j.stack.Connector.run: Connector died".
Log JVB:
docker-compose.yaml:
.env
NGINX config:
NAT for the ports 4443/tcp and 10000-20000/udp.
Any help would be appreciated!
Thanks