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!

kingfisher I guess the problem with the installation from 2022 could be that you upgraded it in one single step instead of running the update jumping from version to version. This may have broken things.
Do you have a backup from before upgrading it?

      DocFraggle I would not agree with my case here. I always upgraded my mailcow on the same night as soon as I see a new update. I have never missed any single update of mailcow.

        @‘DocFraggle’#p23818 Ah, that’s a misunderstanding. It’s not the 2022 version, I’ve made every update since then. The database, all files are from 2022, and compared to the relatively new instance that has been well updated, that may be the source of the problem. Some kind of artefact from the ‘old days’.

        I found out what the problem is/was.

        In /opt/mailcow-dockerized/data/web/inc/ was a file called vars.local.inc.php with this content

        <?php
// mailcow Apps - buttons on login screen
$MAILCOW_APPS = "";
// Change theme (default: lumen)
// Needs to be one of those: cerulean, cosmo, cyborg, darkly, flatly, journal, lumen, paper, readable, sandstone,
// simplex, slate, spacelab, superhero, united, yeti
// See https://bootswatch.com/
// WARNING: Only lumen is loaded locally. Enabling any other theme, will download external sources.
$DEFAULT_THEME = 'lumen';
// Rows until pagination begins
$PAGINATION_SIZE = 100;
// Mailbox has POP3 access by default
$MAILBOX_DEFAULT_ATTRIBUTES['pop3_access'] = false;

        Removing it solved the problem with blank page. I found it by comparing a working environment and and narrowing down everything with diff -r.

        What is this file about?

          kingfisher so you mean by removing the file blank page issue gone? Will have to figure out other causes of removal of the file that may come as well as the next update will bring back the file.

            The file is not present on a fresh install on a separate computer. I think it’s an artefact from versions long ago.

              kingfisher so if I remove the file and update it to the latest Moo update, will it start working fine?

                kingfisher I only have the following content in the file. I don’t know if the same is affecting the issue.

                  I think I might have changed the theme from Lumens to materia when initially setup mailcow.

                  Just move it out of the folder and everything is back again :-)

                  i don’t know here should I laugh with the issue or the issue has been sorted within new update after March Mooupdate.

                  I removed the vars.local.inc.php file and updated the mailcow with stable release and it updated fine without the blank page issue and the same is now showing as shown in following:

                  I was still not convinced that the vars.local.inc.php file would be causing the issue, so I copied it back as shown below:

                  And the same mailcow UI came fine. Everything is working fine now without the blank page.

                    mailcow-helper Did you restart Mailcow to check if it still works afterwards? It may be possible that the file isn’t loaded if it wasn’t there during the start of the php container

                        DocFraggle … Yes of course. I did whole down and up 3 times to better check if it’s working or not. Well, I experimented with Mailcow UI Theme from Lumen to materia (I like Google Material Design a lot) and the difference is here:

                        Default UI:

                        Materia UI:

                        so the theme change confirms that var.local.inc.php override is working perfectly fine.

                        If anyone want to try just go to bootswatch.com, download theme’s bootstrap.css. Rename downloaded css file as themename-bootstrap.css and copy it into data/web/css/themes/ folder.
                        then edit data/web/inc/vars.local.inc.php and add $UI_THEME = “materia”;
                        (Use your theme name instead of materia).

                        I haven’t tested if only restarting nginx container would bring the theme back on display so you will have to check that.

                          BTW, to get a quick overview of modified or additional files of your installation you can diff it against the current release tag. Here, for example, diff the “data” directory against release 2025-03b

                          git diff refs/tags/2025-03b data/

                          While you will see some legit diffs like your SSL certificate / private key or your black- and whitelist files you should have found the additional vars.local.inc.php file as well.

                          Maybe this helps someone in the future 🙂

                          Yes, that’s helpful. Even afterwards :-)

                          For an instant overview, only the file names which differ:

                          git diff --name-only refs/tags/2025-03b data/

                          No one is typing