players timing out/an error occurred in e4mc #50

Open
opened 2024-01-28 23:54:44 +02:00 by queermoth · 0 comments

from what i can tell from looking through the logs, it appears to be this series of lines:
[28Jan2024 16:45:39.941] [nioEventLoopGroup-2-1/DEBUG] [io.netty.incubator.codec.quic.Quiche/]: quiche: 76533a766955ee9d0738dc3a6232e5623bbee4db idle timeout expired
[28Jan2024 16:45:39.942] [nioEventLoopGroup-2-1/INFO] [net.minecraft.client.gui.components.ChatComponent/]: [CHAT] An error occurred in e4mc
[28Jan2024 16:45:39.944] [nioEventLoopGroup-2-1/INFO] [e4mc-quiclime/]: channel inactive(from Quiclime): [id: 0x6153c159, QuicStreamAddress{streamId=25}] (MC: [id: 0x1e419c6d, L:local:E:341da339 - R:local:e4mc-relay])
[28Jan2024 16:45:39.949] [nioEventLoopGroup-2-1/INFO] [e4mc-quiclime/]: channel inactive(from MC): [id: 0x6153c159, QuicStreamAddress{streamId=25}] (MC: [id: 0x1e419c6d, L:local:E:341da339 ! R:local:e4mc-relay])

e4mc was working fine last night, but started seeing this issue when players joined me today, and has occurred with multiple players. it doesn't seem to have a specific trigger that i can tell when playing, and i have no clue how to go about debugging this ;0; my debug is too big to upload, but i can package it if you need it.

from what i can tell from looking through the logs, it appears to be this series of lines: [28Jan2024 16:45:39.941] [nioEventLoopGroup-2-1/DEBUG] [io.netty.incubator.codec.quic.Quiche/]: quiche: 76533a766955ee9d0738dc3a6232e5623bbee4db idle timeout expired [28Jan2024 16:45:39.942] [nioEventLoopGroup-2-1/INFO] [net.minecraft.client.gui.components.ChatComponent/]: [CHAT] An error occurred in e4mc [28Jan2024 16:45:39.944] [nioEventLoopGroup-2-1/INFO] [e4mc-quiclime/]: channel inactive(from Quiclime): [id: 0x6153c159, QuicStreamAddress{streamId=25}] (MC: [id: 0x1e419c6d, L:local:E:341da339 - R:local:e4mc-relay]) [28Jan2024 16:45:39.949] [nioEventLoopGroup-2-1/INFO] [e4mc-quiclime/]: channel inactive(from MC): [id: 0x6153c159, QuicStreamAddress{streamId=25}] (MC: [id: 0x1e419c6d, L:local:E:341da339 ! R:local:e4mc-relay]) e4mc was working fine last night, but started seeing this issue when players joined me today, and has occurred with multiple players. it doesn't seem to have a specific trigger that i can tell when playing, and i have no clue how to go about debugging this ;0; my debug is too big to upload, but i can package it if you need it.
715 KiB
Sign in to join this conversation.
No description provided.