Blank Page after Nightly Update - Connection to SoGo fails?

sudo-cpipe

Hi,
to start off, I’m still new to Mailcow & Docker.
Straight to the Problem:
Our Mailcow Server is currently on Nightly Build ‘89ed9147’. For external Authentication we’re using Keycloak connected to our local AD. Traffic also passes through a nginx reverse Proxy. After trying to update to the newest nightly version, the Login Page for our Server stays blank. All containers come back up without any Errors, apart from the SoGo Container which says “Waiting for Schema Update”, I’ve addded a part of the SoGo Logfile below.
Inspecting the Source Code of the Page also stays blank and the Developer Tools only show that its waiting for for server response. NGINX Logs also show nothing unusual.

Let me know, if I any other Logfiles, etc could be helpful.

Here is an outtake of othe SoGo Logs:

2025-02-21 09:26:04,770 WARN received SIGTERM indicating exit request 2025-02-21 09:26:04,771 INFO waiting for processes, syslog-ng, bootstrap-sogo to die 2025-02-21 09:26:05,772 WARN stopped: bootstrap-sogo (terminated by SIGTERM) Feb 21 09:26:05 df344e495ebd syslog-ng[8]: syslog-ng shutting down; version='3.38.1' 2025-02-21 09:26:05,876 INFO stopped: syslog-ng (exit status 0) 2025-02-21 09:26:05,877 WARN stopped: processes (terminated by SIGTERM) 2025-02-21 09:26:06,400 INFO Set uid to user 0 succeeded 2025-02-21 09:26:06,401 INFO supervisord started with pid 1 2025-02-21 09:26:07,403 INFO spawned: 'processes' with pid 7 2025-02-21 09:26:07,405 INFO spawned: 'syslog-ng' with pid 8 2025-02-21 09:26:07,407 INFO spawned: 'bootstrap-sogo' with pid 9 Uptime: 407 Threads: 17 Questions: 788 Slow queries: 0 Opens: 42 Open tables: 35 Queries per second avg: 1.936 Waiting for schema update... [2025-02-21T09:26:07.430782] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; Feb 21 09:26:07 df344e495ebd syslog-ng[8]: syslog-ng starting up; version='3.38.1' 2025-02-21 09:26:08,433 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2025-02-21 09:26:08,433 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2025-02-21 09:26:08,433 INFO success: bootstrap-sogo entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update... 2025-02-21 09:32:23,110 WARN received SIGTERM indicating exit request 2025-02-21 09:32:23,110 INFO waiting for processes, syslog-ng, bootstrap-sogo to die 2025-02-21 09:32:23,112 WARN stopped: bootstrap-sogo (terminated by SIGTERM) 2025-02-21 09:32:23,112 INFO reaped unknown pid 623 (exit status 0) Feb 21 09:32:23 df344e495ebd syslog-ng[8]: syslog-ng shutting down; version='3.38.1' 2025-02-21 09:32:23,215 INFO stopped: syslog-ng (exit status 0) 2025-02-21 09:32:23,216 WARN stopped: processes (terminated by SIGTERM) 2025-02-21 09:32:23,705 INFO Set uid to user 0 succeeded 2025-02-21 09:32:23,706 INFO supervisord started with pid 1 2025-02-21 09:32:24,709 INFO spawned: 'processes' with pid 7 2025-02-21 09:32:24,710 INFO spawned: 'syslog-ng' with pid 8 2025-02-21 09:32:24,711 INFO spawned: 'bootstrap-sogo' with pid 9 Uptime: 784 Threads: 17 Questions: 1549 Slow queries: 0 Opens: 51 Open tables: 44 Queries per second avg: 1.975 Waiting for schema update... [2025-02-21T09:32:24.733926] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; Feb 21 09:32:24 df344e495ebd syslog-ng[8]: syslog-ng starting up; version='3.38.1' 2025-02-21 09:32:25,736 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2025-02-21 09:32:25,736 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2025-02-21 09:32:25,736 INFO success: bootstrap-sogo entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Waiting for schema update... Waiting for schema update... Waiting for schema update... Waiting for schema update...

Thanks in Advance!
Best,
cpipe

sudo-cpipe

After trying to access SoGo through different Links and Adresses, i get the following error in the nginx container:

2025/02/21 09:40:40 [error] 20#20: *242 connect() failed (111: Connection refused) while connecting to upstream, client: 10.50.x.x, server: mail-extern.xxx.com, request: "GET /SOGo/so/x.x@extern.x.com/Mail/view HTTP/2.0", upstream: "http://172.22.x.x:20000/SOGo/so/x.x@extern.x.com/Mail/view", host: "extern.x.com"

pkernstock

The code for the log message seems to be here:
mailcow/mailcow-dockerizedblob/120366fec7b9ea79c9f563a81fa5ea30321ab0b2/data/Dockerfiles/sogo/bootstrap-sogo.sh#L16-L25

So I think something went wrong and did not properly update the mailcow database schema. Not sure which container is responsible for this - maybe the phpfpm? Can you run the SELECT statements and see what its values are?

sudo-cpipe

Thanks for your quick reply!

So i ran the the following statements:
SELECT version FROM versions WHERE application = 'db_schema';
Output:
+---------------+ | version | +---------------+ | 30072023_1600 | +---------------+ 1 row in set (0.000 sec)

The second Statement is basically the same.

After a little search i can see that the “new” Database Schema Version, which i found in the ../data/web/inc/init_db.inc.php, is: 27012025_1555
I’m guessing that this mismatch could be the root of my problem and if so how would i go about fixing this?

chrisbish

Have also ran into this issue of blank pages after upgrading to the nightly.

Is there a fix for this yet?