Troubleshooting

How can I start the services?

bin/production.sh up -d

How can I stop the services?

bin/production.sh stop

How can I check the log files?

bin/production.sh logs -f
bin/production.sh logs mta
bin/production.sh logs mda

The mailserver-ssl container is exiting all the time

Not a problem! This container is used to create self-signed certificates. It will exit, if they're already certificates existing.

Connection errors are popping up

Problem with dial: dial tcp 172.19.0.7:80: getsockopt: connection refused. Sleeping 1s
Problem with dial: dial tcp 172.19.0.7:80: getsockopt: connection refused. Sleeping 1s
Problem with dial: dial tcp 172.19.0.7:80: getsockopt: connection refused. Sleeping 1s

Don't worry if you see these messages after starting up. The services of docker-mailserver are depending on each other. It takes up to 2 minutes to start all services and the messages should disappear then.

When you think that something takes too much time, then try to figure out which service the IP address is pointing to. Port :80 is a strong indicator that something is wrong with the web service so you may have a look into its logs.

How can I check the state of a service and if it's healthy?

Use bin/production.sh ps -a to see the state and health of all services.

All services except for ssl should have the state Up. Keep an eye up for something like Up (unhealthy), since most of the services are doing healthcheck on their own and should always be in a healthy condition.