After just restarting my physical server, after updating the linux kernel, i just ran into the problem, that postifix ist unable to start, because the port is allocated, but in the same time - no its not.

I’ve ran following:
netstat -tulpn | grep LISTEN > No port 587 is in use
lsof -i tcp:587 > Nothing
docker ps > besides mailcow only traefik exposes 80 & 443 to the host all other services expose to the internal networks
service docker restart > nothing
docker rm -f $(docker ps -aq) (remove all containers) > nothing
docker rm -f $(docker ps -aq) (remove all containers) > and only start postfix also dont work
reboot > nothing

But in the same time, compose will always show me: Bind for 0.0.0.0:587 failed: port is already allocated.

I can definitively say, that there are no services on the entire system except mailcow that uses those ports (besides debian, only docker is installed and running all the software)

Maybe one of you have encountered something strange like that and can help me with this just a bit.
I’ll appreciate the help and thank you in advance.

Can also answered on german

Something other to mention:
docker run -p 587:80 -d nginx && curl http://<hostname||ip>:587 works just fine and the port is not allocated

Have something to say?

Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

I now just switched the port to 586 and updated my client configs, so i think it should’n bother me for now

No one is typing