On start mc-image-helper fails with timeout #2466

johannes-wolf · 2023-11-03T15:24:45Z

johannes-wolf
Nov 3, 2023

Describe the problem

When starting the container, the mc-image-helper fails with the following message:

[mc-image-helper] 15:22:09.641 ERROR : 'resolve-minecraft-version' command failed. Version is 1.36.5
mc_1  | reactor.core.Exceptions$ReactiveException: io.netty.channel.ConnectTimeoutException: connection timed out: launchermeta.mojang.com/13.107.246.45:443

Container definition

version: "3.8"

services:
  mc:
    image: itzg/minecraft-server
    tty: true
    stdin_open: true
    ports:
      - "25565:25565"
    environment:
      EULA: "TRUE"
      MEMORY: "2G"
      VERSION: "1.20.2"
      WHITELIST_FILE: "/data/whitelist"
      OPS_FILE: "/data/admins"
    volumes:
      - ./data:/data

Container logs

mc_1  | [init] Running as uid=1000 gid=1000 with /data as 'drwxr-xr-x 3 1000 1000 4096 Nov  3 15:07 /data'
mc_1  | [init] Resolving type given VANILLA
mc_1  | [mc-image-helper] 15:22:09.641 ERROR : 'resolve-minecraft-version' command failed. Version is 1.36.5
mc_1  | reactor.core.Exceptions$ReactiveException: io.netty.channel.ConnectTimeoutException: connection timed out: launchermeta.mojang.com/13.107.246.45:443
mc_1  |         at reactor.core.Exceptions.propagate(Exceptions.java:408)
mc_1  |         at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:101)
mc_1  |         at reactor.core.publisher.Mono.block(Mono.java:1712)
mc_1  |         at me.itzg.helpers.versions.ResolveMinecraftVersionCommand.call(ResolveMinecraftVersionCommand.java:26)
mc_1  |         at me.itzg.helpers.versions.ResolveMinecraftVersionCommand.call(ResolveMinecraftVersionCommand.java:12)
mc_1  |         at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
mc_1  |         at picocli.CommandLine.access$1500(CommandLine.java:148)
mc_1  |         at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
mc_1  |         at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
mc_1  |         at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
mc_1  |         at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
mc_1  |         at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
mc_1  |         at picocli.CommandLine.execute(CommandLine.java:2170)
mc_1  |         at me.itzg.helpers.McImageHelper.main(McImageHelper.java:157)
mc_1  |         Suppressed: java.lang.Exception: #block terminated with an error
mc_1  |                 at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:103)
mc_1  |                 ... 12 common frames omitted
mc_1  | Caused by: io.netty.channel.ConnectTimeoutException: connection timed out: launchermeta.mojang.com/13.107.246.45:443
mc_1  |         at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:261)
mc_1  |         at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
mc_1  |         at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:153)
mc_1  |         at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173)
mc_1  |         at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166)
mc_1  |         at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
mc_1  |         at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
mc_1  |         at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
mc_1  |         at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
mc_1  |         at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
mc_1  |         at java.base/java.lang.Thread.run(Unknown Source)

dlabreu · 2023-11-04T10:23:19Z

dlabreu
Nov 4, 2023

+1 here same issue.

0 replies

johannes-wolf · 2023-11-04T10:41:58Z

johannes-wolf
Nov 4, 2023
Author

It is a routing issue on the host side, the container in unable to ping any host. I re-opened the issue because other people have the same problem.

0 replies

itzg · 2023-11-04T14:29:07Z

itzg
Nov 4, 2023
Maintainer

Let's not reopen an issue I can't fix...but I will convert to a discussion so it's more visible.

0 replies

Rick-O-Shay · 2023-11-04T16:46:33Z

Rick-O-Shay
Nov 4, 2023

Hi,

I am new to GitHub and also docker containers. I am trying to setup a minecraft server on my Synology NAS using a docker container and I found this thread after googling because I have the exact same issue. The OP was made just hours ago. Is this something wrong in our setup or is there another issue at hand here? I tried vanilla and paper, and both are just erroring out on me and will not run.

Any info would be appreciated for a noob like me.

Thanks,

4 replies

Rick-O-Shay Nov 4, 2023

Sorry, going nuts here. Does this post mean that we have config properly, but there is a problem outside of what we have done? Is every self-hosted minecraft server down??

itzg Nov 4, 2023
Maintainer

Yes, the posted container configuration is fine. The container starts fine for me, apparently for most others since I see no mention of networking issues on the Discord server, and even the OP from @johannes-wolf since they reported it was a routing issue on their host.

Perhaps @johannes-wolf you can share more details about how you resolved your issue.

Rick-O-Shay Nov 4, 2023

Interesting. I disabled my firewall in my router for a split second to test if that was the issue and it works fine, so apparently there is something other than the default port of 25565 that needs to be opened up, but now I have to troubleshoot that....
Thanks

johannes-wolf Nov 4, 2023
Author

I could not get it to work, and my routing knowledge is very limited. My “solution” was to host the Minecraft server without using docker - without this project. This container creates a new network and ip route also looks fine to my understanding…

guercheLE · 2024-04-28T16:58:37Z

guercheLE
Apr 28, 2024

Getting same error. If take TYPE=PAPER, it goes fine and downloads VANILLA. How do I figure out which URL the script is trying to download and to fix it?

28/04/2024
13:36:21
[init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 12 1000 1000 4096 Nov 26 12:16 /data'
28/04/2024
13:36:21
[init] Resolving type given PAPER
28/04/2024
13:37:53
[mc-image-helper] 13:37:53.484 ERROR : 'install-paper' command failed. Version is 1.38.13
28/04/2024
13:37:53
reactor.core.Exceptions$ReactiveException: io.netty.channel.ConnectTimeoutException: connection timed out after 30000 ms: api.papermc.io/172.67.72.198:443
28/04/2024
13:37:53
at reactor.core.Exceptions.propagate(Exceptions.java:408)
28/04/2024
13:37:53
at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:101)
28/04/2024
13:37:53
at reactor.core.publisher.Mono.block(Mono.java:1712)
28/04/2024
13:37:53
at me.itzg.helpers.paper.InstallPaperCommand.useCoordinates(InstallPaperCommand.java:153)
28/04/2024
13:37:53
at me.itzg.helpers.paper.InstallPaperCommand.call(InstallPaperCommand.java:110)
28/04/2024
13:37:53
at me.itzg.helpers.paper.InstallPaperCommand.call(InstallPaperCommand.java:35)
28/04/2024
13:37:53
at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
28/04/2024
13:37:53
at picocli.CommandLine.access$1500(CommandLine.java:148)
28/04/2024
13:37:53
at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
28/04/2024
13:37:53
at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
28/04/2024
13:37:53
at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
28/04/2024
13:37:53
at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
28/04/2024
13:37:53
at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
28/04/2024
13:37:53
at picocli.CommandLine.execute(CommandLine.java:2170)
28/04/2024
13:37:53
at me.itzg.helpers.McImageHelper.main(McImageHelper.java:159)
28/04/2024
13:37:53
Suppressed: java.lang.Exception: #block terminated with an error
28/04/2024
13:37:53
at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:103)
28/04/2024
13:37:53
... 13 common frames omitted
28/04/2024
13:37:53
Caused by: io.netty.channel.ConnectTimeoutException: connection timed out after 30000 ms: api.papermc.io/172.67.72.198:443
28/04/2024
13:37:53
at io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe$2.run(AbstractEpollChannel.java:615)
28/04/2024
13:37:53
at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
28/04/2024
13:37:53
at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:153)
28/04/2024
13:37:53
at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173)
28/04/2024
13:37:53
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166)
28/04/2024
13:37:53
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
28/04/2024
13:37:53
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:416)
28/04/2024
13:37:53
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
28/04/2024
13:37:53
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
28/04/2024
13:37:53
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
28/04/2024
13:37:53
at java.base/java.lang.Thread.run(Unknown Source)
28/04/2024
13:37:53
[init] ERROR: failed to download paper

2 replies

guercheLE Apr 28, 2024

The following command:

curl -X 'GET'
'https://api.papermc.io/v2/projects/paper/versions/1.20.1/builds/196/downloads/234a9b32098100c6fc116664d64e36ccdb58b5b649af0f80bcccb08b0255eaea'
-H 'accept: application/json'

Is returning:

{
"error": "Download not found."
}

guercheLE Apr 28, 2024

Same for the following command:

curl -X 'GET'
'https://api.papermc.io/v2/projects/paper/versions/1.20.5/builds/15/downloads/f7e96c63895aae25188f907844ad151c4ad2c620e002f16c446a58b4c32e9161'
-H 'accept: application/json'

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

On start mc-image-helper fails with timeout #2466

{{title}}

Replies: 5 comments 6 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

On start mc-image-helper fails with timeout #2466

Describe the problem

Container definition

Container logs

Replies: 5 comments · 6 replies

johannes-wolf Nov 4, 2023 Author

itzg Nov 4, 2023 Maintainer

itzg Nov 4, 2023 Maintainer

johannes-wolf Nov 4, 2023 Author

Replies: 5 comments 6 replies

johannes-wolf
Nov 4, 2023
Author

itzg
Nov 4, 2023
Maintainer

itzg Nov 4, 2023
Maintainer

johannes-wolf Nov 4, 2023
Author