Вопрос Помогите с Запуском NullCordX

N

NeznixWorld

Пользователь
Сообщения
21
3.4 Разрешается выкладывание кода, файлов конфигураций, логов и т.д. только под BB-код CODE
Другие ядра
  1. WaterFall
[13:11:03] [ForkJoinPool.commonPool-worker-1/ERROR] [NullCordX]: Failed to check for update
org.apache.http.conn.ConnectTimeoutException: Connect to 47.206.114.248:23446 [/47.206.114.248] failed: Connect timed out
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at net.shieldcommunity.nullcordx.utils.HttpUtils.makeRequest(HttpUtils.java:38) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at net.shieldcommunity.nullcordx.utils.SimpleUpdateChecker.lambda$startCheckForUpdate$0(SimpleUpdateChecker.java:40) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(ForkJoinTask.java:1395) ~[?:?]
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373) ~[?:?]
at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182) ~[?:?]
at java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655) ~[?:?]
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622) ~[?:?]
at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165) ~[?:?]
Caused by: java.net.SocketTimeoutException: Connect timed out
at sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:551) ~[?:?]
at sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:602) ~[?:?]
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327) ~[?:?]
at java.net.Socket.connect(Socket.java:633) ~[?:?]
at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:75) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
... 17 more
[13:11:05] [NullCordX-startup/ERROR] [NullCordX]: Failed to load Country GeoIp database
org.apache.http.conn.ConnectTimeoutException: Connect to 47.206.114.248:23446 [/47.206.114.248] failed: Connect timed out
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at net.shieldcommunity.nullcordx.utils.HttpUtils.makeRequest(HttpUtils.java:38) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at net.md_5.bungee.util.ConnectionPendingHandler.makeRequest(ConnectionPendingHandler.java:92) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at net.shieldcommunity.nullcordx.antibot.maxmind.connections.ShieldcommunityMaxMindConnection.openConnection(ShieldcommunityMaxMindConnection.java:22) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at net.shieldcommunity.nullcordx.antibot.MaxMindDatabase.downloadDataBase(MaxMindDatabase.java:141) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at net.shieldcommunity.nullcordx.antibot.MaxMindDatabase.reloadDatabase(MaxMindDatabase.java:61) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at net.shieldcommunity.nullcordx.antibot.maxmind.AbstractMaxMindManager.reloadDatabase(AbstractMaxMindManager.java:118) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at net.shieldcommunity.nullcordx.antibot.maxmind.AntiCountryManagerImpl.onLoad(AntiCountryManagerImpl.java:80) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at net.shieldcommunity.nullcordx.ManagerComponent.load(ManagerComponent.java:26) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at net.shieldcommunity.nullcordx.NullCordXImpl.asyncLoad(NullCordXImpl.java:314) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at java.lang.Thread.run(Thread.java:842) [?:?]
Caused by: java.net.SocketTimeoutException: Connect timed out
at sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:551) ~[?:?]
at sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:602) ~[?:?]
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327) ~[?:?]
at java.net.Socket.connect(Socket.java:633) ~[?:?]
at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:75) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142) ~[NullCordX.jar:1.20-R0.3-SNAPSHOT]
... 19 more
[13:11:05] [NullCordX-startup/WARN] [NullCordX]: Using the cached Country GeoIp database...
[13:11:05] [NullCordX-startup/ERROR] [NullCordX]: Unable to load Country GeoIp database. Cache is not found!
[13:11:05] [NullCordX-startup/INFO] [NullCordX]: AntiCountryManager loaded in 15011ms
[13:11:05] [NullCordX-startup/INFO] [NullCordX]: Loading AntiASNManager...
[13:11:05] [NullCordX-startup/INFO] [NullCordX]: AntiASNManager disabled: Not used anywhere in the antibot settings!
[13:11:05] [NullCordX-startup/INFO] [NullCordX]: AntiASNManager loaded in 0ms
[13:11:05] [NullCordX-startup/INFO] [NullCordX]: Loading AntiProxyManager...
[13:11:05] [NullCordX-startup/INFO] [NullCordX]: AntiProxyManager disabled: Not used anywhere in the antibot settings!
[13:11:05] [NullCordX-startup/INFO] [NullCordX]: AntiProxyManager loaded in 0ms
[13:11:05] [NullCordX-startup/INFO] [NullCordX]: Loading AntiBotAttributesLimiter...
[13:11:05] [NullCordX-startup/INFO] [NullCordX]: AntiBotAttributesLimiter loaded in 0ms
[13:11:05] [NullCordX-startup/INFO] [NullCordX]: Loading CaptchaGenerator...
[13:11:05] [NullCordX-startup/INFO] [NullCordX]: CaptchaGenerator disabled: Not used anywhere in the antibot settings!
[13:11:05] [NullCordX-startup/INFO] [NullCordX]: CaptchaGenerator loaded in 0ms
[13:11:05] [NullCordX-startup/INFO] [NullCordX]: NullCordX successfully loaded in 16637ms!
 
Config.yml

So if you would like to support multiple client versions, simply specify at least one server per version and BungeeCord will do the matching for you.
#
# bind_local_address - Whether the address Bungee uses to connect to your servers will be explicitly set to the address Bungee is listening on.
# This serves no purpose unless your system has multiple IP addresses.
#
# host - The IP and Port in which the BungeeCord instance will be hosted on.
# Use 0.0.0.0 to listen to all IPs (recommended).
#
# max_players - The max player limit shown in the minecraft client's multiplayer menu.
# Note that this limit is fake, you can set it to 0, players will still be able to join. Look at player_limit above for a "real" player limit.
#
# tab_size - The amount of players that will show up in the tab list (Pressing tab on keyboard)
#
# force_default_server - If true, the player will always connect to the default servers specified in the priorities list when they join the server.
# if false, the player will join the server they were last connected to. Note: forced_hosts does NOT override this.
# To make the forced_hosts setting work, set this to false. Should be kept on for cracked server!
listeners:
- query_port: 25577
motd: "<blue>Another NullCordX server"
tab_list: "GLOBAL_PING"
query_enabled: false
proxy_protocol: false
forced_hosts:
pvp.md-5.net: "pvp"
ping_passthrough: false
priorities:
- "lobby"
bind_local_address: true
host: "0.0.0.0:25577"
max_players: 1
tab_size: 60
force_default_server: false

# Configuration for servers
#
# motd - The message to be displayed in the multiplayer menu when players ping the server.
# address - The address of the backend server to which the proxy will try to connect the player
# restricted - Prevents players from joining the server unless they have the bungeecord.server.[servername] permission
servers:
lobby:
motd: "<blue>Just another NullCordX - Forced Host"
address: "localhost:25565"
restricted: false

# Whether to enable IP (which forwards the players true IP to Bukkit, rather than the proxy IP) and UUID forwarding (which forwards the players true online-mode UUID to Bukkit, rather than an offline-mode username hash!)
# If you're running an online-mode: true server, It is highly recommended you use this option.
ip_forward: true

# This makes the server send the IP of connecting players to Mojang to check if they are using a proxy to connect to the BungeeCord.
prevent_proxy_connections: false

# Whether the BungeeCord instance will authenticate with the Mojang servers. If set to false, cracked players will also be able to join your server.
online_mode: false

# Choose if your BungeeCord instance supports Forge clients or not.
forge_support: false

# Should a proxy reject connections made via transfer? This will prevent the player from connecting if he was sent to this proxy.
reject_transfers: true

# When a player ping a BungeeCord server, that ping is also included in the BungeeCord console.
log_pings: false

# When a player writes a BungeeCord command, that command is also included in the BungeeCord console.
log_commands: false

# Should the proxy always expect a secure profile from a client?
enforce_secure_profile: false

# After how many milliseconds to close the connection if no packet has been sent?
timeout: 20000

# If the packet is larger than this value, it will be compressed. Use -1 to disable compression.
network_compression_threshold: 256

# For how long in milliseconds BungeeCord should use cached results of server pings instead of manually pinging them to get the playercount. (-1 to disable)
remote_ping_cache: -1

# How long in milliseconds BungeeCord will try to ping a server to get the playercount before cancelling the connection.
remote_ping_timeout: 5000

# Once an IP has connected connection_throttle_limit times within connection_throttle milliseconds, it must wait connection_throttle milliseconds before attempting to connect again.
# Example: With default settings, an IP may make 6 connection attempts in 4000ms (4s) before the IP is forced to wait 4s before connecting again.
connection_throttle_limit: 6

# The time delay before a client is allowed to connect again after a recent connection attempt to prevent attacks (in milliseconds).
connection_throttle: 4000

# How long in milliseconds BungeeCord will try to connect a player to a server before cancelling the connection.
server_connect_timeout: 5000

# Global player limit for your BungeeCord instance. If set to 0 or below, this will allow an unlimited amount of users to join.
player_limit: -1

# Use this to disable commands on your BungeeCord instance.
disabled_commands:
- "disabledcommandhere"

# These are the permissions of what commands or actions you can use within the proxy.
# Please note, that these are different to Bukkit/Spigot permissions.
# The permissions are group based and are used to attach players later on in the configuration.
# All players will have ability to use the commands under default, those players given the admin group in the groups section are allowed to use the extra commands for BungeeCord as stated below that group.
# Note each group only inherits default so you may need to put the same node in different groups if you add more.
permissions:
default:
- "bungeecord.command.server"
- "bungeecord.command.list"
admin:
- "bungeecord.command.alert"
- "bungeecord.command.end"
- "bungeecord.command.ip"
- "bungeecord.command.reload"
- "bungeecord.command.kick"
- "nullcordx.player"
- "nullcordx.player.help"
- "nullcordx.player.stats"
- "nullcordx.player.livestats.default"
- "nullcordx.player.livestats.cpu"
- "nullcordx.player.livestats.network"
- "nullcordx.player.livestats.upstream_network"
- "nullcordx.player.livestats.downstream_network"

# Here, you can assign players to a permission group that you created earlier in the configuration.
# The format is groups, followed by each player, followed by each group they are in.
# By default md_5 is given admin group, which gives permissions as defined by permissions section.
# Every player has default. Only add players who need more than the default permissions.
groups:
md_5:
- "admin"

# A unique value used for metrics statistics.
# Not used by proxy anywhere, but can be used for plugins.
stats: "6fb2da7d-d38b-4828-bdb0-8bdcb8cd4f2d"
config_version: 1
 
Касательно платных плагинов/ядер помогать здесь тебе никто не будет

Обратись к автору ядра за поддержкой

offtop
А модерацию прошу чистить такое и выдавать предупреждения
 
Прочитав только две строчки можно понять из-за чего
Код: 
[13:11:03] [ForkJoinPool.commonPool-worker-1/ERROR] [NullCordX]: Failed to check for update
org.apache.http.conn.ConnectTimeoutException: Connect to 47.206.114.248:23446 [/47.206.114.248] failed: Connect timed out
Смотри в сторону хостинга/настройки файрволла и тд
 
dronsyy написал(а):
Прочитав только две строчки можно понять из-за чего
Код: 
[13:11:03] [ForkJoinPool.commonPool-worker-1/ERROR] [NullCordX]: Failed to check for update
org.apache.http.conn.ConnectTimeoutException: Connect to 47.206.114.248:23446 [/47.206.114.248] failed: Connect timed out
Смотри в сторону хостинга/настройки файрволла и тд
Нажмите для раскрытия…
я запускаю на пк
 
сервер 47.206.114.248:23446 либо недоступен либо заблокирован айпи/порт страны,
 
Последнее редактирование модератором:
Войдите или зарегистрируйтесь для ответа.
Назад
Сверху Снизу