Hello, I'm facing an issue on multiple servers since the last update: SOGo display only a blank page. Here is the log showing up in the web browser console: ```js [Error] ReferenceError: Can't find variable: CKEDITOR Global Code (custom-sogo.js:4) ``` Here is the incriminated file's content: ```js // Custom SOGo JS // Change the visible font-size in the editor, this does not change the font of a html message by default CKEDITOR.addCss("body {font-size: 16px !important}"); // Enable scayt by default //CKEDITOR.config.scayt_autoStartup = true; ``` However, I have more interesting logs from the SOGo Docker container: ``` [61]: an error occurred when caching value for key REDACTED@REDACTED.net+defaults': "ITEM TOO BIG" ``` I'm running Mailcow v2024-08a, on a up-to-date Debian 12 host with 8GB RAM, 2GB SWAP and not customization **at all**. Here is my `mailcow.conf` file: ``` mathilde@REDACTED:~$ sudo cat /opt/mailcow-dockerized/mailcow.conf [sudo] password for mathilde: # ------------------------------ # mailcow web ui configuration # ------------------------------ # example.org is _not_ a valid hostname, use a fqdn here. # Default admin user is "admin" # Default password is "moohoo" MAILCOW_HOSTNAME=REDACTED # ------------------------------ # SQL database configuration # ------------------------------ DBNAME=mailcow DBUSER=mailcow # Please use long, random alphanumeric strings (A-Za-z0-9) DBPASS=REDACTED DBROOT=REDACTED # ------------------------------ # HTTP/S Bindings # ------------------------------ # You should use HTTPS, but in case of SSL offloaded reverse proxies: # Might be important: This will also change the binding within the container. # If you use a proxy within Docker, point it to the ports you set below. HTTP_PORT=80 HTTP_BIND= HTTPS_PORT=443 HTTPS_BIND= # ------------------------------ # Other bindings # ------------------------------ # You should leave that alone # Format: 11.22.33.44:25 or 0.0.0.0:465 etc. # Do _not_ use IP:PORT in HTTP(S)_BIND or HTTP(S)_PORT SMTP_PORT=25 SMTPS_PORT=465 SUBMISSION_PORT=587 IMAP_PORT=143 IMAPS_PORT=993 POP_PORT=110 POPS_PORT=995 SIEVE_PORT=4190 DOVEADM_PORT=127.0.0.1:19991 SQL_PORT=127.0.0.1:13306 SOLR_PORT=127.0.0.1:18983 # Your timezone TZ=Europe/Paris # Fixed project name COMPOSE_PROJECT_NAME=mailcowdockerized # Set this to "allow" to enable the anyone pseudo user. Disabled by default. # When enabled, ACL can be created, that apply to "All authenticated users" # This should probably only be activated on mail hosts, that are used exclusivly by one organisation. # Otherwise a user might share data with too many other users. ACL_ANYONE=disallow # Garbage collector cleanup # Deleted domains and mailboxes are moved to /var/vmail/_garbage/timestamp_sanitizedstring # How long should objects remain in the garbage until they are being deleted? (value in minutes) # Check interval is hourly MAILDIR_GC_TIME=1440 # Additional SAN for the certificate # # You can use wildcard records to create specific names for every domain you add to mailcow. # Example: Add domains "example.com" and "example.net" to mailcow, change ADDITIONAL_SAN to a value like: #ADDITIONAL_SAN=imap.*,smtp.* # This will expand the certificate to "imap.example.com", "smtp.example.com", "imap.example.net", "imap.example.net" # plus every domain you add in the future. # # You can also just add static names... #ADDITIONAL_SAN=srv1.example.net # ...or combine wildcard and static names: #ADDITIONAL_SAN=imap.*,srv1.example.com # ADDITIONAL_SAN= # Skip running ACME (acme-mailcow, Let's Encrypt certs) - y/n SKIP_LETS_ENCRYPT=n # Create seperate certificates for all domains - y/n # this will allow adding more than 100 domains, but some email clients will not be able to connect with alternative hostnames # see https://wiki.dovecot.org/SSL/SNIClientSupport ENABLE_SSL_SNI=n # Skip IPv4 check in ACME container - y/n SKIP_IP_CHECK=n # Skip HTTP verification in ACME container - y/n SKIP_HTTP_VERIFICATION=n # Skip ClamAV (clamd-mailcow) anti-virus (Rspamd will auto-detect a missing ClamAV container) - y/n SKIP_CLAMD=y # Skip Solr on low-memory systems or if you do not want to store a readable index of your mails in solr-vol-1. SKIP_SOLR=n # Solr heap size in MB, there is no recommendation, please see Solr docs. # Solr is a prone to run OOM and should be monitored. Unmonitored Solr setups are not recommended. SOLR_HEAP=4096 # Enable watchdog (watchdog-mailcow) to restart unhealthy containers (experimental) USE_WATCHDOG=y # Allow admins to log into SOGo as email user (without any password) ALLOW_ADMIN_EMAIL_LOGIN=y # Send notifications by mail (no DKIM signature, sent from watchdog@MAILCOW_HOSTNAME) # Can by multiple rcpts, NO quotation marks #WATCHDOG_NOTIFY_EMAIL=a@example.com,b@example.com,c@example.com WATCHDOG_NOTIFY_EMAIL=REDACTED # Notify about banned IP (includes whois lookup) WATCHDOG_NOTIFY_BAN=n # Max log lines per service to keep in Redis logs LOG_LINES=9999 # Internal IPv4 /24 subnet, format n.n.n (expands to n.n.n.0/24) IPV4_NETWORK=172.22.1 # Internal IPv6 subnet in fc00::/7 IPV6_NETWORK=fd4d:6169:6c63:6f77::/64 # Use this IPv4 for outgoing connections (SNAT) SNAT_TO_SOURCE= # Use this IPv6 for outgoing connections (SNAT) SNAT6_TO_SOURCE= # Create or override API key for web ui # You _must_ define API_ALLOW_FROM, which is a comma separated list of IPs # API_KEY allowed chars: a-z, A-Z, 0-9, - #API_KEY= #API_ALLOW_FROM=172.22.1.1,127.0.0.1 # mail_home is ~/Maildir MAILDIR_SUB=Maildir # SOGo session timeout in minutes SOGO_EXPIRE_SESSION=480 # Checks if mailcow is an open relay. Requires a SAL. More checks will follow. # No data is collected. Opt-in and anonymous. # Will only work with unmodified mailcow setups. WATCHDOG_EXTERNAL_CHECKS=n REDIS_PORT=127.0.0.1:7654 # Create or override read-only API key for web UI #API_KEY_READ_ONLY= # Skip SOGo: Will disable SOGo integration and therefore webmail, DAV protocols and ActiveSync support (experimental, unsupported, not fully implemented) - y/n SKIP_SOGO=n # DOVECOT_MASTER_USER and _PASS must _both_ be provided. No special chars. # Empty by default to auto-generate master user and password on start. # User expands to DOVECOT_MASTER_USER@mailcow.local # LEAVE EMPTY IF UNSURE DOVECOT_MASTER_USER= # LEAVE EMPTY IF UNSURE DOVECOT_MASTER_PASS= # Password hash algorithm # Only certain password hash algorithm are supported. For a fully list of supported schemes, # see https://mailcow.github.io/mailcow-dockerized-docs/model-passwd/ MAILCOW_PASS_SCHEME=BLF-CRYPT # Additional server names for mailcow UI # # Specify alternative addresses for the mailcow UI to respond to # This is useful when you set mail.* as ADDITIONAL_SAN and want to make sure mail.maildomain.com will always point to the mailcow UI. # If the server name does not match a known site, Nginx decides by best-guess and may redirect users to the wrong web root. # You can understand this as server_name directive in Nginx. # Comma separated list without spaces! Example: ADDITIONAL_SERVER_NAMES=a.b.c,d.e.f ADDITIONAL_SERVER_NAMES= # Subject for watchdog mails. Defaults to "Watchdog ALERT" followed by the error message. WATCHDOG_SUBJECT="Watchdog ALERT mx.clic.email" # Lets Encrypt registration contact information # Optional: Leave empty for none # This value is only used on first order! # Setting it at a later point will require the following steps: # https://mailcow.github.io/mailcow-dockerized-docs/debug-reset-tls/ ACME_CONTACT= # Enable watchdog verbose logging WATCHDOG_VERBOSE=n # WebAuthn device manufacturer verification # After setting WEBAUTHN_ONLY_TRUSTED_VENDORS=y only devices from trusted manufacturers are allowed # root certificates can be placed for validation under mailcow-dockerized/data/web/inc/lib/WebAuthn/rootCertificates WEBAUTHN_ONLY_TRUSTED_VENDORS=n # Used Docker Compose version # Switch here between native (compose plugin) and standalone # For more informations take a look at the mailcow docs regarding the configuration options. # Normally this should be untouched but if you decided to use either of those you can switch it manually here. # Please be aware that at least one of those variants should be installed on your maschine or mailcow will fail. DOCKER_COMPOSE_VERSION=standalone # Spamhaus Data Query Service Key # Optional: Leave empty for none # Enter your key here if you are using a blocked ASN (OVH, AWS, Cloudflare e.g) for the unregistered Spamhaus Blocklist. # If empty, it will completely disable Spamhaus blocklists if it detects that you are running on a server using a blocked AS. # Otherwise it will work as usual. SPAMHAUS_DQS_KEY= # Send notifications to a webhook URL that receives a POST request with the content type "application/json". # You can use this to send notifications to services like Discord, Slack and others. #WATCHDOG_NOTIFY_WEBHOOK=https://discord.com/api/webhooks/XXXXXXXXXXXXXXXXXXX/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX # JSON body included in the webhook POST request. Needs to be in single quotes. # Following variables are available: SUBJECT, BODY #WATCHDOG_NOTIFY_WEBHOOK_BODY='{"username": "mailcow Watchdog", "content": "**${SUBJECT}**\n${BODY}"}' # Send a notification when the watchdog is started. WATCHDOG_NOTIFY_START=y # Skip Unbound (DNS Resolver) Healthchecks (NOT Recommended!) - y/n SKIP_UNBOUND_HEALTHCHECK=n # Prevent netfilter from setting an iptables/nftables rule to isolate the mailcow docker network - y/n # CAUTION: Disabling this may expose container ports to other neighbors on the same subnet, even if the ports are bound to localhost DISABLE_NETFILTER_ISOLATION_RULE=n # Obtain certificates for autodiscover.* and autoconfig.* domains. # This can be useful to switch off in case you are in a scenario where a reverse proxy already handles those. # There are mixed scenarios where ports 80,443 are occupied and you do not want to share certs # between services. So acme-mailcow obtains for maildomains and all web-things get handled # in the reverse proxy. AUTODISCOVER_SAN=y # Experimental FTS feature FLATCURVE_EXPERIMENTAL=y ``` Thanks in advance for your help!

Have you tried to clear the cache of your browser? did you try to re-run the update.sh? Maybe some containers were not pulled due to timeouts.

@"esackbauer"#p18089 thanks for your suggestions. - I happens on all browsers, from different persons, networks, etc - I've thought maybe I was missing something, so I ran `./update.sh` again on both servers - I checked the state of the containers from the web interface and using `docker ps -a` and everything is in order

As nobody else has this problem, you should start to tell us about your specific setup. WAF? Reverse proxy? Why are you using docker compose standalone variant, when the installation docs tell you to use the plugin variant? What are your docker and docker-compose versions?

@"esackbauer"#p18094 thanks for your reply. I believe I mentioned everything needed to be known. See below for the answers to your questions: > @"esackbauer"#p18094 WAF? No extra firewall or anything, bare Mailcow instance. > @"esackbauer"#p18094 Reverse proxy? No reverse proxy (Nginx, HAProxy, Apache HTTPd or whatsoever). > @"esackbauer"#p18094 Why are you using docker compose standalone variant, when the installation docs tell you to use the plugin variant? Because both instances predate the mere existence of docker compose as a plugin. I don't recall any release notes announcing the deprecation of `docker-compose` in favor of `docker compose`. > @"esackbauer"#p18094 What are your docker and docker-compose versions? - Docker version 27.2.0, build 3ab4256 - Docker Compose version v2.24.5 Thanks again for your help!

> @"mathilde"#p18095 Because both instances predate the mere existence of docker compose as a plugin. Not really. Please clarify this. Do you have both installed? If yes, what are the version numbers for each of them? If you do changes and then use docker compose (without dash) when making changes, mailcow update might get confused, because it expects the standalone variant (with dash) as in your mailcow.conf is `DOCKER_COMPOSE_VERSION=standalone`. It must be somewhere in your specific setup.

> @"esackbauer"#p18096 Please clarify this. Do you have both installed? No, I have not. ``` mathilde@REDACTED:~$ dpkg -l | grep docker ii docker-ce 5:27.2.0-1~debian.12~bookworm amd64 Docker: the open-source application container engine ii docker-ce-cli 5:27.2.0-1~debian.12~bookworm amd64 Docker CLI: the open-source application container engine ii docker-ce-rootless-extras 5:27.2.0-1~debian.12~bookworm amd64 Rootless support for Docker. ``` See also: ``` mathilde@REDACTED:~$ file /usr/local/bin/docker-compose /usr/local/bin/docker-compose: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=zvVKxZLLiydHMsnu1qqO/b3S_ydudojs1Aimp3uRX/XtztaO16VodJDgWV0NPb/p-xJ5TGMY_BoQukQzaaX, not stripped ``` > @"esackbauer"#p18096 If you do changes and then use docker compose (without dash) when making changes, mailcow update might get confused, because it expects the standalone variant (with dash) as in your mailcow.conf is DOCKER_COMPOSE_VERSION=standalone. I understand this quite well. I have always and only used `docker-compose`, as `docker compose` was never installed on those machines. > @"mathilde"#p18086 However, I have more interesting logs from the SOGo Docker container: > ``` > [61]: an error occurred when caching value for key REDACTED@REDACTED.n > ``` Can someone help me with this issue, I think it might be the root cause of the problem I'm encountering. Have someone else had to deal with that kind of error message when using SOGo with Memcached?

> @"mathilde"#p18097 I have always used docker-compose as docker compose was never installed on those machines. Ok, so no problem from that side. SELinux or UFW active? Try to switch them off. I would suggest you open an issue on Github then, to have the devs a closer look.

> @"esackbauer"#p18099 SELinux or UFW active? No SELinux enabled, nor UFW, as mentioned in my previous message:@"mathilde"#p18095. Thanks for your suggestion to open a GitHub issue. I'm quite reluctant to use GitHub, alas, I guess I don't have much choice aymore... Except maybe if @"DerLinkman"#1496 would be so kind to take a quick look here directly?

Seems like you or more the instances you maintain have modified SOGOs JS files. But with SOGo 5.11.0 SOGo updated the CKEDITOR to a newer version (see https://www.sogo.nu/news/2024/sogo-v5110-released.html) maybe it is broken due to this, but this is your custom stuff, no mailcow issue here, as we always only retain stock mailcow installations or installations not heavily modified.... > @"[unknown]"#p18095 Because both instances predate the mere existence of docker compose as a plugin. I don’t recall any release notes announcing the deprecation of docker-compose in favor of docker compose. There was no one. As long as docker is using compose v2 then it is fine, no matter which (standalone or plugin)

@"DerLinkman"#p18101 thanks for your reply! I have not modified SOGo JS files. My only modification are the name of the application and the favicon which is documented in your [administrator guide](https://docs.mailcow.email/manual-guides/SOGo/u_e-sogo/#change-favicon). See: ```diff mathilde@REDACTED:/opt/mailcow-dockerized$ sudo git diff origin/master [sudo] password for mathilde: diff --git a/data/conf/postfix/main.cf b/data/conf/postfix/main.cf index 6a87f2ec..56684644 100644 --- a/data/conf/postfix/main.cf +++ b/data/conf/postfix/main.cf @@ -173,3 +173,36 @@ parent_domain_matches_subdomains = debug_peer_list,fast_flush_domains,mynetworks # DO NOT EDIT ANYTHING BELOW # # Overrides # + +postscreen_dnsbl_sites = wl.mailspike.net=127.0.0.[18;19;20]*-2 + hostkarma.junkemailfilter.com=127.0.0.1*-2 + list.dnswl.org=127.0.[0..255].0*-2 + list.dnswl.org=127.0.[0..255].1*-4 + list.dnswl.org=127.0.[0..255].2*-6 + list.dnswl.org=127.0.[0..255].3*-8 + ix.dnsbl.manitu.net*2 + bl.spamcop.net*2 + bl.suomispam.net*2 + hostkarma.junkemailfilter.com=127.0.0.2*3 + hostkarma.junkemailfilter.com=127.0.0.4*2 + hostkarma.junkemailfilter.com=127.0.1.2*1 + backscatter.spameatingmonkey.net*2 + bl.ipv6.spameatingmonkey.net*2 + bl.spameatingmonkey.net*2 + b.barracudacentral.org=127.0.0.2*7 + bl.mailspike.net=127.0.0.2*5 + bl.mailspike.net=127.0.0.[10;11;12]*4 + dnsbl.sorbs.net=127.0.0.10*8 + dnsbl.sorbs.net=127.0.0.5*6 + dnsbl.sorbs.net=127.0.0.7*3 + dnsbl.sorbs.net=127.0.0.8*2 + dnsbl.sorbs.net=127.0.0.6*2 + dnsbl.sorbs.net=127.0.0.9*2 + zen.spamhaus.org=127.0.0.[10;11]*8 + zen.spamhaus.org=127.0.0.[4..7]*6 + zen.spamhaus.org=127.0.0.3*4 + zen.spamhaus.org=127.0.0.2*3 + +# User Overrides +myhostname = REDACTED + diff --git a/data/conf/rspamd/local.d/spamassassin.conf b/data/conf/rspamd/local.d/spamassassin.conf deleted file mode 100644 index d091af63..00000000 --- a/data/conf/rspamd/local.d/spamassassin.conf +++ /dev/null @@ -1 +0,0 @@ -ruleset = "/etc/rspamd/custom/sa-rules"; diff --git a/data/conf/sogo/custom-favicon.ico b/data/conf/sogo/custom-favicon.ico index 4d5cb322..bf3d219b 100644 Binary files a/data/conf/sogo/custom-favicon.ico and b/data/conf/sogo/custom-favicon.ico differ diff --git a/data/conf/sogo/sogo.conf b/data/conf/sogo/sogo.conf index d398eb05..445c0794 100644 --- a/data/conf/sogo/sogo.conf +++ b/data/conf/sogo/sogo.conf @@ -5,7 +5,7 @@ PrivateDAndTViewer ); - WOWorkersCount = "20"; + WOWorkersCount = "10"; SOGoACLsSendEMailNotifications = YES; SOGoAppointmentSendEMailNotifications = YES; SOGoDraftsFolderName = "Drafts"; @@ -39,14 +39,15 @@ WOPort = "0.0.0.0:20000"; SOGoMemcachedHost = "memcached"; - SOGoLanguage = English; + SOGoLanguage = French; + SOGoTimeZone = Europe/Paris; SOGoMailAuxiliaryUserAccountsEnabled = YES; // SOGoCreateIdentitiesDisabled = NO; SOGoMailCustomFromEnabled = YES; SOGoMailingMechanism = smtp; SOGoSMTPAuthenticationType = plain; - SxVMemLimit = 384; + SxVMemLimit = 512; SOGoMaximumPingInterval = 3540; @@ -63,8 +64,9 @@ WONoDetach = YES; SOGoIMAPAclConformsToIMAPExt = Yes; - SOGoPageTitle = "SOGo Groupware"; + SOGoPageTitle = "SOGo"; SOGoFirstDayOfWeek = "1"; + SOGoFirstWeekOfYear = "First4DayWeek"; SOGoSieveFolderEncoding = "UTF-8"; SOGoPasswordChangeEnabled = NO; diff --git a/data/web/favicon.png b/data/web/favicon.png index 69eb2fcd..bf3d219b 100644 Binary files a/data/web/favicon.png and b/data/web/favicon.png differ diff --git a/docker-compose.yml b/docker-compose.yml index cf0a028f..16789083 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -613,36 +613,6 @@ services: aliases: - ofelia - ipv6nat-mailcow: - depends_on: - - unbound-mailcow - - mysql-mailcow - - redis-mailcow - - clamd-mailcow - - rspamd-mailcow - - php-fpm-mailcow - - sogo-mailcow - - dovecot-mailcow - - postfix-mailcow - - memcached-mailcow - - nginx-mailcow - - acme-mailcow - - netfilter-mailcow - - watchdog-mailcow - - dockerapi-mailcow - - solr-mailcow - environment: - - TZ=${TZ} - image: robbertkl/ipv6nat - security_opt: - - label=disable - restart: always - privileged: true - network_mode: "host" - volumes: - - /var/run/docker.sock:/var/run/docker.sock:ro - - /lib/modules:/lib/modules:ro - networks: mailcow-network: driver: bridge ``` This is only Mailcow stuff that I never ever touched: ```js mathilde@REDACTED:/opt/mailcow-dockerized$ sudo cat data/conf/sogo/custom-theme.js /* EXAMPLE - EXAMPLE - EXAMPLE - EXAMPLE - EXAMPLE - EXAMPLE - EXAMPLE (function() { 'use strict'; angular.module('SOGo.Common') .config(configure) configure.$inject = ['$mdThemingProvider']; function configure($mdThemingProvider) { var greyMap = $mdThemingProvider.extendPalette('grey', { '200': 'F5F5F5', '300': 'E5E5E5', '1000': '4C566A' }); var greenCow = $mdThemingProvider.extendPalette('green', { '600': 'E5E5E5' }); $mdThemingProvider.definePalette('frost-grey', greyMap); $mdThemingProvider.definePalette('green-cow', greenCow); $mdThemingProvider.theme('default') .primaryPalette('green-cow', { 'default': '400', 'hue-1': '400', 'hue-2': '600', 'hue-3': 'A700' }) .accentPalette('green', { 'default': '600', 'hue-1': '300', 'hue-2': '300', 'hue-3': 'A700' }) .backgroundPalette('frost-grey'); $mdThemingProvider.generateThemesOnDemand(false); } })(); */ ``` Also, I forgot to mention that, but it doesn't impact all email addresses on the instance. So far only one or two are on each ones. Sometimes the page load, sometimes not. But much more often not than the opposite. Hence the lead on the memcached issue?

SOGo blank page, memcached issue?

mathilde

DocFraggle I guess, even better for all the recipient’s mailboxes 😃

Indeed! I only send (and read) emails in plain text format, while still be able to include a lot of rich content. Alas, people want to use HTML with all the bells and whistles… 😩

mathilde

mathilde annnnnd we are back with the issue. 😥

Maybe SOGo v5.11.2 would improve the state of this? Some fixes for blank pages and loading times announced: https://www.sogo.nu/news/2024/sogo-v5111-released.html

« Previous Page