What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Connection closed! [TCP-E-S] 0.0.0.0:0

Status
Not open for further replies.

Jet8

Member
Joined
Dec 8, 2011
Messages
106
Reaction score
2
when i turn on Fate bot, i get this message spammed in my console. When i click stop, it doesn't stop the bot, but when i click it a second time the bot crashes.

"Connection closed! [TCP-E-S] 0.0.0.0:0.............." the last part looks like my IP
 
when i turn on Fate bot, i get this message spammed in my console. When i click stop, it doesn't stop the bot, but when i click it a second time the bot crashes.

"Connection closed! [TCP-E-S] 0.0.0.0:0.............." the last part looks like my IP

Same is happening with me, been so for almost 45 minutes now. Aggravating...
 
So is the server still down or what? It's been a few hours now with no news. Still getting errors:

Code:
[04:55:27.252 N] Connection closed! [TCP-E-S] 0.0.0.0:0 -> 192.99.148.87:31214
[04:55:27.412 N] Connection established! [TCP-E-E] 192.168.1.2:49231 -> 192.99.148.87:31213 (7j6Ecr6fdE24u2duTHAQpw)
[04:55:27.415 D] NetworkCommsDotNet.ConnectionSetupException: Error during TCP connection establish with destination ([TCP-E-S] 0.0.0.0:0 -> 192.99.148.87:31214). Destination may not be listening or connect timed out. NetworkCommsDotNet.ConnectionSetupException: Timeout waiting for remoteEndPoint to accept TCP connection.
   at NetworkCommsDotNet.Connections.TCP.TCPConnection.ConnectSocket()
   at NetworkCommsDotNet.Connections.TCP.TCPConnection.ConnectSocket()
   at NetworkCommsDotNet.Connections.TCP.TCPConnection.EstablishConnectionSpecific()
   at NetworkCommsDotNet.Connections.Connection.EstablishConnection()
   at NetworkCommsDotNet.Connections.TCP.TCPConnection.GetConnection(ConnectionInfo connectionInfo, SendReceiveOptions defaultSendReceiveOptions, TcpClient tcpClient, Boolean establishIfRequired, SSLOptions sslOptions)
   at Š...ctor()
   at ff14bot.Navigation.GaiaNavigator..ctor(Single pathPrecision)
   at ff14bot.BotBases.FateBot.Start()
   at ff14bot.TreeRoot.()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
 
So is the server still down or what? It's been a few hours now with no news. Still getting errors:

Code:
[04:55:27.252 N] Connection closed! [TCP-E-S] 0.0.0.0:0 -> 192.99.148.87:31214
[04:55:27.412 N] Connection established! [TCP-E-E] 192.168.1.2:49231 -> 192.99.148.87:31213 (7j6Ecr6fdE24u2duTHAQpw)
[04:55:27.415 D] NetworkCommsDotNet.ConnectionSetupException: Error during TCP connection establish with destination ([TCP-E-S] 0.0.0.0:0 -> 192.99.148.87:31214). Destination may not be listening or connect timed out. NetworkCommsDotNet.ConnectionSetupException: Timeout waiting for remoteEndPoint to accept TCP connection.
   at NetworkCommsDotNet.Connections.TCP.TCPConnection.ConnectSocket()
   at NetworkCommsDotNet.Connections.TCP.TCPConnection.ConnectSocket()
   at NetworkCommsDotNet.Connections.TCP.TCPConnection.EstablishConnectionSpecific()
   at NetworkCommsDotNet.Connections.Connection.EstablishConnection()
   at NetworkCommsDotNet.Connections.TCP.TCPConnection.GetConnection(ConnectionInfo connectionInfo, SendReceiveOptions defaultSendReceiveOptions, TcpClient tcpClient, Boolean establishIfRequired, SSLOptions sslOptions)
   at Š...ctor()
   at ff14bot.Navigation.GaiaNavigator..ctor(Single pathPrecision)
   at ff14bot.BotBases.FateBot.Start()
   at ff14bot.TreeRoot.()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

It seems that way. Just be patent and I'm sure Mastahg will have a fix soon.
 
Status
Not open for further replies.
Back
Top