Solved [video] Unknown Error in Proxy server

Discussion in 'BungeeCord Help' started by phrack_, May 18, 2020.

  1. on Bungee proxy server
    " Could not connect to a default or fallback server "
    The error is displayed.
    This situation is a little special.
    On all fork proxy servers,
    (1.15.2 Assuming Bucket is used)
    The " outdated warning " is not displayed in a lower version than 1.15.2.
    " Could not connect to a default or fallback server "
    The error is displayed.
    However, it is connected well when connecting to 1.15.2.



    Code (YAML):
    server_connect_timeout: 10000
    custom_server_name
    : Phrack - WILD
    forge_support
    : false
    always_handle_packets
    : false
    player_limit
    : -1
    log_pings
    : true
    permissions
    :
      default
    :
     - bungeecord.command.server
      admin
    :
     - bungeecord.command.alert
      - bungeecord.command.end
      - bungeecord.command.ip
      - bungeecord.command.reload
      - bungeecord.command.send
    timeout
    : 30000
    log_commands
    : false
    online_mode
    : true
    disabled_commands
    :
    - op
    servers
    :
      W_latest
    :
        address
    : localhost:20006
        restricted
    : false
        motd
    : "           &8&m&l  &7&m&l   &f&m&l   &f&l|&o&l &7mc.PHRACK.xyz &f&m&l|&f&m&l\
          \   &7&m&l   &8&m&l  \n&7&l              T      E      S      T"

      Lobby
    :
        address
    : localhost:20001
        restricted
    : false
        motd
    : '&1Phrack Server - &c서버 재부팅 중'
    listeners
    :
    - query_port
    : 25577
      motd
    : "           &8&m&l  &7&m&l   &f&m&l   &f&l|&o&l &7mc.PHRACK.xyz &f&m&l|&f&m&l\
        \   &7&m&l   &8&m&l  \n&7&l              W      I      L      D"

      tab_list
    : GLOBAL_PING
      query_enabled
    : true
      proxy_protocol
    : false
      forced_hosts
    :
        mc.phrack.xyz
    : W_latest
      ping_passthrough
    : false
      priorities
    :
     - W_latest
      - Lobby
      bind_local_address
    : true
      host
    : 0.0.0.0:25565
      max_players
    : 30
      tab_size
    : 60
      force_default_server
    : true
    remote_ping_timeout
    : 10000
    ip_forward
    : true
    network_compression_threshold
    : 512
    remote_ping_cache
    : -1
    connection_throttle
    : 10000
    stats
    : 9eeeedb6-107a-4b81-a9a2-f8a3e26aad3f
    connection_throttle_limit
    : 3
    groups
    :
      UBASE
    :
     - admin
      Phrack_
    :
     - admin
      Phrack
    :
     - admin
    prevent_proxy_connections
    : false
     
     
    #1 phrack_, May 18, 2020
    Last edited: May 18, 2020
  2. [SOLVED]
    I turned on the priority "Lobby" server only when I restart the server.
    The proxy has expelled a lower version of the client from the W_latest server (outdated)
    Connect to disabled Lobby
    Therefore, the above message is displayed.
    Perhaps this problem was previously accessible in most versions of the viaversion plugin.
    I think this misunderstanding occurred because the update of spigot(or viaversion) did not provide protocol support and could not be accessed from an old client.