Cannot join local server

  • Tech Support section is for getting help with FTB related problems. If there's a repeatable issue that can be labeled as a bug, then please use the issue tracker for the pack or the app at GitHub issue trackers - If there's no repository for a pack that means that the pack is old and/or will not be updated. Bugs for older packs will not be fixed, unless they are critical.
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
K

KasStrider

Guest
Title Cannot join local server

Launcher Type FTB Launcher

Modpack SkyFactory 3

Modpack version

Have you modified the pack? No

Link to log file http://paste.feed-the-beast.com/view/dc755b56

Details of the issue Was running a local server for SkyFactory, on the off chance any friends wanted to hop in. Things were going fine, but the game suddenly crashed when I attempted to put on a stone helmet. Since then, I get the follwoing error from Minecraft when attempting to join the server:

Internal Exception: java.io.IOException: An established connection was aborted by the software in your host machine

In the log, I see my character joining the game, then the following red error message appears:

{Netty Client IO 2/ERROR} {FML}: NetworkDispatcher exception

There is an additional yellow error message that appears prior to the previous message:

[Netty Client IO #2/WARN] [journeymap]: dim0 (Initialized) Bad configField entry during updateFrom(): enabled=null

The full log is linked, but those are the messages (specifically, the first one I mentioned) that I believe are relevant.

Running Windows 10 and I do have an NVidia graphics card, but I did not see this problem mentioned anywhere in that thread.
 
Last edited by a moderator:
K

KasStrider

Guest
Update: Tried it again after a couple computer restarts, and instead of the previously mentioned error message, the connection simply timed out (according to Minecraft). Subsequent attempts gave the original error message.