Internal Exception: java.lang.IllegalStateException: Invalid characters in username

[fair junco]

https://dump.geysermc.org/siaAd6cgU6Lp7jM16GI2PEp5cQO5fUeE

The backend server runs without any plugin. This happens when connecting through force-host and with the /server command (Velocity)

This error does not happend on my main server under the same Velocity proxy.

[hoary roost]

<:geyser:723981877773598771> Geyser Velocity

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.

Git info

Latest: No
Commit: 6331cb6
Branch: master
Behind by 9 commits

Platform

Velocity

Listen address

0.0.0.0:19132 (internal IP)

Remote address

***:25565

Auth type

FLOODGATE

Server version

3.4.0-SNAPSHOT (git-69ee655d-b445)

Autoconfigured remote?

Yes

Nov 4, 2024, 9:25 PM

[hoary roost]

Found errors in the image!

We don't currently have automated responses for the detected errors!

[fair junco]

Bump

[hoary roost]

Level Up!

You leveled up to level 11!

[knotty geyser]

Your dump says your 9 commits behind, please update and post a new dump

[winter loom]

!!lp

[hoary roost]

To fix issues with luckperms not recognizing Bedrock players, you can set allow-invalid-usernames to true in LuckPerms’ config.

[fair junco]

It’s still wierd.. since players are able to connect to my main server under same velocity? 🤔

[winter loom]

Maybe LuckPerms integrates with the Floodgate API?

[fair junco]

something is really wierd...

Luckperms (Velocity): allow-invalid-usernames: true
Luckperms on backend server: the same ^^

Without any plugins on backend server: Same result

The other backend server however works. Is there anything in server.properties, spigot or paper configuration which could do this?

https://dump.geysermc.org/hNQBiUVYRft7dmAK6NyesQaapfyXNse3

[hoary roost]

<:geyser:723981877773598771> Geyser Velocity

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.

Git info

Latest: No
Commit: d61ad7b
Branch: master
Behind by 61 commits

Platform

Velocity

Listen address

0.0.0.0:19132 (internal IP)

Remote address

***:25565

Auth type

FLOODGATE

Server version

3.4.0-SNAPSHOT (git-69ee655d-b445)

Autoconfigured remote?

Yes

Nov 5, 2024, 4:31 PM

[fair junco]

wait what, is there 61 new commits today? 😅
Updated new Geyser update yesterday...

[knotty geyser]

You are one build behind, current is b706. Must’ve been quite a few commits between builds. An update can’t hurt

[fair junco]

Found the issue

paper.global.yml 😠
perform-username-validation: true

I had old copys in the first directory, forgot the new ones is in a config directory...

[knotty geyser]

Glad you got it figured out!

[hoary roost]

Level Up!

You leveled up to level 3!

[fair junco]

this was litteraly the first thing I checked.. but I changed a non active config

lmao

Thanks for the help folks ^^ hopefully someone can CTRL + F this if they have the samme issue.

[knotty geyser]

🤣 it’s always what you least expect