Jump to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

Posted

As title, players are unable to connect to the server with mod installed on both sides. (I've tested myself on my two laptops and one of them work, one of they don't)

Client shows: "An established connection was aborted by the software in your host machine (but it works fine to join other server)", on Server it just says "Took too long to log in", anyways, debug logs:

Some of the names and information are change due to privacy (logs provided by other user)

Server Debug Log: https://pastebin.com/3WJjwV8M

Client Debug Log: https://pastebin.com/yVd5nxWP

Repository: https://bitbucket.org/kaneka/planttech2/src/1.16.x/

 

Thanks in advance.

Edited by poopoodice

  • Author

Update:

It is still not working after I disabled nearly all features in the mod, but we got more testing results coming out:

 

If A create the world and open to lan:

B can't connect.

If B creates the world and opens to lan:

A can connect.

 

If A host the local server:

B can't connect

If B host the local server:

A can connect, but B cannot.

 

It is really confusing because it sounds like a hardware problem but it happens on some other players as well, the client log always shows:

[Netty Client IO #0/DEBUG] [ne.mi.fm.ne.FMLHandshakeHandler/FMLHANDSHAKE]: Registry load complete, continuing handshake.
[Netty Client IO #0/DEBUG] [ne.mi.fm.ne.FMLLoginWrapper/FMLHANDSHAKE]: Dispatching wrapped packet reply for channel fml:handshake with index 18
[Netty Client IO #0/DEBUG] [ne.mi.fm.ne.FMLLoginWrapper/FMLHANDSHAKE]: Recieved login wrapper packet event for channel fml:handshake with index 19
[Netty Client IO #0/DEBUG] [ne.mi.fm.ne.FMLHandshakeHandler/FMLHANDSHAKE]: Received config sync from server
[Netty Client IO #0/DEBUG] [ne.mi.fm.ne.FMLLoginWrapper/FMLHANDSHAKE]: Dispatching wrapped packet reply for channel fml:handshake with index 19

and just stuck

and the server always shows

[Netty Server IO #3/DEBUG] [ne.mi.fm.ne.FMLLoginWrapper/FMLHANDSHAKE]: Recieved login wrapper packet event for channel fml:handshake with index 17
[Netty Server IO #3/DEBUG] [ne.mi.fm.ne.FMLHandshakeHandler/FMLHANDSHAKE]: Received client indexed reply 17 of type net.minecraftforge.fml.network.FMLHandshakeMessages$C2SAcknowledge
[Netty Server IO #3/DEBUG] [ne.mi.fm.ne.FMLHandshakeHandler/FMLHANDSHAKE]: Received acknowledgement from client
[Server thread/DEBUG] [ne.mi.fm.ne.FMLHandshakeHandler/FMLHANDSHAKE]: Sending ticking packet info 'Registry minecraft:entity_type' to 'fml:handshake' sequence 18
[Server thread/DEBUG] [ne.mi.fm.ne.FMLHandshakeHandler/FMLHANDSHAKE]: Sending ticking packet info 'Config planttech2-server.toml' to 'fml:handshake' sequence 19
[Server thread/DEBUG] [ne.mi.fm.ne.FMLHandshakeHandler/FMLHANDSHAKE]: Sending ticking packet info 'Config forge-server.toml' to 'fml:handshake' sequence 20
[Server thread/INFO] [minecraft/ServerLoginNetHandler]: Disconnecting com.mojang.authlib.GameProfile@42dc9d62[id=380df991-f603-344c-a090-369bad2a924a,name=Dev,properties={},legacy=false] (/10.0.0.204:56686): Took too long to log in

and then the player got kicked.

Also I'm certain it is not the mod config's problem because the problem persists even if it is disabled.

Edited by poopoodice

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.