Autopause function

[woeisme]

I'm using the autopause feature successfully, however I notice in the logs endless wakeups from random access attempts (I'm runnning a user whitelist).

Endless knock attempts from random IP's are sort of defeating the purpose of the pause, what would be a good way to mitigate this behaviour?

[itzg]

You will need to allow/restrict IP addresses at your internet router or some other routing point prior to the container. Any whitelisting within the Minecraft server won't help because...it has to be unpaused to process and block the connections.

[woeisme]

That´s unfortunately what I feared, is there a way to do container specific IP firewallling perhaps?

[woeisme]

I decided to switch away from docker iptables rules to ufw and opened the minecraft port for just the a single users IP using UFW.
I'll test for the next few days to see if that cuts down on the random knocking.

[woeisme]

For those that would like to use UFW to solve this please read this

I ended up limiting IP access at the router level.

[itzg]

Great solution using UFW and that was exactly the answer to your question of container specific firewall.

[indykoning]

For the people where that may not be an option it might be cool to implement the likes of https://github.com/timvisee/lazymc
Which doesn't boot the server until a client actually tries to connect.
It gets rid of those pesky port scanners starting the server, but keeps the server accessible from any ip

[itzg]

Very interesting concept, @indykoning . I could use the https://github.com/itzg/mc-router/tree/master/mcproto bits and tie that into start/stop logic in https://github.com/itzg/mc-server-runner/tree/master ...

[github-actions]

This issue is stale because it has been open 30 days with no activity. Please add a comment describing the reason to keep this issue open.