failed to bind host port

[twilit bobcat]

Error Event [b4962ebb-33b1-4297-9dba-f9d9c8ce4141]: environment/docker: failed to start container: Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint 57464b6f-7c94-4e6c-9841-9716236b25ed (bf7234db3ac689129b9bc7bd8fe5416ba0bb13bfe44917114066dbd8e65bcc9f): failed to bind host port for 62.122.242.127:25565:172.18.0.2:25565/tcp: cannot assign requested address

[warm bramble]

At your service, @twilit bobcat!

The IP address you have assigned to your server is not actually available for use on your machine, or something is already running on that port. Use ss -plnt | grep :<port> (replacing <port> with your own) to find what processes might be using it.

If you don't find any service using the port, then refer to the instructions below.

Execute the command hostname -I | awk '{print $1}' and change your Node allocations to use this IP. Yes, it can be your internal/local IP when you're behind NAT. You still have to use it as that is your network interface IP.

If you have added multiple public IPs to your network interface, then you can view all of them using the command ip a | grep "inet "

[twilit bobcat]

Error: Unable to access jarfile server.jar

[tiny bone]

use local IP

[vague salmon]

Why are you responding to week old messages that have already been resolved ?