#Bedorck Skin Issue...
1 messages · Page 1 of 1 (latest)
Possible problems:
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).
Velocity
0.0.0.0:35562 (internal IP)
***:35562
FLOODGATE
3.4.0-SNAPSHOT (git-d47848cb-b523)
Yes
So I was able to figure out the issue and make bedrock players join. but im facing a issue that Java players are unable to see bedrock players skin.
Bedorck Skin Issue...
..
!!skins
0
0
1 millisecond
Huh do you got floodgate on
Yeah you do from the logs I see
Are the skins too complex or not classic skins?
I do have flood gate on both servers.
So i got a main server and a proxy velocity server both has floodgate installed and the skin i use is minecraft marketplace skin and i've tried other skins too it didnt worked.
.
@tall frost U do not need use proxy protocol enabled.
Tag Unable To Connect removed
Thats it? And i should be good?
Your skins should be loading if floodgate is installed on the proxy and backend.
Make sure the key.pem from the proxy is the same one for the backend servers.
I said that because you don’t need it enabled.
Yes i've done that
Well you should probably disable use-proxy-protocol and restart your proxy.
Idk if that’ll fix the skins but it’ll probably stop some issue from happening in the future.
!!skins
0
0
moments
Post is tagged with Answered
@tall frost Are skins still not showing up today?
They should be appearing since the queue is empty and uh u have floodgate installed on the proxy and backend.
I mean unless the skin isn’t supported.
I'll try few diff skins again..
i disabled used proxy protocol in geyser velocity and while joining from bedrock gives me End of stream error
Does the server log anything?
!!logs
@tall frost ^
[06:16:04 INFO] [geyser]: LazySenpaii has disconnected from the Java server because of End of stream
for the proxy server or the backend
backend too please :>
So uhm was able to figure out the issue for the skins.
but uhm should i still try to fix the end of stream error which is causing from use proxy protocol or let it be?
sorry im being a trouble..
alr
Could I get a new dump?
Also, I would recommend updating ViaVersion and ViaBackwards.
Yeah was about to do it..
I dont have geyser on the backend server.. so i can only provide dump from proxy
Possible problems:
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).
Velocity
0.0.0.0:35562 (internal IP)
***:35562
FLOODGATE
3.4.0-SNAPSHOT (git-d47848cb-b523)
Yes
After disabling it i get error for end of stream
@empty echo https://dump.geysermc.org/TMNK1iuyBQeTr2f0Ajo56IGsLR8chd4S
here its the updated dump withg proxy protocol set to false
Velocity
0.0.0.0:35562 (internal IP)
***:35562
FLOODGATE
3.4.0-SNAPSHOT (git-d47848cb-b523)
Yes
Update ViaVersion and ViaBackwards to see if it fixes that.
alright
Updated both ViaVersion and ViaBackwards to the latest version. and still getting the End of Stream error when use-proxy-protocol is set to false.
Is it your fabric anti cheat blocking it?
I honestly don’t know looking through logs
Given it worked on true but then didn’t on false maybe your velocity has config with proxy protocol on
there's no particular proxy-protocol on velocity config..
Huh idk
keeping it set to true wont be alr?
i'll say if it works it works..
@tall frost
I mean it shouldn’t be enabled in the first place. But, if it fixes the issue, feel free to keep it enabled. I have no clue if it will.
yeah im unsure too why its working if it shouldn't.. but its alr.. if it works..
tysm for your help.. @empty echo
Did it work?
keeping it enabled is working.
I was able to fix the skin issue earlier but we were stuck on the end of stream issue occur when use-proxy-protocol set to false. it works normally when set to true
wdym?
True
It’s interesting how it fixed it though
Maybe velocity can’t listen or something when it’s false
I did see the ports were overwritten on both and if velocity was in someway overwritten then proxied from making it connect maybe
Maybe that or looping
true..
Well what does that toggle change anyway
We can infer probally what we have to change to fix based of that
@glossy sun
use-proxy-protocol: Whether to enable PROXY/HAProxy protocol or not while connecting to the server. This is useful only when:
Your server supports PROXY protocol (it probably doesn't)
You run Velocity or BungeeCord with its respective option enabled.
IF YOU DON'T KNOW WHAT THIS IS, DON'T TOUCH IT!
UDP reverse proxy in front of your Geyser instance is what it does
But why does it work only with that though
That’s the thing we need to pinpoint
Don’t ask me. I don’t know the internals of Geyser.
I have like very basic insight I shouldn’t be doing this either
Huh well I’ll look at it I guess
ehhh guys the most important thing in programming is if the code works it just works. we dont ask questions.
It has to do with the whitlisted ip and or the server running with proxy encoded packets and the client not being able to read without it
(In my opinion)
Though I’ll check if use and enable are both off or both on
Maybe it was forgot to not use and not enable
i think use is set to true and enable proxy one is set to false
enable-proxy-connections: Allow connections from ProxyPass and Waterdog. See https://www.spigotmc.org/wiki/firewall-guide/ for assistance - use UDP instead of TCP. This option does not need to be enabled in instances like BungeeCord or Velocity.
So they would chain local bedrock and Java ports interesting
It does filter out all the ipv6 stuff with it I would belive too
Maybe just maybe ipv4 not being brought in is the issue
🤷

Geyser by default technically doesn’t support IPv6. You gotta do a small change in the Geyser config for it to work.
want me to try it out with use-proxy-protocol = false?
End of Stream is a lovely error where the cause of it is basically somewhat impossible to figure out. :)