I had a full storage occurence 🤦♂️, sql-container failing because of it, but got it sorted and the entire stack back up and running.
However, afterwards the rspamd web UI will not open up.
I get the standard “Preparing ..”-page
What is happening?
Please do not stop the stack while we are initializing the database or do other preparations.
What is happening? - Nginx cannot connect to an upstream server or other services are not ready yet.
This is fine if mailcow was just installed or updated and can take a few minutes to complete.
Please check the logs or contact support if the error persists.
Checking the recommended logs I find this:
mailcowdockerized-nginx-mailcow-1 | 172.22.1.13 - - [11/Apr/2024:09:38:30 +0200] "GET / HTTP/1.1" 200 15 "-" "check_http/v (nagios-plugins 2.4.5)"
mailcowdockerized-nginx-mailcow-1 | 172.22.1.12 - - [11/Apr/2024:09:38:31 +0200] "POST /pipe.php HTTP/1.1" 200 5 "-" "rspamd-3.7.5"
mailcowdockerized-nginx-mailcow-1 | 2024/04/11 09:38:39 [error] 20#20: *9174 connect() failed (111: Connection refused) while connecting to upstream, client: 172.17.10.21, server: mail.redacted.no, request: "GET /rspamd/ HTTP/1.1", upstream: "http://172.22.1.9:11334/", host: "mail.redacted.no"
mailcowdockerized-nginx-mailcow-1 | 172.17.10.21 - - [11/Apr/2024:09:38:39 +0200] "GET /rspamd/ HTTP/1.1" 502 2015 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36"
mailcowdockerized-nginx-mailcow-1 | 172.22.1.12 - - [11/Apr/2024:09:38:40 +0200] "HEAD /settings.php HTTP/1.1" 304 0 "-" "rspamd-3.7.5"
Without being sure how it all connects, it seems maybe the webserver serving the UI doesn’t come up, based on the refused log.
If I try to check the rspamd logs in the normal mailcow admin UI, it works fine, (connected via API?).
So rspamd works as normal, except for the web UI.