BungeeCord: Could not connect to default server: java.net.ConnectException

Discussion in 'BungeeCord Discussion' started by matzefratze123, Jun 18, 2013.

  1. Hello,

    I just got a little problem, setting up bungeecord on my vServer. Every time I try to connect to my lobby server it says me: Could not connect to default server: java.net.ConnectException. I also sometimes get a bad packet id error while logging in.

    I'm using BungeeCord git-BungeeCord-Proxy-1.5-SNAPSHOT-"22133bc"-537. Also my lobby server is set to offline mode and the connection throttle is set to -1. The lobby server is running on port 25566. I also configured it in the Bungee config.yml that my lobby server is running on port 25566. BungeeCord self is running on port 25565 (default port).

    Here is my Bungee config:
    Code (Text):
    groups:
      md_5:
      - admin
      matzefratze123:
      - admin
    player_limit: -1
    stats: 013da7b3-757c-46c5-858f-01fb1e6a1615
    permissions:
      default:
      - bungeecord.command.server
      - bungeecord.command.list
      admin:
      - bungeecord.command.alert
      - bungeecord.command.end
      - bungeecord.command.ip
      - bungeecord.command.reload
    listeners:
    - fallback_server: lobby
      max_players: 1000
      #212.224.126.25:25565
      host: 212.224.126.25:25565
      tab_size: 60
      force_default_server: true
      texture_size: 16
      tab_list: GLOBAL_PING
      motd: '§e§l<§6PvP-Server Memorian§e§l> §r§a1.5.2'
      default_server: lobby
      forced_hosts:
        pvp.md-5.net: pvp
    timeout: 30000
    servers:
      lobby:
        address: localhost:25566
        restricted: false
    online_mode: true

    And here my Bungee log:

    Code (Text):
    16:07:12 [INFO] Enabled BungeeCord version git-BungeeCord-Proxy-1.5-SNAPSHOT-"22133bc"-537
    16:07:12 [INFO] Listening on /212.224.126.25:25565
    16:07:17 [INFO] [matzefratze123] <-> InitialHandler has connected
    16:07:19 [INFO] [matzefratze123] disconnected with: ?cCould not connect to default server, please try again later: java.net.ConnectException
    16:07:19 [INFO] [matzefratze123] -> UpstreamBridge has disconnected
    16:07:32 [INFO] [matzefratze123] <-> InitialHandler has connected
    16:08:02 [INFO] [matzefratze123] <-> InitialHandler has connected
    16:08:02 [INFO] [matzefratze123] disconnected with: ?cCould not connect to default server, please try again later: java.net.ConnectException
    16:08:02 [INFO] [matzefratze123] -> UpstreamBridge has disconnected
    16:08:05 [INFO] [matzefratze123] <-> InitialHandler has connected
    16:08:12 [INFO] [matzefratze123] <-> InitialHandler has connected
    16:08:13 [INFO] [matzefratze123] disconnected with: ?cCould not connect to default server, please try again later: java.net.ConnectException
    16:08:13 [INFO] [matzefratze123] -> UpstreamBridge has disconnected
    16:08:16 [INFO] [matzefratze123] <-> InitialHandler has connected
    16:08:16 [INFO] [matzefratze123] disconnected with: ?cCould not connect to default server, please try again later: java.net.ConnectException
    16:08:16 [INFO] [matzefratze123] -> UpstreamBridge has disconnected
    16:08:19 [INFO] [matzefratze123] <-> InitialHandler has connected
     

    Spigot Version: git-Spigot-937

    I'm appreciative for any help :)

    Regards,
     
  2. i had that problem. but do you have 2 server? because if so (i dont know if this is the best idea) but you can always have the hub server in the server list (that will make you connect to the server on the list) but if you want. pm me and i might be able to help you with this :)
     
  3. I only use one server at this time (the hub server). I wanted to test out BungeeCord but it just won't work. I also tried setting up BungeeCord on my PC and it works great, but not on my vServer.
     
  4. Are you just trying to connect to your host server?
     
  5. Ok I solved the problem myself. For anyone who has the same problem:

    Your target servers address can not be localhost. Use your IP and it will work :)

    Edit: But now I got another problem. Sometimes it happens that I get a bad packet id message upon login. I'm on the newest bungeecord and spigot version...
     
    #5 matzefratze123, Jun 19, 2013
    Last edited: Jun 19, 2013
  6. The new spigot version causes this often it has been reported and md_5 knows about this downgrade your spigot or live with it until md_5 fixes this.
     
  7. Try build #514 for Bungee and #934 for Spigot.

    From: http://www.spigotmc.org/threads/long-live-spigot-first-milestones.2775/
     
    • Like Like x 1
  8. All is working perfectly now. Thanks to all who helped :)
     
  9. Which build did you settle on/did you try #934?

    From #933 to #934 the change apparently was: "Downgrade network engine to fix reliability issues". I am surprised LithiumSyntax had trouble with #934? I would expect #934 to have a network engine from a previous working version etc.
     

  10. This is what i thought but when i used #934 i got a lot of bad packet id's with #933 i get the occasional but not that bad apparently its based on your system and how its setup according to md_5
     
  11. I'm using spitgot build #934 and it works without any problems...
     

  12. Good for you its based on your system setup its different for a few people.
     
  13. thx it really helped