Auto reconnect не работает

Captan_cat

Пользователь
Сообщения
1
Плагин
Bungee-Reconnect-1.3.5
Ядро сервера
  1. Paper
  2. Bungeecord
Версия сервера
  1. 1.20
Здравствуйте. у меня есть 2 сервера, первый выживание, второй bungee прокси, на bungee стоит плагин auto reconnect. Но при перезагрузке основного он кикает с сообщением:
> 13:58:19 [INFO] [Captan_Cat_] disconnected with: Could not connect to a default or fallback server, please try again later: io.netty.channel.AbstractChannel$AnnotatedConnectException
> 13:58:19 [INFO] [Captan_Cat_] -> UpstreamBridge has disconnected

и не даёт подключится с таким же.

Конфиг Reconnect:

Код:
# Reconnect --- config file

# In this file, you can setup some basic settings for the plugin.



# The current version of this configuration. Do NOT change this value!

# If the plugin uses a more recent config version, this config gets replaced by it

#   while a backup of the old config will be kept as "config.old.ver.<OLD VERSION>.yml".

version: 14



# Should debugging messages be shown?

debug: true



# This is for configuring custom animations.

Animations:

  # This is the placeholder of the animation.

  # It will be replaced with the correct animation when it is found in a value that supports animations

  "%dots%":

    # At what frequency should the animation play

    # 1000 = 1 change per second

    # Minimum value is update-rate

    Delay Millis: 1000

    # The animation itself

    # You may use the %playerName% placeholder in animations

    Animation:

    - "&b.&7.."

    - "&7.&b.&7."

    - "&7..&b.&7"

 



# This value should not be changed unless you are experiencing issues with titles "flickering" on bedrock clients

# In which case you should change this value to 1 second (1000)

# Minimum value is 50 Maximum value is 5000

update-rate: 50



# The text that should be displayed, when the plugin is trying to reconnect a player.

# Leave empty if you don't wish any title or action bar message to be displayed.

reconnecting-text:

  # You can add animations to the reconnecting texts by using the animations placeholder.

  title: "&cRestarting%dots%"

  subtitle: "&ePlease wait."

  actionbar: "&bYou will be &aautomatically reconnected &bin a few moments"



# The text that should be displayed, when the plugin managed to establish a connection to the previous server.

# Leave empty if you don't wish any title or action bar message to be displayed.

connecting-text:

  title: "&aReconnecting%dots%"

  subtitle: "&ePlease wait."

  actionbar: "&aReconnecting to server%dots%"



# The text that should be displayed, when the plugin didn't manage to

#   establish a connection to the previous server within time limits and connected the player to the fallback server.

# Includes a kick message in the event of no fallback server being found.

# Leave empty if you don't wish any title or action bar message to be displayed.

failed-text:

  title: "&4Failed"

  subtitle: "&cTry to join again in a few moments."

  actionbar: "&bYou have been moved to the fallback server!"

  kick-message: "&4Reconnection failed. Please try again later."



# The amount of milliseconds the plugin will wait before attempting to check if the server is alive.

# This can be zero, however if you use an automatic restart plugin that kicks players

#   reconnect may actually reconnect them before the server stops accepting new connections. This may cause unstable behavior.

delay-before-trying: 10000



# The amount of milliseconds the plugin will wait between each new connection attempt per player - per server.

# Depending on server size and hardware having 20+ people reconnect at once can cause issues in the game, plugins and or databases.

# if your server ends up hanging when people are reconnecting this (can) be an indicator that this value is too low

#   or that the hardware your server is running on is too weak and or that the plugins/server are badly optimized.

#   Also be sure to see connect-finalization-timeout

# Recommended value is 1000

delay-between-reconnects: 1000



# How much MORE time between reconnects should we wait for a connection to finalize.

# A connection is considered "finalized" once the server sends a dimension to the client.

# This "can" help in preventing server overloads before allowing another reconnect attempt.

# However you should still set delay-between-reconnects to a reasonable value in-case of plugins sending

#   dimension changes to the client and or to issues (see above)

# Recommended value is 2000

connect-finalization-timeout: 2000



# The amount of milliseconds the plugin will wait for the proxy-server connection to establish, before it decides to try again.

# Note: If a connection is not finalized within this timeframe another attempt will be made.

# Any reconnect that times out will be chucked back at the start of the reconnect queue.

# Cannot be less then 2000 + connect-finalization-timeout

# Recommended value is 6000

reconnect-timeout: 6000



# The maximum amount of time the plugin will wait to connect everyone.

# If this time limit is reached the plugin will first attempt to connect them to your fallback-server otherwise kicking them.

# This value cannot be less than delay-before-trying + reconnect-timeout.

# The default value is 240000 (240 seconds) if your server takes longer to restart and connect everyone set this higher.

# be mindful to set this value high enough to also accommodate for delay-between-reconnects.

max-reconnect-time: 240000



# Control what servers users are automatically reconnected to.

servers:

  # Blacklist & Whitelist mode

  mode: whitelist

  # The list of servers to apply the filter to

  list:

    - 135.181.126.139:25794

    - "some_other_server"



# This block is necessary for the plugin to differentiate whether a kick happened because of a shutdown or not.

shutdown:

  # Note: Formatting codes (color codes) will be ignored here. So don't include them.

  # When regex is set to false, the kick message must be equal to the following text if the player should be reconnected to that server.

  # When regex is set to true, the regex must match the kick message if the player should be reconnected to that server.

  # Leaving the text empty will lead the plugin to always reconnect the players, no matter what the actual kick-reason was.



  # You can still use the "ServerReconnectEvent" as a plugin developer to decide on your own whether the user should be reconnected automatically

  # or not.



  # Default value: ((?i)(server closed|server is restarting))+$

  text: "((?i)(server closed|server is restarting))+$"

  regex: true



Конфиг bungee:



server_connect_timeout: 5000

listeners:

- query_port: 25887

  motd: '&1Another Bungee server'

  tab_list: GLOBAL_PING

  query_enabled: false

  proxy_protocol: false

  forced_hosts:

    f16.joinserver.ru: 135.181.126.139:25975

  ping_passthrough: false

  priorities:

  - lobby

  bind_local_address: true

  host: 0.0.0.0:25887

  max_players: 1

  tab_size: 60

  force_default_server: false

remote_ping_cache: -1

network_compression_threshold: 256

permissions:

  default:

  - bungeecord.command.server

  - bungeecord.command.list

  admin:

  - bungeecord.command.alert

  - bungeecord.command.end

  - bungeecord.command.ip

  - bungeecord.command.reload

log_pings: true

connection_throttle_limit: 3

prevent_proxy_connections: false

timeout: 30000

player_limit: -1

ip_forward: false

groups:

  md_5:

  - admin

remote_ping_timeout: 5000

connection_throttle: 4000

log_commands: false

stats: 8b2d8aa3-4763-42ce-b75e-3dc93c4f3240

online_mode: false

forge_support: false

disabled_commands:

- disabledcommandhere

servers:

  lobby:

    motd: '&1Just another BungeeCord - Forced Host'

    address: 135.181.126.139:25975

    restricted: false
 

Вложения

  • proxylog.txt
    109.7 KB · Просмотры: 2
Назад
Сверху Снизу