-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how fix this warn #1235
Comments
Do you really have no plugins? Please list your plugins, as this is caused by plugins. Or are you using ViaVersion on Bungee and 1.13 is trying to connect? |
yes i have plugins .. AAC, AACAdditionPro, CancelSounds, ChatGuard, ChestCommands, CustomJoinItems, Essentials, EssentialsChat, FastAsyncWorldEdit, FastPot, GUIPlus, HolographicDisplays, LeaderHeads, NoRain, OldCombatMechanics, PermissionsEx, PlaceholderAPI, PressureCommand, ProtocolLib, ProtocolSupportPotions, SkyWars, SmoothKnockback, Vault, ViaBackwards, ViaRewind, ViaRewind-Legacy-Support, ViaVersion, WorldEdit, WorldGuard.. i using viaversion last |
one of the Via plugins will be the source of this issue. Please report issue to them. |
What behaviour is expected:
What you expected to see
hello I put the last paper 1.12 and it gives me a warn all the time
What behaviour is observed:
What you actually saw
12:49:09] [Netty Epoll Server IO #1/WARN]: [io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
java.nio.channels.ClosedChannelException: null
Steps/models to reproduce:
This may include a build schematic, a video, or detailed instructions to help reconstruct the issue
Plugin list:
A list of your plugins
Paper version git-Paper-1500 (MC: 1.12.2) (Implementing API version 1.12.2-R0.1-SNAPSHOT)
Paper build number:
This can be found by running
/version
on your server.latest
is not a proper version number; we require the output of/version
so we can properly track down the issue.Anything else:
Anything else you think may help us resolve the problem
The text was updated successfully, but these errors were encountered: