Question When connecting, the player is not redirected to the "try" path, but to a random server. Why?

MeteoraCD2

New member
Jun 6, 2023
1
0
1
32
Hello!
log:
[16:02:42 ERROR]: [connected player] Cookie_Herald (/37.21.238.37:61643): unable to connect to server test
io.netty.channel.AbstractChannel$AnnotatedConnectException: finishConnect(..) failed: В соединении отказано: /127.0.0.1:40001
Caused by: java.net.ConnectException: finishConnect(..) failed: В соединении отказано
at io.netty.channel.unix.Errors.newConnectException0(Errors.java:164) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.channel.unix.Errors.handleConnectErrno(Errors.java:129) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.channel.unix.Socket.finishConnect(Socket.java:359) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe.doFinishConnect(AbstractEpollChannel.java:710) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe.finishConnect(AbstractEpollChannel.java:687) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe.epollOutReady(AbstractEpollChannel.java:567) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:489) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:397) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at java.lang.Thread.run(Thread.java:833) [?:?]


velocity.toml in file
 

hello

New member
Aug 26, 2023
13
0
1
Hello!
log:
[16:02:42 ERROR]: [connected player] Cookie_Herald (/37.21.238.37:61643): unable to connect to server test
io.netty.channel.AbstractChannel$AnnotatedConnectException: finishConnect(..) failed: В соединении отказано: /127.0.0.1:40001
Caused by: java.net.ConnectException: finishConnect(..) failed: В соединении отказано
at io.netty.channel.unix.Errors.newConnectException0(Errors.java:164) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.channel.unix.Errors.handleConnectErrno(Errors.java:129) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.channel.unix.Socket.finishConnect(Socket.java:359) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe.doFinishConnect(AbstractEpollChannel.java:710) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe.finishConnect(AbstractEpollChannel.java:687) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe.epollOutReady(AbstractEpollChannel.java:567) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:489) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:397) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[velocity-3.2.0-SNAPSHOT-256.jar:3.2.0-SNAPSHOT (git-40b76c63-b256)]
at java.lang.Thread.run(Thread.java:833) [?:?]


velocity.toml in file

1. Check Server Configuration: Ensure that your server's configuration files have the correct IP address and port settings. Double-check any service configurations that might be expecting connections on 127.0.0.1:40001.

2. Disable Plugins/Mods: If you're using plugins or mods, temporarily disable them one by one to identify if any are causing the issue. This can help pinpoint the source of the connection attempt.

3. Verify Networking Code: If you've written custom networking code for the server, review it for any attempts to connect to 127.0.0.1:40001 that might be unintended.

4. Check Hosting Environment: If you're using a hosting service, contact their support to verify that their configurations aren't causing the problem.

5. Examine Server Logs: Look at the logs leading up to the error for more clues. These might help you understand what's causing the connection attempt.

6. Check Language/Localization: If the error message is unexpectedly in Russian, investigate if it's related to language or localization settings in the server or plugins.

7. Restart Server: Sometimes, a simple server restart can clear temporary glitches.

8. Test on Different Client: Test connecting to the server from a different device or client to see if the issue persists.

Remember, the error message suggests a connection attempt to 127.0.0.1:40001, which is typically a local address. Make sure your server isn't unintentionally trying to connect to itself on this address and port. If the issue persists and you're not making progress, consider seeking help from experienced Minecraft server administrators or developers.