Server not connectable

    Rebooted my server today and found that my Rising World server isn't connectable.


    Error log:


    Rising World - 0.5.7.3 - Dedicated Server
    Linux 3.13.0-53-generic Java 1.8.0
    06/02/2015 07:09 PM


    Items initialized!
    Plants initialized!
    NPCs initialized!
    Initialize Static Classes...
    Constructions initialized!
    Objects initialized!
    Picking initialized!
    Food-Definitions initialized!
    Crafting-Definitions initialized!
    06/02/2015 07:09 PM z.g
    INFO: Register BuildDestroyPermission: object.plank
    06/02/2015 07:09 PM z.g
    INFO: Register BuildDestroyPermission: ores.copper
    06/02/2015 07:09 PM z.g
    INFO: Register BuildDestroyPermission: world.dirt
    06/02/2015 07:09 PM z.g
    INFO: Register BuildDestroyPermission: world.stone
    06/02/2015 07:09 PM z.g
    INFO: Register MainPermission: permission.changespawn
    LOAD WORLD New World
    DATABASE TYPE: SqLite
    /home/kayfanx/server/Worlds/New World:::New World
    CREATE WORLD STRUCTURE - DONE!
    Load world New World
    WORLDINFO Seed :1433114703114
    WORLDINFO Caves :true
    WORLDINFO Vegetations :true
    WORLDINFO Worldtype :Normal
    WORLDINFO Time :8.1.0 0:36:0.9106524
    set game time: 8.1.0 0:36:0.9106524
    WORLDINFO Spawninventory :2 0 0 23 0 1 -65 -128 0 0 0 1 0 17 0 1 -65 -128 0 0 0 0 0 0
    Worldpart generating...
    Biomepart generating...
    Biomepart generated: 0 - 0
    CavePoints: 377874
    Worldpart generated: 0 - 0
    WORLDINFO Version :0.5.7.3_19
    Worldconverter: Updating not required
    WORLDINFO Spawnposition :256.0 153.0 256.0
    WORLDINFO Spawnrotation :0.0 0.0 0.0 1.0
    dir does not exist: Worlds/New World/customImages/
    2 chests loaded from DB!
    0 Plants loaded from DB!
    1 Furnaces loaded from DB!
    21 NPCs loaded from DB!
    STARTING RISING WORLD SERVER...
    Server bind to IP: ***.***.****.***:4255
    06/02/2015 07:09 PM commons.util.Utils
    SEVERE: Unable to determine mac address: java.lang.NullPointerException
    StartUp TcpKernel Port: 4255
    StartUp UdpKernel Port: 4255
    StartUp UdpKernel Port: 4256
    StartUp TcpKernel Port: 4256
    StartUp UdpKernel Port: 4257
    StartUp TcpKernel Port: 4257
    StartUp TcpKernel Port: 4258
    CREATED SERVER SAVE THREAD
    RISING WORLD SERVER STARTED
    START
    /home/kayfanx/server/scripts
    HTTP Server bind to IP: 0.0.0.0:4254
    06/02/2015 07:09 PM server.Main
    INFO: Server successfully authenticated!
    *************** NEW THREAD LOCAL ALLOCATION ***************
    dispatch: ClientRegisterMessage
    NEXT CLIENT ID: 1
    *************** NEW THREAD LOCAL ALLOCATION ***************
    06/02/2015 07:11 PM x.c
    INFO: dispatch: ClientRegisterChannelMessage TCP Port:4257
    dispatch: ClientRegisterChannelMessage TCP Port:4256
    dispatch: ClientRegisterChannelMessage TCP Port:4258
    SET HOSTED CONNECTION FOR CHANNEL: 3 de.jiw.network.base.HostedConnection@332412ee
    SET HOSTED CONNECTION FOR CHANNEL: 6 de.jiw.network.base.HostedConnection@332412ee
    *************** NEW THREAD LOCAL ALLOCATION ***************
    SET HOSTED CONNECTION FOR CHANNEL: 5 de.jiw.network.base.HostedConnection@332412ee
    ConnectionPending: 1


    *************** NEW THREAD LOCAL ALLOCATION ***************
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    *************** NEW THREAD LOCAL ALLOCATION ***************
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    *************** NEW THREAD LOCAL ALLOCATION ***************
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    *************** NEW THREAD LOCAL ALLOCATION ***************
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    dispatch: ClientRegisterChannelMessage UDP Port:4256
    dispatch: ClientRegisterChannelMessage UDP Port:4255
    dispatch: ClientRegisterChannelMessage UDP Port:4257
    ///////////////////////////////////////////////////
    ///////////////////////////////////////////////////
    ///////////////////////////////////////////////////
    ///////////////////////////////////////////////////
    DISCONNECT Port: 4258 Channel: java.nio.channels.SocketChannel[connected local=/192.168.2.167:4258 remote=/192.168.2.51:11337] HostedConnection: de.jiw.network.base.HostedConnection@332412ee false false
    ///////////////////////////////////////////////////
    DISCONNECT Port: 4257 Channel: java.nio.channels.SocketChannel[connected local=/192.168.2.167:4257 remote=/192.168.2.51:11336] HostedConnection: de.jiw.network.base.HostedConnection@332412ee false false
    ///////////////////////////////////////////////////
    DISCONNECT Port: 4256 Channel: java.nio.channels.SocketChannel[connected local=/192.168.2.167:4256 remote=/192.168.2.51:11335] HostedConnection: de.jiw.network.base.HostedConnection@332412ee false false
    ///////////////////////////////////////////////////
    pendingCloseEvents.add 4256
    closeConnection
    TCP ENDPOINT CLOSE
    TCP ENDPOINT CLOSE
    TCP ENDPOINT CLOSE
    TCP ENDPOINT CLOSE
    pendingCloseEvents.add 4258
    pendingCloseEvents.add 4257
    DISCONNECT Port: 4255 Channel: java.nio.channels.SocketChannel[connected local=/192.168.2.167:4255 remote=/192.168.2.51:11334] HostedConnection: de.jiw.network.base.HostedConnection@332412ee false false
    ///////////////////////////////////////////////////
    SERVER: TcpKernel gracefully disconnected
    pendingCloseEvents.add 4255


    I have reinstalled the server and it still does the above while trying to connect to the server.

    It seems that the client cannot establish an UDP connection to the server. Is the server running on a dedicated server? Can other clients connect to that server?
    It could be either an issue with the server (but then nobody should be able to connect), or with your client (a firewall/antivirus program might be blocking the connection).

    Quote from red51

    It seems that the client cannot establish an UDP connection to the server. Is the server running on a dedicated server? Can other clients connect to that server?
    It could be either an issue with the server (but then nobody should be able to connect), or with your client (a firewall/antivirus program might be blocking the connection).


    It is a dedicated server yeah.


    Eventually fixed it with a full server restart.

Participate now!

Don’t have an account yet? Create a new account now and be part of our community!

Create Account Login