The instance is showing every connected IP as the docker default, which in this case is 172.17.0.1, which is messing with smart/ip bans. We’ve had fresh players join and get instantly banned because the plugin thinks its the same person coming from the same IP.
Reproduction Steps
Configure containerization as per posted instructions
Install a smart-banning plugin like GriefPrevention
Ban someone for any reason
Have a new player try to connect and get autobanned
Never seen this issue before. Check to see if your docker networking mode is set to “host” in the ADS’ settings.
And just a sanity check, you’re not trying to run all of AMP in the unofficial docker image, correct?
I want to guess that it’s the “Use Host Networking for new Containers” right? If that’s the case it’s set to off, which I think was required in the documentation.
And yes, afaik it’s not running entirely in docker, I just followed the guide for making new instances containerized with just the switches/options in the panel.
I have host networking turned on for all my containers, haven’t had a single issue with it (usually solves weird networking issues when you’re working with docker lol).
Not sure if you can convert existing docker instances though, you may need to disable docker for that instance, wait a few, then enable docker again for the setting to take effect.
I’ll give that a shot when I can get around to rebooting the server, and report back!
This is kinda my first time doing anything large with docker, so what exactly does the host networking option do? and how come the guide says to turn it off?
Which guide are you referring to? It might be some use case/niche issue I’m unaware of.
To my understanding, host networking makes it so the Docker container uses the host machine’s IPs/ports when dealing with networking, rather than having the Docker local IP getting thrown in to the mix.
I’m not sure if I have to do something to the container to enable host networking, since it says “on new containers” and might not instantly apply it to existing ones. Hopefully I don’t need to destroy and recreate the instance?
You can try enabling host mode networking and see if it works with a new instance, but this may not be a fixable problem on a Windows host. Docker uses an internal proxy so whatever is inside the container will not see the real-world IP for connections to game servers.
The alternative for Windows being to simply not use Docker at all, or to use a Linux VM for AMP.
Fair enough! I was aiming to migrate to a real rack server in the very near future, so I’ll just see if that fixes it and roll with it if it doesn’t. Thank you guys for your help!
One more unrelated question - not sure if I can stick it on this thread, but if I upgraded my license from an old MCMyAdmin to a proper AMP one do I have to remake the instance or is it seamless in some form?