#I'm having Bedrock Skin problems

39 messages · Page 1 of 1 (latest)

cold quest
#

Hey can anyone help me if a Java player sees a Bedrock player, the Java player cannot see the skin of the Bedrock player

#

?

pulsar cryptBOT
cold quest
#

I'm having Bedrock Skin problems

languid otter
#

Are you using a proxy or just 1 server?

cold quest
#

VeloCity Proxy

pulsar cryptBOT
languid otter
#

So yes as I said earlier you shouldnt have Geyser on the backends

#

only on the proxy

#

!!setup please follow this guide under the proxy tab

pulsar cryptBOT
cold quest
#

If I don't have Geyser on the backend server, Bedrock players can't join

languid otter
#

Then you are not sending them to the correct geyser instances

#

they should be connecting to the one on the proxy

#

if removing the others breaks them joining then you havent got your network setup properly

cold quest
#

I set it according to the Geyser Install guid

languid otter
#

The proxy servers bit?

pulsar cryptBOT
# cold quest https://dump.geysermc.org/U9xZzhF9sf5ylTsiaaIYZlUMt1CS2hDR

Possible problems:

  • You aren't on the latest Geyser version! Please download the latest version.
Git info

Latest: No
Commit: 0a928c4
Branch: master
Behind by 3 commits

Platform

Velocity

Listen address

0.0.0.0:19132 (internal IP)

Remote address

127.0.0.1:25565 (internal IP)

Auth type

FLOODGATE

Server version

3.3.0-SNAPSHOT (git-5154f029-b404)

Autoconfigured remote?

Yes

languid otter
#

ok so that looks fine, I suggest doing a connection test and seeing what that returns

#

!!connectiontest

pulsar cryptBOT
# languid otter !!connectiontest

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.

languid otter
#

That checks if your geyser is the one your IP points to

#

along with some other bits

cold quest
#

[22:43:28 INFO]: The port you are testing with (19321) is not the same as you set in your Geyser configuration (19132)
[22:43:28 INFO]: Re-run the command with the port in the config, or change the bedrock port in the config.
[22:43:28 INFO]: Testing server connection to 23.88.3.230 with port: 19321 now. Please wait...
[22:43:31 INFO]: Your server is likely unreachable from outside the network!
[22:43:31 INFO]: Got the error message: Connection timed out
[22:43:31 INFO]: If you still face issues, check the setup guide for instructions: https://wiki.geysermc.org/geyser/setup/
[22:43:31 INFO]: If that does not work, see https://wiki.geysermc.org/geyser/fixing-unable-to-connect-to-world/, or contact us on Discord: https://discord.gg/geysermc

languid otter
#

Think you made a typo on the port

cold quest
#

geyser connectiontest 23.88.3.230:19132
[22:45:55 INFO]: Testing server connection to 23.88.3.230 with port: 19132 now. Please wait...
[22:45:55 INFO]: The MOTD did not match when we pinged the server (we got 'A Minecraft Server'). Did you supply the correct IP and port of your server?
[22:45:55 INFO]: If you still face issues, check the setup guide for instructions: https://wiki.geysermc.org/geyser/setup/
[22:45:55 INFO]: If that does not work, see https://wiki.geysermc.org/geyser/fixing-unable-to-connect-to-world/, or contact us on Discord: https://discord.gg/geysermc

languid otter
#

Yea so likely your port forwarding or something is passing the traffic to the wrong box

cold quest
#

But that was already the case when there was only one server

languid otter
#

your port forwarding needs to point all traffic to velocity both for java and geyser for it to work

pulsar cryptBOT
cold quest
#

and how should I say that?

languid otter
#

I cant teach you how to do that you will have to look it up

cold quest
#

Oh yeah, that's some good support

languid otter
#

We support Geyser not general server network troubleshooting

#

Ive told you the issue but we cant do anything to fix it, we know nothing about your setup only you do so we cant fix it for you

cold quest
#

All the devs tell me it's Geyser's fault and you say it's not our fault. Ah yes

languid otter
#

Geyser has told you that your firewall is sending traffic to a backend geyser not the one on velocity. Geyser shouldnt be on a backend server. You need to take it off there and resolve the connection issue by altering firewall/port forwarding rules without adding it back to the backend