Fabric Server kicking player when joining from Velocity
For some reason, when a player join my fabric server (1.12) from velocity (1.21), it immediately kicks them with no error. The fabric server uses Fabric Proxy Lite.
Console:
14 Replies
Thanks for asking your question!
Make sure to provide as much helpful information as possible such as logs/what you tried and what your exact issue is
Make sure to mark solved when issue is solved!!!
/close
!close
!solved
!answered
Requested by lupancham#0
Mods, mods ending in .disabled are disabled
```
alternate-current-mc1.21-1.8.0.jar
Amplified_Nether_1.21_v1.2.5.jar
amplified-nether-height-1.1.jar
AnvilNeverTooExpensive-fabric-1.21-1.2.jar
architectury-13.0.3-fabric.jar
audioplayer-fabric-1.21-1.10.2.jar
balm-fabric-1.21-21.0.11.jar
bclib-21.0.3.jar
better-end-21.0.0.jar
c2me-fabric-mc1.21-0.2.0+alpha.11.106.jar.disabled
cloth-config-15.0.127-fabric.jar
cpm-svc-compat-1.2.1.jar
CustomPlayerModels-Fabric-1.21-0.6.17d.jar
day-dream-1.0.10.jar
dcintegration-fabric-3.0.7.2-1.21.jar.disabled
dungeons-and-taverns-ancient-city-overhaul-v2.jar
dungeons-and-taverns-desert-temple-overhaul-v1.jar
dungeons-and-taverns-jungle-temple-overhaul-v1.jar
dungeons-and-taverns-nether-fortress-overhaul-v1.jar
dungeons-and-taverns-ocean-monument-overhaul-v1.jar
dungeons-and-taverns-pillager-outpost-rework-v2.jar
dungeons-and-taverns-stronghold-rework-v2.jar
dungeons-and-taverns-swamp-hut-overhaul-v2.jar
dungeons-and-taverns-v4.jar
dungeons-and-taverns-woodland-mansion-overhaul-v1.jar
elytratrims-fabric-3.3.0+1.21.jar
fabric-api-0.100.4+1.21.jar
fabric-language-kotlin-1.11.0+kotlin.2.0.0.jar
FabricProxy-Lite-2.9.0.jar
ferritecore-7.0.0-fabric.jar
flan-1.21-1.10.6-fabric.jar
infinities-1.2+1.21.jar
instantgroup-fabric-1.21-1.6.0.jar
item-rename-1.0.0-fabric.jar
jamlib-fabric-1.0.9+1.21.jar
krypton-0.2.8.jar.disabled
lithium-fabric-mc1.21-0.12.7.jar
MendableAnvils-fabric-1.21-1.2.0.jar
midnightlib-fabric-1.5.7.jar
moderner-beta-fabric-6.5+er1.3.1+1.21.jar
modernfix-fabric-5.18.5+mc1.21.jar
modmenu-11.0.1.jar
mostructures-fabric-1.5.0+1.21.jar
mru-0.4.4+1.21.jar
netherportalfix-fabric-1.21-21.0.2.jar
noisium-fabric-2.2.1+mc1.21.jar
Nullscape_1.21_v1.2.6.jar
Pl3xMap-1.21-501.jar
repurposed_structures-7.5.3+1.21-fabric.jar
servercore-fabric-1.5.3+1.21.jar.disabled
sit!-1.1.7+1.21.jar
SnowUnderTrees-2.4.0+1.21.jar
styledplayerlist-3.5.1+1.21.jar
tool-trims-mod-v2-1-3a.jar
vcinteraction-fabric-1.21-1.0.7.jar
vivecraft-1.21-1.1.9-a2-fabric.jar
vmp-fabric-mc1.21-0.2.0+beta.7.162-all.jar.disabled
voicechat-fabric-1.21-2.5.18.jar
waystones-fabric-1.21-21.0.8.jar
worldweaver-21.0.4.jar
xlpackets-1.0.5-1.21.jar
YetAnotherConfigLib-3.5.0+1.21-fabric.jar
you_may_rest_now-fabric-1.0.0+1.21.jar
1. send the entire logs of your backend
2. send the entire logs of your proxy
through https://mclo.gs/ which hides private info
mclo.gs - Paste, share & analyse your Minecraft logs
Easily paste your Minecraft logs to share and analyse them.
I won't be able to get the proxy logs for a while until the person who runs the proxy gets online
:ThumbsUp:
currently it seems to either be a proxy issue or a client issue
Also noting that I can join the server directly with the proxy disabled
most likely proxy then
I’ll ask the operator soon
No clue why it shows as a forge server log
Lrss is the fabric server
Particularly for some very large mod packs, there is an elevated risk of the connection between the player and the proxy dropping. There is not much we can do on the proxy end to alleviate this. We suggest either reducing the number of mods your server uses, or raise the read-timeout setting in velocity.toml and add the -Dfml.readTimeout startup flag to your Forge server and setting it to the value (in seconds) you chose for the proxy. For instance, if you determine that 120 seconds is the best read timeout to use, use -Dfml.readTimeout=120 and set read-timeout = 120000 in velocity.toml.
that’s for forge
Same goes for fabric but may change
Are both servers on the same machine
They are
trying with increased timeout limit
It does not work
also giving the same error in logs uploaded already
might have to disconnect the server from the proxy and let it have it's own IP rather than have a npc in the hub