Help with Velocity-Fabric setup
I am setting up a Velocity server with a single 1.19.2 Fabric server, and I've downloaded and configured everything so far, but I'm having trouble both getting it to be publicly accessible, and with the a error being thrown when attempting to connect.
16 Replies
Thanks for asking your question!
Once you have finished, please close your thread.
Make sure to provide as much helpful information as possible such as logs/what you tried and what your exact issue is
command to close
/close
!close
!solved
Requested by dramerica#0
my guess here is that I messed up somewhere in the config, as I'm kind of new and I'm not entirely sure what all I need to get this working
make sure the mods on the server side are the same as the mods on the client side
they are, it's copy pasted from the client
werid, but is the client joining first to velocity or directly to fabric?
velocity
the only difference is FabricProxy-Lite, but that's server side
maybe because velocity doesn't expect the mods to be present and kicks you?
I wouldn't think so, it looks like the server itself is the one kicking me
and I got bungeecord working with a 1.20.1 server earlier, so I assume that there aren't any underlying issues with my setup, and that it's gotta be some sort of user error with configurations
specifically, the error states this at the beginning:
java.lang.IllegalArgumentException: Payload may not be larger than 1048576 bytes
and that's from the output from the modded server, not velocity, velocity is just reporting the disconnect and reason
I tried changing ping-passthrough to all 4 options, no change. I'm going to keep looking though
The first issue regarding the error is still present, however, and is still either something I configured in error, or possibly that velocity is handling incorrectly
fixed the second issue, needed to enable
haproxy-protocol = true for it to correctly interpret FRP traffic
so, partially solved in that regard
tried a run locally, and it worked flawlessly, so I can only assume there's an issue with velocity causing this
maybe velocity is doing some weird shit with the packets, idk
I'll try doing a few more things before I go to bed
messing with compression didn't do anything, so now I'm trying the connectivity mod
connectivity mod is incompatible with something in my modpack, causes a crash (bruh)
Aight, I'm back and got some new info. It seems that this is an issue with the mods, as removing all of the mods (except for a few) results in a working server
If anyone could give me a list of fabric mods that have issues with Velocity, it would be greatly appreciated, because I have a fairly large modpack, and even doing a binary search will be a real pain in the ass, especially because I will have to mimic the mods on both the client and server sidesend the mods brother
It’s this modpack https://modrinth.com/modpack/dogcraft-official
Modrinth
DogCraft - Minecraft Modpack
Fabric modpack focused on adventure, multiplayer and creativity, compiled by TheGamerCanine. Play with friends!
I've replicated the behavior with these mods
Please use a paste service instead!
Paste services are more mobile friendly and easier to read than just posting a log file
message.txt
Requested by dramerica#0
On a hunch, I'm gonna test if removing Traveler's titles will do the trick
it didn't
I've narrowed it down to be either consistency plus or continuity
well, now it's just yelling about an NBT tag
I think it's chipped
Okay, just removing chipped doesn't fix it, so I'm trying removing chipped, everything with the word "create"/"creative" in its name (and the things that depend on them), consistency+, and continuity
Okay, doing that fixed it, so now to figure out which mod specifically is causing it
Okay, if I remove just Chipped, Consistency+, and Continuity, then I get the NBT tag error
https://mclo.gs/n3MkJPj - Client Log
https://mclo.gs/xSzYivX - Server Log
Did some more testing. The combination of Chipped, Consistency+, Continuity, Create and Create Deco, and FabricProxy-Lite will always result in the NBT tag error, which is just the watered down version of the other issue.
After even further testing: I can safely conclude that Velocity is causing this issue
I think you were partially right with this, but I think it's probably Velocity not expecting the added data from the mods to go over a couple of hard-coded max values, so it just decides not to handle them and throws an error