Lost connection internal server error - Исправление ошибок и поиск оптимальных решений проблем

Greetings fellow miners and crafters.

I have a Nitrado server that I setup so my son and I could play 1.3. We had quite a few hours in the game when one morning I just could not connect. The server posts the errors thread below.

Here is what I have tried:

Rebooted the server.
Reinstalled Minecraft.
Removed my UUID.dat file from the world/playerdata folder.
Changed my skin back to default. (Changing my skin was one of the last things I did before the issue started).
Connecting from another computer on my network with a fresh install.
Played No Man’s Sky for three days to make Minecraft jealous.

[14:33:24] [User Authenticator #2/INFO]: UUID of player TillyDeHun is 471510ac-ad15-41cb-8afc-482e0ccb101a
[14:33:24] [Server thread/WARN]: Failed to handle packet for /{My external IP and port}
java.lang.IllegalStateException: Not a JSON Object: null
at com.google.gson.JsonElement.getAsJsonObject(JsonElement.java:90) ~[minecraft_server.jar:?]
at wn.a(SourceFile:82) ~[minecraft_server.jar:?]
at wn.<init>(SourceFile:48) ~[minecraft_server.jar:?]
at vo.a(SourceFile:915) ~[minecraft_server.jar:?]
at te.<init>(SourceFile:159) ~[minecraft_server.jar:?]
at vo.g(SourceFile:442) ~[minecraft_server.jar:?]
at ud.b(SourceFile:113) ~[minecraftserver.jar:?]
at ud.Y(SourceFile:65) ~[minecraft_server.jar:?]
at hw.a(SourceFile:238) ~[minecraft_server.jar:?]
at ua.c(SourceFile:171) [minecraft_server.jar:?]
at net.minecraft.server.MinecraftServer.w(SourceFile:749) [minecraft_server.jar:?]
at sn.w(SourceFile:357) [minecraft_server.jar:?]
at net.minecraft.server.MinecraftServer.v(SourceFile:656) [minecraft_server.jar:?]
at net.minecraft.server.MinecraftServer.run(SourceFile:559) [minecraft_server.jar:?]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
[14:33:24] [Server thread/INFO]: [email protected][id=471510ac-ad15-41cb-8afc-482e0ccb101a,name=TillyDeHun,properties={textures=[[email protected]]},legacy=false] (/{My external IP and port}) lost connection: Internal server error

Any help would be greatly appreciated. I am out of ideas and patience.

Thanks!

Источник

Description :
When a player attempt to connect to the server after another player or himself succesfully connect the first time, the player get an «Internal server error».
So it means that after each restart of the server, only one player can play before the next restart. As we are four it’s a little frustrating.

There seems to be a NullPointerException from FTBEssentials juste after the building of the quest package.

From the issue #1690, radiomike told me to try editing or deleting the players json files from <world>/ftbessentials/playerdata because it is probabely an issue with the nickname. I did both action but it didn’t resolve the problem.

[24May2021 18:07:17.211] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: Ajhplyr joined the game
[24May2021 18:07:17.444] [Server thread/DEBUG] [Silent Gear/]: Sending materials crafting item correction packet
[24May2021 18:07:17.445] [Server thread/DEBUG] [Silent Gear/]: Sending parts crafting item correction packet
[24May2021 18:07:17.447] [Server thread/DEBUG] [FTB Quests/]: Wrote 15423 bytes, 247 objects
[24May2021 18:07:17.450] [Server thread/ERROR] [net.minecraftforge.eventbus.EventBus/EVENTBUS]: Exception caught during firing event: null
	Index: 8
	Listeners:
		0: HIGHEST
		1: ASM: class net.silentchaos512.gear.event.ServerEvents onPlayerJoinServer(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		2: ASM: io.github.noeppi_noeppi.libx.impl.config.ConfigEvents@538ab4c6 playerJoin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		3: HIGH
		4: ASM: class ovh.corail.tombstone.event.EventHandler onPlayerLogued(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		5: ASM: class me.shedaniel.architectury.event.forge.EventHandlerImplCommon event(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		6: NORMAL
		7: ASM: class com.supermartijn642.configlib.ConfigLib$ConfigEvents onPlayerJoin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		8: ASM: class com.feed_the_beast.mods.ftbessentials.FTBEEventHandler playerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		9: ASM: class com.endertech.minecraft.forge.world.GameWorld$WorldData onPlayerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		10: ASM: class net.gigabit101.shrink.events.PlayerEvents playerConnect(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		11: ASM: class xreliquary.handler.CommonEventHandler blameDrullkus(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		12: ASM: mods.waterstrainer.event.EventPlayerLoggedIn@232f388e onPlayerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		13: ASM: class net.silentchaos512.gear.util.GearData$EventHandler onPlayerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		14: ASM: class net.blay09.mods.farmingforblockheads.registry.market.MarketRegistryLoader onLogin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		15: ASM: class me.desht.pneumaticcraft.common.recipes.amadron.AmadronOfferManager$EventListener serverLogin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		16: ASM: class com.logprot.event.EventHandler onEntityAdded(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		17: ASM: org.cyclops.integrateddynamics.core.persist.world.LabelsWorldStorage@5a02618d onPlayerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		18: ASM: class blusunrize.immersiveengineering.common.blocks.multiblocks.StaticTemplateManager onLogin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		19: ASM: class com.feed_the_beast.mods.ftbbackups.FTBBackups playerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		20: ASM: class com.ldtteam.structurize.event.EventSubscriber onPlayerLogin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		21: ASM: class com.leobeliik.extremesoundmuffler.eventHandlers.PlayerEventsHandler onPlayerLoggin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		22: ASM: class hellfirepvp.astralsorcery.common.event.handler.EventHandlerCache onPlayerConnect(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		23: ASM: net.minecraftforge.common.ForgeInternalHandler@7970fde7 playerLogin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		24: ASM: class vazkii.psi.common.core.handler.PlayerDataHandler$EventHandler onPlayerLogin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		25: ASM: class vazkii.psi.common.core.handler.LoopcastTrackingHandler onPlayerLogIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		26: ASM: class twilightforest.TFEventListener playerLogsIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		27: ASM: class twilightforest.TFEventListener onClientConnect(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		28: ASM: com.valkyrieofnight.envirotech.m_voidminer.datapack.voidregistry.VoidMinerDataRegistry@7c7970fd onPlayerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		29: ASM: com.valkyrieofnight.envirotech.m_voidminer.datapack.program.VoidMinerProgramRegistry@50406b14 onPlayerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		30: net.minecraftforge.eventbus.EventBus$$Lambda$2840/0x0000000800de7040@1c19802f
		31: net.minecraftforge.eventbus.EventBus$$Lambda$2840/0x0000000800de7040@239b8ef
		32: ASM: class vazkii.patchouli.common.handler.PlayerJoinHandler playerLogin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		33: ASM: com.valkyrieofnight.envirocore.m_machines.m_lens_grinder.dp.cat.LensGrinderCategoryRegistry@4d3f3062 onPlayerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		34: ASM: com.valkyrieofnight.envirocore.m_machines.m_lens_grinder.dp.LensGrinderRecipeRegistry@6df717fb onPlayerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		35: ASM: com.valkyrieofnight.envirocore.m_machines.m_mem_progrm.datapack.cat.MemProgrmCategoryRegistry@7cc1c46e onPlayerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		36: ASM: com.valkyrieofnight.envirocore.m_machines.m_mem_progrm.datapack.MemProgrmRecipeRegistry@79bb9715 onPlayerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		37: ASM: com.valkyrieofnight.envirocore.m_machines.m_assembler.datapack.AssemblerRecipeRegistry@3678dbe9 onPlayerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		38: ASM: class com.hollingsworth.arsnouveau.common.event.EventHandler playerLogin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		39: ASM: class me.shedaniel.architectury.networking.forge.NetworkManagerImpl loggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		40: ASM: net.blay09.mods.trashslot.TrashSlot@7ea3c25b onPlayerLogin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		41: ASM: class sirttas.elementalcraft.entity.EntityHandler playerLogin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		42: ASM: class net.blay09.mods.waystones.handler.LoginHandler onPlayerLogin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		43: ASM: de.castcrafter.travel_anchors.EventListener@63af0ddc playerJoin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		44: net.minecraftforge.eventbus.EventBus$$Lambda$2840/0x0000000800de7040@229f0140
		45: ASM: stepsword.mahoutsukai.handlers.ServerHandler@19e9d7f5 playerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		46: ASM: com.feed_the_beast.mods.ftbchunks.FTBChunks@69d42384 loggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		47: net.minecraftforge.eventbus.EventBus$$Lambda$2840/0x0000000800de7040@5b8c8b54
		48: ASM: class slimeknights.tconstruct.shared.PlayerDataEvents onPlayerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		49: ASM: class com.ma.progression.ProgressionEventHandler onPlayerLogin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		50: ASM: class sonar.fluxnetworks.register.CommonEventHandler onPlayerJoined(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		51: ASM: class com.minecolonies.coremod.event.EventHandler onPlayerEnterWorld(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		52: ASM: class com.minecolonies.coremod.event.FMLEventHandler onPlayerLogin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		53: ASM: class com.cazsius.solcarrot.tracking.MaxHealthHandler onPlayerLogin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		54: ASM: class com.cazsius.solcarrot.tracking.CapabilityHandler onPlayerLogin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		55: ASM: class vazkii.quark.base.handler.ContributorRewardHandler onPlayerJoin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		56: net.minecraftforge.eventbus.EventBus$$Lambda$2840/0x0000000800de7040@bc470f2
		57: ASM: vazkii.quark.content.tweaks.module.AutomaticRecipeUnlockModule@7eab925c onPlayerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		58: ASM: org.cyclops.cyclopscore.event.PlayerRingOfFire@16b76207 onLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		59: ASM: org.cyclops.cyclopscore.event.PlayerRingOfFire@24de031e onLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		60: ASM: shadows.apotheosis.ench.EnchModuleEvents@59222f61 login(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		61: net.minecraftforge.eventbus.EventBus$$Lambda$2840/0x0000000800de7040@44755fa5
		62: net.minecraftforge.eventbus.EventBus$$Lambda$2840/0x0000000800de7040@1e3ad36a
		63: ASM: top.theillusivec4.curios.common.event.CuriosEventHandler@338335fd playerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		64: ASM: mekanism.common.CommonPlayerTracker@7862ef22 onPlayerLoginEvent(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		65: ASM: org.cyclops.cyclopscore.event.PlayerRingOfFire@3e15c78d onLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		66: ASM: mcjty.theoneprobe.ForgeEventHandlers@5c65142e onPlayerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		67: ASM: org.cyclops.cyclopscore.event.PlayerRingOfFire@2bfe4b9b onLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		68: ASM: org.cyclops.cyclopscore.event.PlayerRingOfFire@2b854898 onLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		69: net.minecraftforge.eventbus.EventBus$$Lambda$2840/0x0000000800de7040@21532dd2
		70: ASM: org.cyclops.cyclopscore.event.PlayerRingOfFire@5abdcb37 onLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		71: ASM: squeek.appleskin.network.SyncHandler@4c39ea68 onPlayerLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		72: net.minecraftforge.eventbus.EventBus$$Lambda$2840/0x0000000800de7040@9b89aea
		73: ASM: org.cyclops.cyclopscore.event.PlayerRingOfFire@38364f26 onLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		74: ASM: org.cyclops.cyclopscore.event.PlayerRingOfFire@30db72b5 onLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		75: ASM: org.cyclops.cyclopscore.event.PlayerRingOfFire@4f07ae54 onLoggedIn(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		76: ASM: edivad.dimstorage.manager.DimStorageManager$DimStorageSaveHandler@2fdcb35c onPlayerLogin(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		77: net.minecraftforge.eventbus.EventBus$$Lambda$2840/0x0000000800de7040@675e640f
		78: ASM: dev.gigaherz.toolbelt.slot.BeltExtensionSlot$EventHandlers@586d0580 joinWorld(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
		79: ASM: mob_grinding_utils.events.ChickenFuseEvent@4b18ae7 startChickenFuse(Lnet/minecraftforge/event/entity/living/LivingEvent;)V
		80: LOWEST
		81: ASM: shetiphian.core.internal.modintegration.ftbteams.FTBTeams_Active$FTBEventHandler@4d44bb74 playerLoggedInEvent(Lnet/minecraftforge/event/entity/player/PlayerEvent$PlayerLoggedInEvent;)V
java.lang.NullPointerException
	at com.feed_the_beast.mods.ftbessentials.net.UpdateTabNamePacket.write(UpdateTabNamePacket.java:41)
	at net.minecraftforge.fml.network.simple.IndexedMessageCodec.lambda$tryEncode$4(IndexedMessageCodec.java:134)
	at java.base/java.util.Optional.ifPresent(Unknown Source)
	at net.minecraftforge.fml.network.simple.IndexedMessageCodec.tryEncode(IndexedMessageCodec.java:132)
	at net.minecraftforge.fml.network.simple.IndexedMessageCodec.build(IndexedMessageCodec.java:147)
	at net.minecraftforge.fml.network.simple.SimpleChannel.encodeMessage(SimpleChannel.java:85)
	at net.minecraftforge.fml.network.simple.SimpleChannel.toBuffer(SimpleChannel.java:98)
	at net.minecraftforge.fml.network.simple.SimpleChannel.toVanillaPacket(SimpleChannel.java:129)
	at net.minecraftforge.fml.network.simple.SimpleChannel.send(SimpleChannel.java:124)
	at com.feed_the_beast.mods.ftbessentials.util.FTBEPlayerData.sendTabName(FTBEPlayerData.java:251)
	at com.feed_the_beast.mods.ftbessentials.FTBEEventHandler.playerLoggedIn(FTBEEventHandler.java:108)
	at net.minecraftforge.eventbus.ASMEventHandler_15_FTBEEventHandler_playerLoggedIn_PlayerLoggedInEvent.invoke(.dynamic)
	at net.minecraftforge.eventbus.ASMEventHandler.invoke(ASMEventHandler.java:85)
	at net.minecraftforge.eventbus.EventBus.post(EventBus.java:302)
	at net.minecraftforge.eventbus.EventBus.post(EventBus.java:283)
	at net.minecraftforge.fml.hooks.BasicEventHooks.firePlayerLoggedIn(BasicEventHooks.java:44)
	at net.minecraft.server.management.PlayerList.func_72355_a(PlayerList.java:231)
	at net.minecraft.network.login.ServerLoginNetHandler.func_147326_c(ServerLoginNetHandler.java:118)
	at net.minecraft.network.login.ServerLoginNetHandler.func_73660_a(ServerLoginNetHandler.java:65)
	at net.minecraft.network.NetworkManager.func_74428_b(NetworkManager.java:222)
	at net.minecraft.network.NetworkSystem.func_151269_c(NetworkSystem.java:134)
	at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:865)
	at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:291)
	at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:787)
	at net.minecraft.server.MinecraftServer.func_240802_v_(MinecraftServer.java:642)
	at net.minecraft.server.MinecraftServer.func_240783_a_(MinecraftServer.java:232)
	at java.base/java.lang.Thread.run(Unknown Source)

[24May2021 18:07:17.452] [Server thread/WARN] [net.minecraft.network.NetworkSystem/]: Failed to handle packet for /[ip address]
java.lang.NullPointerException: null
	at com.feed_the_beast.mods.ftbessentials.net.UpdateTabNamePacket.write(UpdateTabNamePacket.java:41) ~[ftbessentials:1604.1.0.13]
	at net.minecraftforge.fml.network.simple.IndexedMessageCodec.lambda$tryEncode$4(IndexedMessageCodec.java:134) ~[forge:?]
	at java.util.Optional.ifPresent(Unknown Source) ~[?:?]
	at net.minecraftforge.fml.network.simple.IndexedMessageCodec.tryEncode(IndexedMessageCodec.java:132) ~[forge:?]
	at net.minecraftforge.fml.network.simple.IndexedMessageCodec.build(IndexedMessageCodec.java:147) ~[forge:?]
	at net.minecraftforge.fml.network.simple.SimpleChannel.encodeMessage(SimpleChannel.java:85) ~[forge:?]
	at net.minecraftforge.fml.network.simple.SimpleChannel.toBuffer(SimpleChannel.java:98) ~[forge:?]
	at net.minecraftforge.fml.network.simple.SimpleChannel.toVanillaPacket(SimpleChannel.java:129) ~[forge:?]
	at net.minecraftforge.fml.network.simple.SimpleChannel.send(SimpleChannel.java:124) ~[forge:?]
	at com.feed_the_beast.mods.ftbessentials.util.FTBEPlayerData.sendTabName(FTBEPlayerData.java:251) ~[ftbessentials:1604.1.0.13]
	at com.feed_the_beast.mods.ftbessentials.FTBEEventHandler.playerLoggedIn(FTBEEventHandler.java:108) ~[ftbessentials:1604.1.0.13]
	at net.minecraftforge.eventbus.ASMEventHandler_15_FTBEEventHandler_playerLoggedIn_PlayerLoggedInEvent.invoke(.dynamic) ~[?:?]
	at net.minecraftforge.eventbus.ASMEventHandler.invoke(ASMEventHandler.java:85) ~[eventbus-4.0.0.jar:?]
	at net.minecraftforge.eventbus.EventBus.post(EventBus.java:302) ~[eventbus-4.0.0.jar:?]
	at net.minecraftforge.eventbus.EventBus.post(EventBus.java:283) ~[eventbus-4.0.0.jar:?]
	at net.minecraftforge.fml.hooks.BasicEventHooks.firePlayerLoggedIn(BasicEventHooks.java:44) ~[forge:?]
	at net.minecraft.server.management.PlayerList.func_72355_a(PlayerList.java:231) ~[?:?]
	at net.minecraft.network.login.ServerLoginNetHandler.func_147326_c(ServerLoginNetHandler.java:118) ~[?:?]
	at net.minecraft.network.login.ServerLoginNetHandler.func_73660_a(ServerLoginNetHandler.java:65) ~[?:?]
	at net.minecraft.network.NetworkManager.func_74428_b(NetworkManager.java:222) ~[?:?]
	at net.minecraft.network.NetworkSystem.func_151269_c(NetworkSystem.java:134) ~[?:?]
	at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:865) ~[?:?]
	at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:291) ~[?:?]
	at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:787) ~[?:?]
	at net.minecraft.server.MinecraftServer.func_240802_v_(MinecraftServer.java:642) ~[?:?]
	at net.minecraft.server.MinecraftServer.func_240783_a_(MinecraftServer.java:232) ~[?:?]
	at java.lang.Thread.run(Unknown Source) [?:?]
[24May2021 18:07:20.686] [Server thread/INFO] [net.minecraft.network.play.ServerPlayNetHandler/]: Ajhplyr lost connection: Internal server error
[24May2021 18:07:20.687] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: Ajhplyr left the game

Источник

Minecraft is one of the most famous online multiplayer games it contains a huge player base of gamers that absolutely adore its gameplay. However, in this article, we will be addressing the internal server error on Minecraft that some users have been getting while attempting to connect to a server or sometimes even during gameplay.

Minecraft Internal Server Error

What Causes the Internal Server Error on Minecraft?

After going through some basic troubleshooting guides, we concluded that the following are some of the most prominent reasons behind the occurrence of this issue.

Log Files: In some cases, the log files that store the login data for a server might’ve been corrupted due to which it might not have properly registered the persons’ login on the server due to which the internal server error is being triggered on Minecraft.
Mods: In some situations, the mods installed on your game might actually be interfering and preventing some important game files from running properly due to which the internal server error is being triggered. It is best to just check which mods are faulty and are hindering your game from working properly by following the methods below.
Faulty Plugins: It is also possible that you have installed some plugins on your computer that are faulty and due to that, you are facing issues while logging in to the Minecraft server. Therefore, try removing any faulty plugins to fix the Internal Server Error on Minecraft.
Background applications: In some rare occasions, background applications can also prevent Minecraft from being able to properly register with the game servers due to which this issue might be triggered. Therefore, it is also wise to diagnose for any rogue background applications.

Now that you are familiar with most of the reasons behind this particular issue, we will be moving on towards implementing the fixes.

Before you start:

Take the power adapter of your router out of the socket and wait for it to shut down completely.

Plugging out the adapter
After waiting for a couple of minutes, power cycle the router by inserting its power adapters into the socket and wait till it acquires full signals.
Sometimes, this error might occur if the Minecraft servers are under maintenance, If this is the case, then the solution is beyond your control. You can check the server status by visiting the Minecraft server website.

Solution 1: Delete the UUID folder

Open up the server’s log and note down the “UUID” of the person who encountered the error. This UUID will most probably be written in the first line.
Now log in to your server and navigate to the “Server Files”.
Now proceed to the “World” and choose “Players”.
Here, delete the person’s user name and UUID who has encountered the Internal Server Error.
Now restart your PC and connect to the server to check if you come across minecraft internal server error again.

Note: If you don’t want to permanently delete the player who encountered the error, just put them in “Jail” and after they join the server, simply “Unjail” them.

Solution 2: Delete installed Mods

Method 1:

This error might trigger due to some incompatible mods installed on your computer. If you have several different mods installed on your PC, then it is a hectic task to locate the faulty mod and delete it to resolve the issue. So, the most efficient approach is to disable all the mods and enable them one by one to check which one is the backbone of the error. A method to disable the mods in Minecraft is indexed below:

Login to the Minecraft’s “Control Panel” and stop your server.
From the “File” menu, select “FTP File Access” and enter your FTP password.
Choose FTP FIle Access
From the “Server folder” list, click on the “Mods” folder.
Choosing Mods
Now select the mod you want to disable and click on the “Rename” button at the top of the page.
Now add “.disable” at the end of the mod name. (For Example: change “Baubles.jar” to “Baubles.jar.disable”).
Renaming mods
Now “Apply” the changes and exit your FTP connection.
Restart your server and check whether the minecraft internal server error pops up again.

Solution 3: Delete installed Plugins

Press “Win + R” on the keyboard to open the Run box and search for “%appdata%”.

Typing in %appdata%
Now open the “Minecraft” folder and then double-click on the “Plugins” folder to open it.
Select all the files in the “Plugin” folder and hit the “Delete” key on the keyboard to delete all the installed plugins.
After deleting the plugins, login to your Minecraft account and check if you encounter the internal server error minecraft again while connecting to a server.

Solution 4: Close background applications

Press the “Ctrl + Shift + Esc” keys simultaneously on the keyboard to open the “Task Manager”.
Navigate to the “Processes” tab, select all the unwanted processes that might be bandwidth-intensive, one by one, and click on the “End Task” button.

Ending background applications
When the unwanted applications are closed, launch Minecraft on your PC and proceed to connect to a server to check if you encounter this error again.

Solution 5: Edit game’s JSON file

Navigate to the “stats” folder in the game’s server and double-click on the JSON file to open it.
Now scroll down in the file and delete the “stat.killEntity.EntityHorse : 3” entry.
Save the file and launch Minecraft again to check if the internal server error is rectified.

Solution 6: Update Minecraft

Press “Windows key + R” on the keyboard to open the run box and search for “%appdata%”.

Typing in %appdata%
Now locate and double-click on the “.minecraft” folder.
Navigate to the “.version” folder, press “Ctrl + A” from the keyboard, and hit the “Delete” key.
When the deletion process is complete, launch Minecraft to automatically detect the changes and update itself.

Solution 7: Reinstall Minecraft

Press “Windows key + R” from the keyboard to open the run box and search for “appwiz.cpl”.

Typing “appwiz.cpl”
Now locate Minecraft from the list of Softwares installed on your computer, right-click on it and select “Uninstall”.

Uninstalling Minecraft
Now launch a browser and download Minecraft from its official website.
Double-click on the downloaded executable file and follow the on-screen instructions to install the game on your PC.
When the game has been installed successfully, launch it and try to connect to a server and most probably the internal server error minecraft issue would’ve been resolved uptil now.

Workaround:

Press “Ctrl + Shift + Esc” keys on the keyboard to open the task manager and navigate to the “Process” tab.
Here, locate a process related to “JAVA”. If you find that process, right-click on it and set its priority to “High”.
Now press “Windows key + R” on the keyboard to open the run box and search for “%appdata%”.

Typing in %appdata%
Navigate to the “.minecraft” folder and open the “TooManyItems” file with notepad.
In this file, make sure that the “Enable” entry is set to “True”.
Launch Minecraft again and check if the error has been fixed.

If you are still unable to fix this issue, you can contact us for any further assistance.

Источник

Playing Minecraft is a great way to unwind, so being met with a Minecraft internal server error is frustrating, as it thwarts players from accessing their worlds, and continuing their building projects. But rather than find yourself stuck, you’ve done the smart thing, and gone online to find solutions. And that’s why we’re here.

In this article, we’ll explain the most effective ways to resolve the internal server issue on Minecraft. As you’ll find out, the name of the error is a little misleading. Here’s what you need to know.

How To Fix The Minecraft Internal Server Error

There are four widely used methods for fixing this particular problem. Usually, if there is a server-related issue, there isn’t a whole lot you can do about it, other than wait for a fix. However, as we alluded to earlier, while it is described as an internal server error, usually the issue isn’t linked to servers at all. This is good news, because it means you actually have the chance to remedy it yourself.

Read More: Minecraft Outdated Server: How To Fix The Minecraft Outdated Server Error

Before you try any of these fixes, we’d recommend that you are signed in as an administrator on your computer. And double-check that you don’t have any internet connectivity problems. Run through the usual checks — run a speed test, close any other apps or devices that are competing for bandwidth, restart your router, and try switching from WiFi to an Ethernet connection, if possible.

Assuming you’ve done all this, you’re ready to try the following solutions.

Make Sure Minecraft is Fully Updated

If you are using an outdated version of Minecraft, the servers may not recognise it anymore. As a result, the servers will automatically block you if you try to join. It’s important to check that you have updated Minecraft to the latest version of the game.

Delete UUID Folders in Minecraft

One way of fixing this error is by resolving an issue with your Minecraft user profile. But in order to do this, you need to remove your UUID. A UUID is a universally unique identifier — a 128-bit code which identifies you as a user. If this is behind the error, then deleting this data from the server will resolve it.

You can obtain your UUID by visiting this website and entering some details.
Once you have this information, log into the server that is giving you this error. From here, go to Server Files and navigate to the world you want to access.
Select Players, then delete the username and UUID for whoever is experiencing the internal server error.
Once this is done, restart your computer, and try connecting once more.

Look at Your Mods

While mods are a major part of playing Minecraft and add to the experience, they can sometimes be responsible for causing errors. If our first fix didn’t work, then it’s well worth checking any mods that you have. Look to see if any of them have a version mismatch with Minecraft. If they do, then disable or delete the mod, and see if this makes a difference.

Mod developers will usually tell you which Minecraft version they are compatible with, so you can identify which ones may not work. If you have a lot of mods, try disabling them all, then enable them one at a time, to see which ones may be causing this error.

Minecraft internal server error

Credit: Mojang

Check Your Plugins

Much like mods, plugins are a popular way to augment the base-Minecraft experience. But as with mods, they can also cause compatibility problems with the game. It’s well worth repeating the mod fix for any plugins you may have installed.

Start by disabling them all, and then enable them individually and see if any are causing the problem. You can also see which version of the plugin you are using by typing ‘/version’ inside the plugin window. If the version is out of date, you can try updating it and see if this helps.

If All Else Fails

A final fix if none of our previous suggestions has worked, is to try a complete reinstallation of Minecraft. This will often work if your installation files have become corrupted, or some other issue with them has manifested itself.

Make sure you’ve backed up your profile data, and any mods that you want to keep, then complete the following steps:

Press Windows + R, type appwiz.cpl in the dialogue box and press Enter.

Find Minecraft in the application manager, right-click on it and select Uninstall. Alternatively, you can uninstall Minecraft by executing the uninstaller from the folder directory. Remember to delete all the mod files and temporary setting files as well.
Finally, download the game again. This will give you the most up-to-date version of the game, and hopefully resolve the Minecraft internal server error.

If even this doesn’t work, then we recommend contacting Mojang Customer Support for further advice.

What Causes The Minecraft Internal Server Error?

As you’ll have seen, the majority of the time this has very little to do with the servers themselves, and is much more commonly linked to problems with your specific setup. The most common causes are as follows:

An incompatible version of Minecraft, which needs to be updated.
A corrupted installation file.
Incompatible mod packs or plugins.
Corrupted temporary files that prevent Minecraft from running properly

Read More: Minecraft Multiplayer Not Working: How To Fix Minecraft Multiplayer

whatever the underlying reason for the issue in your case, trying the solutions we’ve outlined above will work in the vast majority of cases. And you can get back to building again.

Источник