-
|
Hi! Logs: This is how I sat up my container: I'm currently using "ghcr.io/itzg/minecraft-server:2026.5.2-java21" image. Does anyone has solution for this? or maybe it's a bug? note: I have tested my proxy with different containers on this same system using http_proxy, https_proxy and NO_PROXY env variables and it does work so the proxy itself is not the problem. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 9 replies
-
|
With this image, make sure proxy env vars are set on the container itself and are visible to both init tools and Java process:
Then verify from inside container: docker exec -it <container> sh -lc 'env | grep -i _proxy; wget -S -O- https://launchermeta.mojang.com >/dev/null'If Also ensure the proxy URL includes scheme and port (for example If you share your compose proxy env block (redact secrets), I can point out exactly what to adjust. If this solved it, please mark the answer so others can find it faster. |
Beta Was this translation helpful? Give feedback.
-
|
I added http_proxy, https_proxy and no_proxy env variables as well and tested it with wget. wget does successfully connect but the error I encountered is still the same. Shell: @[~]$ sudo docker exec -it ix-minecraft-minecraft-1 sh -lc 'env | grep -i _proxy; wget -S -O- https://launchermeta.mojang.com >/dev/null' NO_PROXY=localhost,127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16 env variables: Docker logs: [init] Running as uid=568 gid=568 with /data as 'drwxrwx---+ 2 568 568 9 May 22 09:33 /data' |
Beta Was this translation helpful? Give feedback.
-
|
Please set the env var |
Beta Was this translation helpful? Give feedback.
-
|
Hello! |
Beta Was this translation helpful? Give feedback.
-
|
Your logs are very useful: they show one Mojang endpoint succeeds first, then a later request fails with So this is likely not a Minecraft version problem; it is a proxy path/routing inconsistency. Two concrete checks from your current config:
You can dump effective env quickly: docker exec -it ix-minecraft-server sh -lc 'env | grep -i proxy | sort'Since maintainer asked for DEBUG logs, I'd keep following that path; these two checks are the first things I'd fix/verify from the log you shared. If this solved it, please mark the most helpful answer so others can find it faster. |
Beta Was this translation helpful? Give feedback.
-
|
I removed CIDR and tested it again and nothing changed. It's exactly is the same problem. with CIDR: without CIDR: note that since you told me earlier, I also added http_proxy, https_proxy and NO_PROXY env variables alongside the other ones which it made no difference. |
Beta Was this translation helpful? Give feedback.
-
|
One more concrete thing to fix: The image docs say PROXY_HOST=192.168.0.183
PROXY_PORT=10811
PROXY_NON_PROXY_HOSTS=localhost|127.*|10.*|172.16.*|192.168.*For a clean test I would also avoid mixing the two proxy mechanisms at first: PROXY_HOST=192.168.0.183
PROXY_PORT=10811
# no http_proxy / https_proxy / NO_PROXY for this testThe successful |
Beta Was this translation helpful? Give feedback.
-
|
I changed proxy env: Container logs: |
Beta Was this translation helpful? Give feedback.
-
|
It's looks like it's something about the newlines ending up in the expanded |
Beta Was this translation helpful? Give feedback.
-
|
Got a PR going that will hopefully fix this |
Beta Was this translation helpful? Give feedback.
-
|
but there's an issue with Github builds right now 
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you! Thank you again |
Beta Was this translation helpful? Give feedback.
-
|
Please try with a re-pulled image. |
Beta Was this translation helpful? Give feedback.
-
|
Hello again, sorry for checking back late. I tested it using the new released package The result is that it's fixed my issue! and I no longer run into any problems. Docker logs if you are curious: |
Beta Was this translation helpful? Give feedback.
Hello again, sorry for checking back late. I tested it using the new released package
ghcr.io/itzg/minecraft-server:2026.6.0-java21that has the #4081 in it, and with the same system and environment as before.The result is that it's fixed my issue! and I no longer run into any problems.
Thank you @itzg for fixing this!
Docker logs if you are curious: