hi all, I wanted to transfer my mailcow server from a PC on a proxmox VM. I used cold-standy. Everything was OK but … when I tried “docker-compose up -d” on the new machine, I have the message “services.nginx-mailcow.ports contains an invalid type, it should be a number, or an object”.
Did you ever had this message ?

  • and you are using the latest docker compose 2.x version?

No, but are you sure that the ports for mailcow are not already in use by something else on the new server?
Mailcow-nginx tries to bind on port 80 and 443.

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!

My guess is that the docker-compose file is a bit messed up or missing entries? (The error services.nginx-mailcow.ports sounds like the docker-compose structure) Did you ever manually change the file and maybe broke its indentation?

The source is a Debian 11 and the copy is a brand new Debian 12 without anything else.
I made no changes in the files. I even checked the two files (the source and the copy) : they are exactly the same !

Looks like docker-compose doesn’t agree here. Have you also copied the .env file accordingly?

yes .. the files in the directory /opt/mailcow-dockerized are the same in the source and in the copy ..

and you are using the latest docker compose 2.x version?

hi @esackbauer : many many thanks ! That was the problem : I was using v1.9 ! It’s a stupid dummy mistake.
Now, docker-compose up -d starts.

a year later

I did the same but when ran docker compose up -d I got this
already exists but was not created by Docker Compose. Use external: true

No one is typing