#v900 IO error using legacy ping passthrough with setting disabled

9 messages · Page 1 of 1 (latest)

proper heron
#

Nonstop connection issues all day. This is a new error on the new v900 release as of today.

java.net.SocketException: Connection reset
        at sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:323) ~[?:?]
        at sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:350) ~[?:?]
        at sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:803) ~[?:?]
        at java.net.Socket$SocketInputStream.read(Socket.java:966) ~[?:?]
        at java.net.Socket$SocketInputStream.read(Socket.java:961) ~[?:?]
        at java.io.DataInputStream.readByte(DataInputStream.java:271) ~[?:?]
        at org.cloudburstmc.nbt.util.VarInts.decode(VarInts.java:149) ~[Geyser-v900.jar:?]
        at org.cloudburstmc.nbt.util.VarInts.readUnsignedInt(VarInts.java:25) ~[Geyser-v900.jar:?]
        at org.geysermc.geyser.ping.GeyserLegacyPingPassthrough.run(GeyserLegacyPingPassthrough.java:120) [Geyser-v900.jar:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [Geyser-v900.jar:?]
        at java.lang.Thread.run(Thread.java:833) [?:?]```
coral flowerBOT
pseudo maple
#

Errors as these would generally imply that geyser wasn't able to ping the java server - could be anything from a misconfigured IP/port, some rate limiting, the java server being offline or otherwise blocking incoming pings

proper heron
#

Is there any way to debug what part of the server is failing to ping?

pseudo maple
#

there's nothing really to debug, this just straight up says it was closed
Check whether Java clients can ping the java server, and whether you have any plugins that might be prohibiting local pings

proper heron
#

Java clients have no issues logging in, connecting, downloading packs or pinging

pseudo maple
#

do you have any plugins or similar running on the java server that could be rejecting pings?

#

(btw, is this the same issue as #1400678769534042213? if yes, it makes 0 sense to have two threads for the same thing)

proper heron