Server IP Address leak in server pack
denzuko opened this issue ยท 1 comments
Details
logs
[09:21:55] [Server thread/INFO] [minecraft/DedicatedServer]: Loading properties
[09:21:55] [Server thread/INFO] [minecraft/DedicatedServer]: Default game type: SURVIVAL
[09:21:55] [Server thread/INFO] [minecraft/DedicatedServer]: Generating keypair
[09:21:56] [Server thread/INFO] [minecraft/DedicatedServer]: Starting Minecraft server on 5.196.106.235:25565
[09:21:56] [Server thread/INFO] [minecraft/NetworkSystem]: Using epoll channel type
[09:21:56] [Server thread/WARN] [minecraft/DedicatedServer]: **** FAILED TO BIND TO PORT!
[09:21:56] [Server thread/WARN] [minecraft/DedicatedServer]: The exception was: io.netty.channel.unix.Errors$NativeIoException: bind(..) failed: Address not available
[09:21:56] [Server thread/WARN] [minecraft/DedicatedServer]: Perhaps a server is already running on that port?
[09:21:56] [Server thread/INFO] [minecraft/MinecraftServer]: Stopping server
[09:21:56] [Server thread/INFO] [minecraft/MinecraftServer]: Saving worlds
[09:21:56] [Server thread/INFO] [FML]: The state engine was in incorrect state POSTINITIALIZATION and forced into state SERVER_STOPPED. Errors may have been discarded.
[09:21:56] [Server Shutdown Thread/INFO] [minecraft/MinecraftServer]: Stopping server
[09:21:56] [Server Shutdown Thread/INFO] [minecraft/MinecraftServer]: Saving worlds
2019/10/16 09:21:57 Done
IP Details
inetnum: 5.196.106.232 - 5.196.106.239
netname: OVH_210615985
mnt-by: OVH-MNT
( OVH server, in the 5.196.106.232/28 netblock)
Root cause:
server.properties
...
server-port=25565
server-ip
=5.196.x.x
....
Expected resolve
change to server-ip=0.0.0.0
docker-compose file to reproduce:
---
version: '3.7'
volumes:
ftb_data:
services:
mc:
image: itzg/minecraft-server
volumes:
- "ftb_data:/data"
environment:
EULA: "true"
TYPE: FTB
SERVER_PORT: 0.0.0.0:25565
FTB_SERVER_MOD: https://media.forgecdn.net/files/2623/86/Bounds+3.0+Server+Files.zip
ports:
- 25565
healthcheck:
test: ['CMD', 'mcstatus', 'localhost:25565', 'ping']
interval: 10m
timeout: 10s
retries: 3
start_period: 90m
...