#bedrock players can’t connect and I can’t run geyser commands on bisect hosting

23 messages · Page 1 of 1 (latest)

neon wolf
#

!!logs

tough obsidianBOT
# neon wolf !!logs

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.

flint walrus
#

This is what I get when i try to get the logs

#

Or any commands

#

Using geyser

neon wolf
#

send the full latest.log file, geyser probably isn't starting up correctly

flint walrus
tough obsidianBOT
# flint walrus
Found errors in the log!

See below for details and possible fixes

java.lang.NullPointerException: Cannot invoke "org.geysermc.geyser.GeyserImpl.getLogger()" because "this.geyser" is null

Unknown fix!
Class: GeyserCommandManager
Method: register
Line: 127
Link: GeyserCommandManager.java#L127

neon wolf
#

!!paper
try using Paper instead of Spigot/Craftbukkit

tough obsidianBOT
flint walrus
tough obsidianBOT
# flint walrus
Found errors in the log!

We don't currently have automated responses for the detected errors!

neon wolf
#

!!setup
Geyser is now running, make sure you've followed the setup guide also, bisect hosting has instructions for setting up Geyser

tough obsidianBOT
flint walrus
#

Bedrock players are still unable to join

tough obsidianBOT
flint walrus
tough obsidianBOT
tough obsidianBOT
flint walrus
tough obsidianBOT