Server can't be accessed externally when through pufferpanel #36
Replies: 4 comments
-
LordRalex wrote at Dec 16 2015 14:19:32 UTC: It sounds like the docker containers are not correctly forwarding the ports, or exposing them. When you have the server running through the panel, can you provide the output of "docker ps"? |
Beta Was this translation helpful? Give feedback.
-
myiume wrote at Dec 16 2015 14:19:32 UTC: Hey there. Thanks for replying :) This would be the output from the command you asked me to execute: |
Beta Was this translation helpful? Give feedback.
-
LordRalex wrote at Dec 16 2015 14:19:32 UTC: Yeah, that is what I thought. Docker is binding the port to 127.0.0.1, not 0.0.0.0. When you set the IP for the server, you did not use 127.0.0.1, correct? |
Beta Was this translation helpful? Give feedback.
-
myiume wrote at Dec 16 2015 14:19:32 UTC: I did actually. Many thanksies. I don't know how I missed that. Duuh! It was a no brainer. |
Beta Was this translation helpful? Give feedback.
-
myiume wrote at Dec 16 2015 14:19:32 UTC:
The minecraft server opened through PufferPanel gives a connection refused error when attempting to connect to it via the Minecraft Client.
It is not an iptables rule, as before pufferpanel touched it with an extra Chain, it was clean Policy ACCEPT.
I can't figure out what's up, but the server will work externally if opened without pufferpanel.
Some assistance would be helpful.
Thanks.
Best regards,
Myiume - Freelance Java Developer
Beta Was this translation helpful? Give feedback.
All reactions