New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Ports not accessible from outside the container; hosted internally on 0.0.0.0 #89
Comments
same here, any news? i tried to force iptables routing inside container without success :( |
I've got a similar issue, restarting over and over seems to fix it for me. but it does come back every so often EDIT: been able to fix the issue I'm experiencing by attaching the container to the host network, done by appending
Unrelated to this issue but I have messed around with the arkmanager.cfg removing some of the things set by environment variables and set them myself inside the config so my docker compose is a bit more sparse. some stuff might not be best practice since I'm new to docker. |
network mode host should be fine, especially if it fixes things, but this is still a pretty bad bug, especially as the documentation says to specify ports without |
not sure if I have the same problem, but using Docker Desktop on Mac (intel) and I cannot seem to access any of the ports and thus cannot log into the server. not a networking guru, but curious how to fix this! is it an image problem or is it a docker problem? |
I am pretty sure it's a problem with the image. |
On my setup, the ports of the internal mechanism of the docker container are mapped to 0.0.0.0 and only 0.0.0.0, nothing else. This means that the Server cannot be accessed from the outside. I'm not sure what causes this.
This is what i got from looking around the ports inside the container (using docker exec -it ark_server bash):
As you can see, the server is reachable on 0.0.0.0, but not on any other addresses of the container.
This is my docker-compose.yml:
The docker-compose setup should not be at fault here. I'm pretty sure something is up with the internal workings of the docker container.
The only port open to the host (and the rest of the internet) is port 27020, that one seems to be working OK. This is the only TCP port of the bunch, maybe that means something?
The text was updated successfully, but these errors were encountered: