Hello,

I’ve setup my mailcow server with a reverse proxy.

Now I have the problem that when I want to add a TOTP to my authenticator the qr code is not showing up.

How can I fix this?

This is my nginx config:

server {
  listen 80 default_server;
  server_name mailcow.example.com autodiscover.* autoconfig.*;
  return 301 https://$host$request_uri;
}
server {
  listen 443 ssl http2;
  server_name mailcow.example.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;

  # See https://ssl-config.mozilla.org/#server=nginx for the latest ssl settings recommendations
  # An example config is given below
  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:8080/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 512k; # Needed since the 2022-04 Update for SOGo
    client_body_buffer_size 512k;
    client_max_body_size 0;
  }

  location / {
    proxy_pass http://127.0.0.1:8080/;
    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;
  # The following Proxy Buffers has to be set if you want to use SOGo after the 2022-04 (April 2022) Update
  # Otherwise a Login will fail like this: https://github.com/mailcow/mailcow-dockerized/issues/4537
    proxy_buffer_size 128k;
    proxy_buffers 64 512k;
    proxy_busy_buffers_size 512k;
  }
}

Here’s a picture of my described problem:

Thank you for your help.

Does the nginx log show a problem on server side, or is it with your browser (adblock, script blocking etc)

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!

Hi,

I think that SoGo is running very slow. I have enough ram and cpu.

When I want to see the needed dns records it loads forever. And navigation through the webinterface takes very long too.

Is there something I can do?

    s3tupw1zard I have enough ram and cpu.

    How much is “enough”?

    s3tupw1zard I think that SoGo is running very slow.

    The 2FA screen you showed is not in SOGo, so SOGo is not relevant, as it has its own 2FA which is independent of Mailcow UI.
    This is why I asked you to check the nginx logs, and ideally also php-fpm container logs.

    s3tupw1zard When I want to see the needed dns records it loads forever.

    Why don’t you look them up on your domain registrar?

    YouTube Icon Didi, der Doppelgänger | ich brauche mehr Details

    No one is typing