#Your version is not supported.
42 messages · Page 1 of 1 (latest)
Possible problems:
enable-proxy-protocolshould ONLY be enabled if you run a reverse UDP proxy in front of Geyser.use-proxy-protocolshould ONLY be enabled if either of these apply:
1. Your server supports PROXY protocol (this has nothing to do with if you're using BungeeCord or Velocity).
2. You have the exact same option enabled in your BungeeCord/Velocity config (it is off by default).
Standalone
***:19132
127.0.0.1:25565 (internal IP)
FLOODGATE
Unknown
Yes
MOTD:
CLOUDHAVEN [1.21.4+] | 20% LAUNCH SALE
ᴏɴᴇʙʟᴏᴄᴋ ʀᴇʟᴇᴀsᴇᴅ → discord.gg/cloudhaven
Players: 21/22
Version: Velocity 1.7.2-1.21.8 (4)
MOTD:
CLOUDHAVEN [1.21.4+] | 20% LAUNCH SALE
ᴏɴᴇʙʟᴏᴄᴋ ʀᴇʟᴇᴀsᴇᴅ → discord.gg/cloudhaven
Players: 21/22
Version: 1.21.101 (827)
This means that the Bedrock client cannot find the server specified.
If you have not already, follow our setup instructions. Then, check the server console for any errors.
To verify Bedrock clients can connect, you can try running the geyser connectiontest <ip> <port> command with your server IP and Geyser port.
Additionally, there are various fixes for this on our wiki, please see here.
Dedicated Server and using Tmux.
All steps has been done especially the port forwarding part
I have no clue why you have enable-proxy-protocol and use-proxy-protocol enabled. There’s no point unless you’re running a reverse udp proxy.
And yes velocity is not a reverse udp proxy.
It was my system admin who set that up. I think its because of tcp shield? I am unsure
Should I just disable it?
Do you have the premium TCPShield or no?
The $100/mo plan for bedrock support? Yes
Yes
!!domain
This is like my only guess if it’s pingable.
Thank you. Will check this out with my admin
Are you self hosting this?
This is what I get from my admin
any thoughts? @steep dove
!!ping
Make sure your domain isn’t using a SRV DNS record.
!!domain
If the issue still occurs after u did the domain stuff, feel free to reply here and wait for me or someone else to reply.
Weird. It works for other but not for me. You know whats causing this?
you're probably using the wrong port, this happened to me and using the correct port fixed it
Are you perhaps using Minecraft: Bedrock for Windows 10? Is the server hosted on the same computer as the bedrock client your joining on?
If you qualify for the above questions, you'll probably need this fix.
!!loopback
Also, make sure your using the right ip address and bedrock port.