Fresh bungee installation, fresh spigot, Users cannot connect; NativeIOException?

Discussion in 'BungeeCord Help' started by Kato, Aug 12, 2016.

  1. Hey people,

    Have a fresh server with BungeeCord (latest, and tried an older version) with spigot. The configuration hasn't changed at all for me, though it's an older server I haven't been on in a while.

    When players connect they get this issue:

    Code (Text):
    17:46:42 [INFO] Listening on /0.0.0.0:25565                                                                                                                                                                 │
    17:46:42 [INFO] Started query on /0.0.0.0:25565                                                                                                                                                             │
    17:46:46 [INFO] [/174.4.47.37:35690] <-> InitialHandler has connected                                                                                                                                       │
    17:46:47 [INFO] [kato233] <-> ServerConnector [hub] has connected                                                                                                                                           │
    17:46:47 [WARNING] [kato233] <-> ServerConnector [hub] - IOException: syscall:read(...)() failed: Connection reset by peer                                                                                  │
    17:46:47 [INFO] [kato233] disconnected with: Exception Connecting:NativeIoException : syscall:read(...)() failed: Connection reset by peer @ io.netty.channel.unix.FileDescriptor:-1                        │
    17:46:47 [INFO] [kato233] <-> ServerConnector [hub] has disconnected                                                                                                                                        │
    17:46:48 [INFO] [kato233] -> UpstreamBridge has disconnected
    Anyone have any experience with this? No googling helped me out.
     
  2. change 0.0.0.0 to your gateway ip
     
  3. try to put ipforwarding on false. I had the same problem, but doing so I solved it
     

Share This Page