question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Geyser Velocity - Read timed out

See original GitHub issue

Describe the bug I have a cuberite server setup (testing on a linux laptop before moving to actual server) with velocity (viaversion and Geyser plugins). Geyser is pointing to the velocity port. When joining a world I see nothing(no chunks) and can move(only positive)… and then kicked off the server with the error read timed out.

To Reproduce Setup a server in the same way and then see the read timed out message on bedrock

Expected behavior To be able to join and interact with the workd

Server Version Cuberite Jenkins x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Release (master) build id: #1288 [16:55:16] from commit id: 6e3f6d58a4a9d660465758b33b6528e73d86520f built at: Mon 13 Jul 12:15:04 UTC 2020 (same issue with arm version too)

Geyser Version This server is running Geyser version 1.0.0 (git-master-e7657c7) (Java: 1.16.1, Bedrock: 1.16.0)

Other Versions ViaVersion 3.0.1

Minecraft: Bedrock Edition Version

Additional Context The server works fine on java though the velocity proxy… but does not work with Geyser

[17:05:49 INFO] [geyser]: /192.168.1.20:35507 tried to connect! [17:05:50 INFO] [geyser]: Player connected with username CactiChamele [17:05:57 INFO] [geyser]: Attempting to login using offline mode... authentication is disabled. [17:05:57 INFO] [geyser]: CactiChamele (logged in as: CactiChamele) has connected to remote java server on address 127.0.0.1 [17:06:27 ERROR]: [initial connection] /127.0.0.1:50202: read timed out [17:06:27 INFO]: [initial connection] /127.0.0.1:50202 has disconnected [17:06:27 INFO] [geyser]: CactiChamele has disconnected from remote java server on address 127.0.0.1 because of Read timed out. [17:06:27 ERROR]: io.netty.handler.timeout.ReadTimeoutException [17:06:27 INFO] [geyser]: Bedrock user with ip: /192.168.1.20 has disconnected for reason CLOSED_BY_REMOTE_PEER

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:8 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
CactiChameleon9commented, Jul 13, 2020

Very fast replys!!! Is this anywhere in the documentation

0reactions
CactiChameleon9commented, Jul 13, 2020

Thanks… sorry to bother you 😄

Read more comments on GitHub >

github_iconTop Results From Across the Web

Player get ReadTimeOut on BungeeCord · Issue #469 - GitHub
Describe the bug When using Geyser on BungeeCord, player sometime get ReadTimeoutException:null, and they keep getting that error, ...
Read more >
Common Issues - GeyserMC Wiki
Commonly, people may have issues with Geyser not showing up in their server list or run into similar issues. This page contains a...
Read more >
Solved - "Read Timed Out" Own Server - Bukkit Forums
"Read Timed Out" means that the client/server could not read data from the other and after a certain amount of time, stopped trying...
Read more >
Error: Timed out : r/GeyserMC - Reddit
When I join, it works alright, but when my friends join, it kicks them out after a few minutes with the error: 'Timed...
Read more >
GeyserMC Locating Server without errors issue, even i have ...
So, I am trying to install and configure GeyserMC sever plugin on my server, I'm using Pebble for hosting my server and it...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found