Hello, I’ve been using mailcow for a long time and since yesterday I am getting the error whenever I visit my self hosted instance NET::ERR_CERT_AUTHORITY_INVALID.

I have reset TLS certificates as given mailcow.github.io Icon here

. But that seem to not working either.

Here’s my nginx config

server {
  listen 80;
  server_name mail.server.com autodiscover.* autoconfig.*;

  return 301 https://$host$request_uri;
}

server {
  listen 443 ssl http2;
  server_name mail.server.com autodiscover.* autoconfig.*;

  ssl_certificate /opt/mailcow-dockerized/data/assets/ssl/cert.pem;
  ssl_certificate_key /opt/mailcow-dockerized/data/assets/ssl/key.pem;
  ssl_session_timeout 1d;
  ssl_session_cache shared:SSL:50m;
  ssl_session_tickets off;


  ssl_protocols TLSv1.2;
  ssl_ciphers HIGH:!aNULL:!MD5:!SHA1:!kRSA;
  ssl_prefer_server_ciphers off;

  location /Microsoft-Server-ActiveSync {
    proxy_pass http://127.0.0.1:8193/Microsoft-Server-ActiveSync;
    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_connect_timeout 75;
    proxy_send_timeout 3650;
    proxy_read_timeout 3650;
    proxy_buffers 64 256k;
    client_body_buffer_size 512k;
    client_max_body_size 0;
  }

  location / {
    proxy_pass http://127.0.0.1:8193/;
    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    client_max_body_size 0;
  }
}

Here’s mailcow.conf's ports

HTTP_PORT=8193
HTTP_BIND=127.0.0.1

HTTPS_PORT=8194
HTTPS_BIND=127.0.0.1

and here’s the output of bash helper-scripts/expiry-dates.sh

TLS expiry dates:
Postfix: Sep 14 07:34:25 2023 GMT
Dovecot: Sep 14 07:34:25 2023 GMT
Nginx: Jan 17 09:08:00 2037 GMT
  • I have fixed this by updating mailcow and then resetting TLS certificates once again.

I have fixed this by updating mailcow and then resetting TLS certificates once again.

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!

Could you check which certificate was presented during the issue? A invalid certificate authority sounds like there was a self-signed offered to the client.

    pkernstock I have the same problem ssl certificate signed by mailcow

    2 years later
    No one is typing