Open up the mail service https://mail.longervision.com I’ve been trying to host on DigitalOcean, I have:

What is happening?
Please do not stop the stack while we are initializing the database or do other preparations.

What is happening? - Nginx cannot connect to an upstream server or other services are not ready yet.
This is fine if mailcow was just installed or updated and can take a few minutes to complete.
Please check the logs or contact support if the error persists.

Quick debugging
Check Nginx and PHP logs:

docker compose logs --tail=200 php-fpm-mailcow nginx-mailcow
Make sure your SQL credentials in mailcow.conf (a link to .env) do fit your initialized SQL volume. If you see an access denied, you might have the wrong mailcow.conf:

source mailcow.conf ; docker compose exec mysql-mailcow mysql -u${DBUSER} -p${DBPASS} ${DBNAME}
In case of a previous failed installation, create a backup of your existing data, followed by removing all volumes and starting over (NEVER do this with a production system, it will remove ALL data):

BACKUP_LOCATION=/tmp/ ./helper-scripts/backup_and_restore.sh backup all
docker compose down --volumes ; docker compose up -d
Make sure your timezone is correct. Use "America/New_York" for example, do not use spaces. Check here for a list.


Click to learn more about getting support.

From my DigitalOcean’s console:

⋊> /o/mailcow-dockerized on master ⨯ sudo systemctl status postgresql                                                                                                 14:14:33
● postgresql.service - PostgreSQL RDBMS
     Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled)
     Active: active (exited) since Wed 2023-06-21 23:24:26 PDT; 14h ago
   Main PID: 1001 (code=exited, status=0/SUCCESS)
        CPU: 2ms

Jun 21 23:24:26 localhost systemd[1]: Starting PostgreSQL RDBMS...
Jun 21 23:24:26 localhost systemd[1]: Finished PostgreSQL RDBMS.
⋊> /o/mailcow-dockerized on master ⨯ sudo systemctl status mysql                                                                                                      14:16:01
○ mysql.service
     Loaded: masked (Reason: Unit mysql.service is masked.)
     Active: inactive (dead)
⋊> /o/mailcow-dockerized on master ⨯

That means: I now ONLY have the service PostgreSQL but WITHOUT MySQL.

Is it possible for me to connect mailcow with PostgreSQL but NOT MySQL ??

Cheers
Pei

I don’t really understand the problem tbh. Where is that PostgreSQL coming from? Aren’t you executing the systemctl status on the host? This doesn’t work with docker containers since the service is inside the container and not on the host.

What does docker ps show?

    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!

    D4niel
    Hi, Thank you for the reply…

    Actually, MySQL is from docker compose exec mysql-mailcow mysql -u${DBUSER} -p${DBPASS} ${DBNAME} .
    I would like to replace mysql with PostgreSQL.

    Anyway, now, I’ve got mysql come back to life…. And it’s running but ….
    it seems DigitalOcean banned port 25 by default? Take a look at https://mail.longervision.com … I just had it work for me for a couple of minutes… My god…

      No one is typing