[Twinsen] [0.15.6] Multiplayer won't connect properly: "invalid state for packet type"

Bugs that we were not able to reproduce, and/or are waiting for more detailed info.
Post Reply
tcjn
Manual Inserter
Manual Inserter
Posts: 4
Joined: Wed Mar 30, 2016 6:37 pm
Contact:
Contact tcjn

[Twinsen] [0.15.6] Multiplayer won't connect properly: "invalid state for packet type"

Post by tcjn »

When I try to connect to a server through the matching server I get the error "Couldn't establish network communication with server."

From client logs:

Code: Select all

10123.898 Joining game 80.229.224.55:34197
10123.898 Info UDPSocket.cpp:33: Opening socket
10123.899 Info ClientMultiplayerManager.cpp:539: MapTick(-1) changing state from(Ready) to(Connecting)
10123.915 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ConnectionRequestReply) received from 80.229.224.55:34197: invalid state for packet type
10123.931 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10123.931 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10123.965 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10123.965 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10123.999 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10123.999 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.032 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.032 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.065 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.065 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.099 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.099 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.131 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.131 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.165 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.165 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.199 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.199 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.232 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.232 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.282 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.282 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.316 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.316 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.331 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.332 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.366 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.366 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.415 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.415 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.450 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.450 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.499 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.499 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.515 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.515 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.565 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.565 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.598 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.598 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.649 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.649 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.682 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.682 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.732 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.732 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.765 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.765 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.815 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.815 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.848 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.848 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.898 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.898 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.932 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.932 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.981 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10124.982 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10125.015 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10125.015 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10125.065 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10125.065 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10125.098 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10125.098 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10125.148 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10125.148 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10125.181 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10125.181 Info UnparsedNetworkMessage.cpp:87: Invalid packet (type ServerToClientHeartbeat) received from 80.229.224.55:34197: invalid state for packet type
10125.215 Error ClientMultiplayerManager.cpp:90: MultiplayerManager failed: multiplayer.not-received-connection-accept-reply
10125.215 Info ClientMultiplayerManager.cpp:539: MapTick(-1) changing state from(Connecting) to(InitializationFailed)
10677.416 Info ClientMultiplayerManager.cpp:177: Quitting multiplayer connection.
10677.416 Info ClientMultiplayerManager.cpp:539: MapTick(-1) changing state from(InitializationFailed) to(Disconnected)
10677.466 Info UDPSocket.cpp:234: Socket closed
From server logs:

Code: Select all

 997.014 ConnectionRequestReplyConfirm (type(ConnectionRequestReplyConfirm) ) from(10.100.0.1:58476)
 997.014 Info ServerRouter.cpp:389: Replying to connectionRequest for address(10.100.0.1:58476).
 997.014 Info ServerSynchronizer.cpp:521: nextHeartbeatSequenceNumber(28371) adding peer(4)
 997.031 Info ServerMultiplayerManager.cpp:663: mapTick(20302) changing state from(InGame) to(InGameSavingMap)
 997.266 ConnectionRequestReplyConfirm (type(ConnectionRequestReplyConfirm) ) from(10.100.0.1:58476)
 997.266 Info ServerRouter.cpp:389: Replying to connectionRequest for address(10.100.0.1:58476).
 997.412 Info ServerMultiplayerManager.cpp:801: MapTick(20302) Serving map(/factorio/factorio/temp/mp-save-3.zip) for peer(4) size(2836116) crc(2653878493)
 997.412 Info ServerMultiplayerManager.cpp:663: mapTick(20302) changing state from(InGameSavingMap) to(InGame)
 997.513 ConnectionRequestReplyConfirm (type(ConnectionRequestReplyConfirm) ) from(10.100.0.1:58476)
 997.513 Info ServerRouter.cpp:389: Replying to connectionRequest for address(10.100.0.1:58476).
 997.784 ConnectionRequestReplyConfirm (type(ConnectionRequestReplyConfirm) ) from(10.100.0.1:58476)
 997.784 Info ServerRouter.cpp:389: Replying to connectionRequest for address(10.100.0.1:58476).
 998.035 ConnectionRequestReplyConfirm (type(ConnectionRequestReplyConfirm) ) from(10.100.0.1:58476)
 998.035 Info ServerRouter.cpp:389: Replying to connectionRequest for address(10.100.0.1:58476).
1023.014 Info ServerMultiplayerManager.cpp:846: Disconnect notification for peer (4)
1023.014 Info ServerSynchronizer.cpp:537: nextHeartbeatSequenceNumber(29015) removing peer(4).
Top
Oxyd
Former Staff
Former Staff
Posts: 1428
Joined: Thu May 07, 2015 8:42 am
Contact:
Contact Oxyd

Re: [0.15.6] Multiplayer won't connect properly: "invalid state for packet type"

Post by Oxyd »

Hello, can you post the complete logs? Does this happen every time you try to connect to the server?
Top
tcjn
Manual Inserter
Manual Inserter
Posts: 4
Joined: Wed Mar 30, 2016 6:37 pm
Contact:
Contact tcjn

Re: [0.15.6] Multiplayer won't connect properly: "invalid state for packet type"

Post by tcjn »

It happens every time, but only when a certain amount of mods are present, which varies depending on the mods. Unfortunately I don't have the logs anymore but I'll try and reproduce.
Top
tcjn
Manual Inserter
Manual Inserter
Posts: 4
Joined: Wed Mar 30, 2016 6:37 pm
Contact:
Contact tcjn

Re: [0.15.6] Multiplayer won't connect properly: "invalid state for packet type"

Post by tcjn »

After further diagnosis I have come to the conclusion that it's related to my network setup due to testing a set of mods which are known working on another person's server. Would be grateful for some explanation as to what these messages actually mean (in terms of packets over the network) to help diagnosing the problem.
Top
Oxyd
Former Staff
Former Staff
Posts: 1428
Joined: Thu May 07, 2015 8:42 am
Contact:
Contact Oxyd

Re: [0.15.6] Multiplayer won't connect properly: "invalid state for packet type"

Post by Oxyd »

Can you post your mod folder, then?

The messages mean the server is sending packets the client doesn't expect. The log files aren't really mean to be helpful to the end-user.
Top
tcjn
Manual Inserter
Manual Inserter
Posts: 4
Joined: Wed Mar 30, 2016 6:37 pm
Contact:
Contact tcjn

Re: [0.15.6] Multiplayer won't connect properly: "invalid state for packet type"

Post by tcjn »

https://www.dropbox.com/s/7bpk9vcbdsq2m ... s.zip?dl=0
This set of mods, with the mod-list.json works. Enable one more and it doesn't.

https://www.dropbox.com/s/1p4z81m558pwi ... s.zip?dl=0
This is a set of mods which run and work on KatherineOfSky's community server. Note that I am also unable to connect to said server.
Top
Twinsen
Factorio Staff
Factorio Staff
Posts: 1330
Joined: Tue Sep 23, 2014 7:10 am
Contact:
Contact Twinsen

Re: [Twinsen] [0.15.6] Multiplayer won't connect properly: "invalid state for packet type"

Post by Twinsen »

Sorry for the late reply.

Unfortunately we can't figure out what is going wrong.

If you can still reproduce the problem, ideally you should find the case where it does not work, and send us a wireshark capture(in private) of both the server and the client, along with the server and client logs when the problem happens.
Top
Post Reply

Return to “Pending”