#New viaversion version - creates ”Unable to connect to world”
30 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.
Velocity
0.0.0.0:19132 (internal IP)
***:25565
FLOODGATE
3.3.0-SNAPSHOT (git-bf507dc0-b380)
Yes
I also have the same problem, I have tried all builds since 1.20.73 support and they all fail!
And I'm currently using support build 1.20.73 so players can temporarily access it!
x2
!!test what's the output of the geyser connectiontest command?
To check whether Bedrock players can connect or if port forwarding for Geyser is working, run the following command in your Minecraft server console:
geyser connectiontest <ip>:<port>
For example, if your server is running on the IP 12.34.56.78 and port 19132, you would run geyser connectiontest 12.34.56.78:19132.
@frail wigeon @young berry please make your own posts, and attach more info there - such as which server hosting providers you're using etc
Server also pings in serverlist for Bedrock users 🤔
Which server hosting provider are you using?
Dedicated machine, OVH
are you using their game firewall?
if yes, try changing the type from "pocket edition" to "other"
#1233084767747047574 message
for more info, see here
Yes - Sounds like it could be it then.
So, if i'm correct:
Remove this firewall rule, and add a new one with "other"
The new rule is now under construction. Do you know if a server restart is required for such change? Or will it start to work automaticly?
Lets fuck around and find out 😅
I will update you with the result.
sounds good :)
Ey yo, it worked! Thanks for the help 😄
No restart was required.
neat! hopefully we'll get OVH to resolve the issue with the pocket edition firewall too :/