Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

org.bouncycastle.tls.TlsFatalAlert: internal_error(80) #1955

Open
liangguohao66 opened this issue Jan 1, 2025 · 1 comment
Open

org.bouncycastle.tls.TlsFatalAlert: internal_error(80) #1955

liangguohao66 opened this issue Jan 1, 2025 · 1 comment

Comments

@liangguohao66
Copy link

when I run jitsi-meet on debian12 system, the dtls negotiation failed . is there any tool to check the cause of the error?

openssl version

OpenSSL 3.0.15 3 Sep 2024 (Library: OpenSSL 3.0.15 3 Sep 2024)

JVB 2024-12-31 09:27:32.455 SEVERE: [107] [confId=7385f3f5c75d0150 conf_name=[email protected] meeting_id=764f6f8e epId=431019ef stats_id=Kenya-QG5 local_ufrag=cdaam1igehqn00] IceTransport.send#272: Error sending packet
java.io.IOException: No socket found to send on.
at org.ice4j.ice.Component.send(Component.java:1227)
at org.jitsi.videobridge.transport.ice.IceTransport.send(IceTransport.kt:269)
at org.jitsi.videobridge.Endpoint$setupDtlsTransport$2.sendData(Endpoint.kt:461)
at org.jitsi.videobridge.transport.dtls.DtlsTransport$dtlsStack$1$2.sendData(DtlsTransport.kt:106)
at org.jitsi.nlj.dtls.DtlsStack$DatagramTransportImpl.send(DtlsStack.kt:291)
at org.bouncycastle.tls.DTLSRecordLayer.sendDatagram(Unknown Source)
at org.bouncycastle.tls.DTLSRecordLayer.sendRecord(Unknown Source)
at org.bouncycastle.tls.DTLSRecordLayer.raiseAlert(Unknown Source)
at org.bouncycastle.tls.DTLSRecordLayer.fail(Unknown Source)
at org.bouncycastle.tls.DTLSServerProtocol.abortServerHandshake(Unknown Source)
at org.bouncycastle.tls.DTLSServerProtocol.accept(Unknown Source)
at org.bouncycastle.tls.DTLSServerProtocol.accept(Unknown Source)
at org.jitsi.nlj.dtls.DtlsServer.accept(DtlsServer.kt:45)
at org.jitsi.nlj.dtls.DtlsServer.start(DtlsServer.kt:41)
at org.jitsi.nlj.dtls.DtlsStack.start(DtlsStack.kt:151)
at org.jitsi.videobridge.transport.dtls.DtlsTransport.startDtlsHandshake(DtlsTransport.kt:137)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
JVB 2024-12-31 09:27:32.456 SEVERE: [107] [confId=7385f3f5c75d0150 conf_name=[email protected] meeting_id=764f6f8e epId=431019ef stats_id=Kenya-QG5] DtlsServer.accept#64: Error during DTLS connection: org.bouncycastle.tls.TlsFatalAlert: internal_error(80)
JVB 2024-12-31 09:27:32.456 SEVERE: [107] [confId=7385f3f5c75d0150 conf_name=[email protected] meeting_id=764f6f8e epId=431019ef stats_id=Kenya-QG5] DtlsTransport.startDtlsHandshake#140: Error during DTLS negotiation, closing this transport manager
org.bouncycastle.tls.TlsFatalAlert: internal_error(80)
at org.bouncycastle.tls.DTLSServerProtocol.accept(Unknown Source)
at org.bouncycastle.tls.DTLSServerProtocol.accept(Unknown Source)
at org.jitsi.nlj.dtls.DtlsServer.accept(DtlsServer.kt:45)
at org.jitsi.nlj.dtls.DtlsServer.start(DtlsServer.kt:41)
at org.jitsi.nlj.dtls.DtlsStack.start(DtlsStack.kt:151)
at org.jitsi.videobridge.transport.dtls.DtlsTransport.startDtlsHandshake(DtlsTransport.kt:137)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.RuntimeException
at org.jitsi.videobridge.transport.ice.IceTransport.send(IceTransport.kt:273)
at org.jitsi.videobridge.Endpoint$setupDtlsTransport$2.sendData(Endpoint.kt:461)
at org.jitsi.videobridge.transport.dtls.DtlsTransport$dtlsStack$1$2.sendData(DtlsTransport.kt:106)
at org.jitsi.nlj.dtls.DtlsStack$DatagramTransportImpl.send(DtlsStack.kt:291)
at org.bouncycastle.tls.DTLSRecordLayer.sendDatagram(Unknown Source)
at org.bouncycastle.tls.DTLSRecordLayer.sendRecord(Unknown Source)
at org.bouncycastle.tls.DTLSRecordLayer.send(Unknown Source)
at org.bouncycastle.tls.DTLSReliableHandshake$RecordLayerBuffer.sendToRecordLayer(Unknown Source)
at org.bouncycastle.tls.DTLSReliableHandshake.writeHandshakeFragment(Unknown Source)
at org.bouncycastle.tls.DTLSReliableHandshake.writeMessage(Unknown Source)
at org.bouncycastle.tls.DTLSReliableHandshake.sendMessage(Unknown Source)
at org.bouncycastle.tls.DTLSServerProtocol.serverHandshake(Unknown Source)
... 9 more

@peterdettman
Copy link
Collaborator

For a large number of TLS errors the peer will simply close its connection and that is likely what this stack trace reflects, although it's hard to be certain. I am a bit curious what version of BC jars this is using too, since DTLSRecordLayer.fail would be expected to catch and ignore an IOException generated while trying to deliver a fatal alert.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants