#environment/docker: failed to start container
6 messages · Page 1 of 1 (latest)
And that error might be ... what exactly ?
Error Event [943d74af-5e56-4c48-aeda-3f692813e984]: environment/docker: failed to start container: Error response from daemon: driver failed programming external connectivity on endpoint 97c83f86-ff87-4ca6-aca9-b9a50dc28a54 (6d9d47e8b9e09a69fdf5ad8747d1eafca5e977cca03b8dcde743899bc0e23401): Error starting userland proxy
At your service, @bright fulcrum!
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 "
do i need to open any ports?
No. Just read what the bot said and use the correct IP address in your allocation