Skip to content

common-issues.md

Latest commit

 

History

History
144 lines (89 loc) · 9.89 KB

common-issues.md

File metadata and controls

144 lines (89 loc) · 9.89 KB
Raw
title Common Issues
description Common issues that people may encounter with Geyser and potential fixes for them.

Common Issues

Commonly, people may have issues with Geyser not showing up in their server list or run into similar issues. This page contains a few common issues people may encounter that you might have as well as potential fixes for them. If you still can't make it work, join our Discord for support.

Floodgate

For Floodgate issues see: Floodgate: Known Issues/Caveats.

I can't connect! (Either the server doesn't show up in the friends list or I get "Unable to connect to world")

  • If you don't use a reverse proxy such as TCPShield make sure that advanced.java.use-haproxy-protocol is set to false. To fix "Unable to connect to world" with no console errors, see here.

If the server doesn't show up in the friends list {#if-the-server-doesnt-show-up-in-the-friends-list}

  • If using Windows 10, iOS, or Android: try adding the server to the Servers list in-game.
  • If using Xbox One: try connecting with BedrockConnect.
  • If using PS4: try using a LAN proxy.
  • If using Nintendo Switch: there is currently no way for local servers to show up in the Friends tab, but you can still connect using BedrockConnect.

If the Geyser instance is locally hosted: try using localhost or 0.0.0.0 as the IP address. If that doesn't work, or your Geyser instance is on another computer in the network: use your local IPv4 address.

:::warning

See here for fixing "Unable to Connect to World" with no console errors

:::

java.net.BindException: Address already in use: bind on startup. {#javanetbindexception-address-already-in-use-bind-on-startup}

This means something (likely another instance of Geyser) is running on the port you have specified in the config. Please make sure you close all applications running on this port. If you don't recall opening anything, usually restarting your computer fixes this.

[...] has been compiled by a more recent version of the Java Runtime (class file version 60.0) {#-has-been-compiled-by-a-more-recent-version-of-the-java-runtime-class-file-version-600}

See this link for updating to Java 17: https://docs.papermc.io/misc/java-install.

Hosting provider will not immediately open up UDP. {#hosting-provider-will-not-immediately-open-up-udp}

These steps only apply for the standalone version of Geyser. This usually has something to do on your host's end. Most commonly, it's because they do not open up ports over the UDP protocol, which is what Minecraft: Bedrock Edition uses, opposed to Minecraft: Java Edition using TCP. One way to get around this (if you're using an online host) is to shut down your server, and when asking for a server jar, select Nukkit, or any other Bedrock edition server software (you won't actually be switching to Nukkit). Afterward, open up your FTP file manager and find the Nukkit jar. Then, replace this jar with the server software you're using. Upon starting up the server, it should open up ports over UDP whilst still allowing you to use the server jar you desire.

PLEASE NOTE: If your server automatically redownloads jars upon startup, such as with an autoupdate system, this workaround will not work. Please contact your host if this does not work for you as there is nothing we can do.

Stuck on "Locating Server" with no errors

You may need to update your Java version. If so, update at Adoptium.net.

Sometimes this happens in poor-network environments. There is an advanced.bedrock.mtu option in the Geyser config; lower this number slowly (in batches of 100), restart each time, and re-test joining.

This option will most likely not help if you are getting "Unable to Connect to World" with no console logs indicating a connection.

Failed to ping the remote Java server

One issue that you can encounter when starting your server with Geyser is eanbled is several occurences of messages similar to the following.

[23:59:55] [Geyser Scheduled Thread-2-1/WARN]: [Geyser-Spigot] Failed to ping the remote Java server! Is it online and configured in Geyser's config?

Such type of message could be caused by incorrect settings in your floodgate setup, but it could also be due to your server MOTD being to long or your server-icon.png being to large. You should see an message similar to the bellow if that is the case.

String too big (was 38210 characters, max 32767)

Another symptom is that your Minecraft client will be unable to ping your server and that you won't see the player count in the server list.

The way to fix this issue is to make sure that your MOTD is of an acceptable length and that your server-icon.png have a sensible file size. RGB (without alpha channel) and 8 bit bit depth when creating your server-icon.png will help reduce the file size.

Login Failed

If you are using a plugin version: in your Geyser config, set your remote address to 127.0.0.1. If that does not work, check your startup log for a message about Docker, and use that address in the remote address

Cannot reply to EncryptionRequestPacket without profile and access token {#cannot-reply-to-encryptionrequestpacket-without-profile-and-access-token}

There are two causes of this message:

Floodgate issue:

This message can occur with a Floodgate setup. Usually, it means that a misconfiguration occurred, or another plugin is conflicting. If you copied the Floodgate key from its folder to the Geyser folder on the same server, this is now unnecessary and you can safely remove the Geyser copy, restart, and try again.

Server is in Online Mode while Geyser is in Offline Mode:

If you have your configuration set up like this, put simply, it won't work. If authentication for the Java server is set to online, it is expected Geyser is configured the same way. The server requires a valid Minecraft: Java Edition account, and if you aren't logging into one with Geyser, then you will be unable to join the server. If your configuration is set up properly and you're still getting this issue, it could be that your credentials are invalid.

Connection Refused: <INSERT IP AND/OR DOMAIN> {#connection-refused-insert-ip-andor-domain}

Connection Refused usually means that a Java server could not be found on that port, or the server denied access to the connection on a network level. The latter can happen with anti-DDOS plugins such as TCPShield, but otherwise ensure that the server you're trying to connect to is spelled correctly in the config, is up and is port forwarded correctly.

Floodgate Misconfiguration {#floodgate-misconfiguration}

See this page for more information.

Missing profile key. This server requires secure profiles. {#missing-profile-key-this-server-requires-secure-profiles}

See this page.

Mojang Resetting Account Credentials {#mojang-resetting-account-credentials}

This is unfortunately something we have no control over, and is most likely the case when you're running Geyser as a plugin on a server host or joining a friend far away from your location. If you're running Geyser locally, this should not happen to you, but what we recommend for servers is a plugin we make called Floodgate, which allows for Bedrock clients to join your server without needing a Java Edition account. Take a look here for more information.

"Invalid IP address!" from Bedrock

This can happen if the domain you are entering resolves to a SRV record, which Bedrock does not support. Try using the IPv4 address instead. Additionally, this can happen when trying to specify both the ip and port in the ip tab - in which case, see here for how to properly connect to "test.geysermc.org:19132".

Bedrock clients freeze when opening up commands for the first time

Disable command-suggestions in your Geyser config. This will stop the freezing at the expense of removing command suggestions from Bedrock clients. If you're a dedicated server admin, you can have a list of commands players should be using. This will remove any unnecessary commands from tab completion as well for Java players. It has other benefits too. Here's a plugin that can just do that: CommandWhitelist. Alternatively, use the HideCommands Geyser extension to hide commands just for Bedrock players.

Failed to load locale asset cache: Unrecognized token 'Cannot'

This or anything else related to failing to download a locale file on startup is usually caused by java trying to connect using IPv6 and Mojang only use IPv4, so start Geyser or the server up with this flag -Djava.net.preferIPv4Stack=true, EG: java -Xms1024M -Djava.net.preferIPv4Stack=true -jar Geyser.jar

Outdated client! Please use 1.x.x

The server is too new or Geyser is outdated. Make sure you're on the latest Geyser.

Outdated server! I'm still on 1.x.x

Update the server or ask them to install ViaVersion. You can also try VIAaaS (ViaVersion as a Service).

Only for BungeeCord with floodgate

If you use floodgate ensure that it is installed on all of your Spigot backend servers as following:

  1. Bungee: Geyser and Floodgate
  2. Lobby: floodgate
  3. Server-1: floodgate
  4. Server-2: floodgate

And so on.

  • Please also make sure that you have the same key.pem and config.yml on all of your servers.

If your players can't connect from the lobby to another backend server, check console.

Plugins that can cause issues {#plugins-that-can-cause-issues}

  • HamsterAPI