Hello! I have geyser and floodgate set up for a fabric 1.20.4 server. When joining on bedrock it says "Tried to log in as a java edition player! Is floodgate set up correctly?" I know this is a common question here so I'm sorry, but I've gone through every post imaginable and can't find a fix. Thanks!
https://dump.geysermc.org/5Ezp8KOXyNha5o7pPGuylMBMPDg36S8f
#Unable to connect via bedrock
1 messages · Page 1 of 1 (latest)
Possible problems:
- Your server is running inside a docker container, please make sure the Geyser port (using UDP) is exported out to the host. If you're using Pterodactyl panel then you need to make sure you have allocated the port to the server.
- You aren't on the latest Geyser version! Please download the latest version.
Git info
Latest: No
Commit: 1291b89
Branch: master
Behind by 97 commits
Platform
Fabric
Listen address
0.0.0.0:19132 (internal IP)
Remote address
***:25565
Auth type
FLOODGATE
Server version
0.15.11
Autoconfigured remote?
Yes
18.05 08:15:11 [Server] defaultEventLoopGroup-7-1/[INFO] RoboSchnitzel (logged in as: RoboSchnitzel) has connected to the Java server
18.05 08:15:11 [Server] defaultEventLoopGroup-7-1/[INFO] RoboSchnitzel has disconnected from the Java server because of Tried to log in as a Java Edition player! Is Floodgate set up correctly?
18.05 08:15:11 [Server] defaultEventLoopGroup-7-1/[ERROR] Cannot reply to ClientboundHelloPacket without profile and access token.
18.05 08:15:11 [Disconnect] User RoboSchnitzel (/172.59.226.130:0) has disconnected, reason: Disconnected```
^ When trying to join via bedrock edition, this is what the console throws
set "use-direct-connection" in geysers config to false for now, and re-enable it once you update to 1.20.6
Still no luck after changing "use-direct-connection" to false
https://dump.geysermc.org/purQZYW6GFT0cSK94NEQUXoAkADMepKH
Possible problems:
- Your server is running inside a docker container, please make sure the Geyser port (using UDP) is exported out to the host. If you're using Pterodactyl panel then you need to make sure you have allocated the port to the server.
- You aren't on the latest Geyser version! Please download the latest version.
Git info
Latest: No
Commit: 1291b89
Branch: master
Behind by 97 commits
Platform
Fabric
Listen address
0.0.0.0:19132 (internal IP)
Remote address
***:25565
Auth type
FLOODGATE
Server version
0.15.11
Autoconfigured remote?
Yes
!!logs please send a full log
An entire log file is a very useful way of debugging any issues with plugins. Sometimes a snippet of a log doesn't tell the whole story!
You can upload your log file into this channel, or you can use https://mclo.gs/ to censor all IPs present in your log.
For BungeeCord (not Waterfall) there is a proxy.log.0 file in the root and for everything else it is latest.log in logs folder.
you need to restart the server for that change to take effect
a geyser reload wont work here (for this specific option)
Sorry that was my bad. Now I am getting a new error. I am definitely whitelisted, but it says when I try to connect via bedrock edition "You are not whitelisted on this server"
Possible problems:
- Your server is running inside a docker container, please make sure the Geyser port (using UDP) is exported out to the host. If you're using Pterodactyl panel then you need to make sure you have allocated the port to the server.
- You aren't on the latest Geyser version! Please download the latest version.
Git info
Latest: No
Commit: 1291b89
Branch: master
Behind by 98 commits
Platform
Fabric
Listen address
0.0.0.0:19132 (internal IP)
Remote address
***:25565
Auth type
FLOODGATE
Server version
0.15.11
Autoconfigured remote?
Yes
!!whitelist
See here for information about adding Bedrock players to the whitelist.
https://wiki.geysermc.org/floodgate/features/#whitelist-command
If whitelisting using the username does not work, you can get the Bedrock player's Floodgate UUID here and whitelist it instead.
You are my hero
Level Up!
You leveled up to level 1!
I love you