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

Cannot connect with latest Velocity version #58

Open
Apocalypsing opened this issue Mar 19, 2023 · 7 comments
Open

Cannot connect with latest Velocity version #58

Apocalypsing opened this issue Mar 19, 2023 · 7 comments

Comments

@Apocalypsing
Copy link

Apocalypsing commented Mar 19, 2023

NanoLimbo version: 1.5.1
Velocity version: Velocity 3.2.0-SNAPSHOT (git-01f1e1a9-b243)

As per title, even with the latest version as I type this issue up, players cannot join the limbo server. Seems like an issue due to latest Velocity version? Something about invalid packets upon trying to connect

Relevant log entries from Velocity proxy (I can't seem to find full stack traces though):

[16:39:17] [Netty epoll Worker #1/INFO] [com.velocitypowered.proxy.connection.MinecraftConnection]: [server connection] Apocalypsing -> Lobby has connected
[16:39:17] [Netty epoll Worker #1/ERROR] [com.velocitypowered.proxy.connection.MinecraftConnection]: [server connection] Apocalypsing -> Lobby: exception encountered in com.velocitypowered.proxy.connection.backend.LoginSessionHandler@2ad0f05a
com.velocitypowered.proxy.util.except.QuietRuntimeException: A packet did not decode successfully (invalid data). If you are a developer, launch Velocity with -Dvelocity.packet-decode-logging=true to see more.
[16:39:17] [Netty epoll Worker #1/INFO] [com.velocitypowered.proxy.connection.MinecraftConnection]: [server connection] Apocalypsing -> Lobby has disconnected
[16:39:17] [Netty epoll Worker #1/INFO] [com.velocitypowered.proxy.connection.MinecraftConnection]: [server connection] Apocalypsing -> Survival has connected
@SuperErnD
Copy link

SuperErnD commented May 17, 2023

My Velocity 3.2.0-SNAPSHOT (git-6a125bd0-b247) is work perfect (3.2.0-snapshot is latest), maybe encryption or similar changed in new commits.

@SuperErnD
Copy link

No, i dont saw the your velocity version, just update velocity

@AlexWright1324
Copy link

Also getting this error with the latest Velocity 3.2.0-SNAPSHOT (git-8dcc7ee3-b294)

[14:31:12 INFO]: [server connection] AlexWright1324 -> lobby has connected
[14:31:12 ERROR]: [server connection] AlexWright1324 -> lobby: exception encountered in com.velocitypowered.proxy.connection.backend.LoginSessionHandler@74b7ad60
io.netty.channel.unix.Errors$NativeIoException: recvAddress(..) failed: Connection reset by peer
[14:31:12 INFO]: [server connection] AlexWright1324 -> lobby has disconnected

@AlexWright1324
Copy link

Also getting this error with the latest Velocity 3.2.0-SNAPSHOT (git-8dcc7ee3-b294)

[14:31:12 INFO]: [server connection] AlexWright1324 -> lobby has connected
[14:31:12 ERROR]: [server connection] AlexWright1324 -> lobby: exception encountered in com.velocitypowered.proxy.connection.backend.LoginSessionHandler@74b7ad60
io.netty.channel.unix.Errors$NativeIoException: recvAddress(..) failed: Connection reset by peer
[14:31:12 INFO]: [server connection] AlexWright1324 -> lobby has disconnected

Turns out it was due to IP set in the config

@LannceXD
Copy link

how did you do it?, cant seem to find a fix

@SuperErnD
Copy link

well, i dont tried nanolimbo on newest velocity, but try update velocity if it old

@LannceXD
Copy link

Got the latest

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

4 participants