#Bedrock Cannot See their own Skins

29 messages · Page 1 of 1 (latest)

pine talon
#

Okay, so simply put bedrock cannot put see their own skins but java can. Yes, I have looked through options, yes I have tested the geyser API to see if it pulls the skin (it does). Here are a key few notes, please let me know if I am crazy lol.

https://dump.geysermc.org/PVhf0y26F6Oj5izNcrgCZWcANngtF0CL

We use NeoProtect, which uses Proxy Protocol, these have all been enabled in each respective server other than the Hub Server (where this is being hosted, portion of the paper-config.yml I do not have enabled for proxy-protocol ), I have uploaded the key.pem file from the Proxy to the Hub, I have the latest versions of all plugins, all of my networking and connection works it is quite literally just the skin.

I understand there is the !!skin option, I also have read the wiki a few times and have tried a few things to troubleshoot. Please let me know if there is anything whoever needs to help me out, I'd appreciate the help as this is quite literally my first time solo setting up Geyser 🙏.

image.png
tight copperBOT
# pine talon Okay, so simply put bedrock cannot put see their own skins but java can. Yes, I ...
<:geyser:723981877773598771> Geyser Velocity

Possible problems:

  • enable-proxy-protocol should ONLY be enabled if you run a reverse UDP proxy in front of Geyser.
  • use-proxy-protocol should 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).
Git info

Latest: Yes
Commit: 7dcdf5c
Branch: master

Platform

Velocity

Listen address

0.0.0.0:19132 (internal IP)

Remote address

***:51820

Auth type

FLOODGATE

Server version

3.4.0-SNAPSHOT (git-6e80f577-b534)

Autoconfigured remote?

Yes

final walrus
#

Huh I really don’t know you actually did this right maybe try enabling on paper too?

#

Also does the skin work on the other places with it enabled

final walrus
#

Do you have the same key.pem across all server installs?

pine talon
#

Yes

#

I have contacted my system admin regarding a possible firewall block

#

Regarding the api

final walrus
#

Do you got a floodgate config and a log of the user joining

pine talon
#

I can send that over within 10-20

#

On my phone rn

final walrus
#

Oh well I got school then most likely

pine talon
#

Haha no worries

final walrus
#

I’ll just when I can help

pine talon
#

I’ll see if my Sys admin allowed the api to pass through our firewall

#

Because I honestly think that’s what’s stopping it

final walrus
#

Still send tho since someone else could maybe

final walrus
pine talon
#

Update: Allowed API access exclusively through our system, still doesn't work

tight copperBOT
#
Current global api skin queue
Pre-upload queue

0

Upload queue

0

Upload queue time

moments

https://api.geysermc.org/v2/stats ·
final walrus
pine talon
#

@final walrus great shout, so it doesn't work on the lobby but it works on the other realm

#

Weird, going to re-install my Hub server.

#

Re-installed, still doesn't work but still works on survival realm sadpepe112

#

When players join the lobby server, they cannot see their own skin but Java players can see their skin. When they join the survival server, players can now see their own skin & java can. When they rejoin to lobby, players can also see their skin again. It's just like the initial joining of the server causes the skin not to load.

final walrus
#

Maybe turn on proxy protocol on paper-config

final walrus