I am using Mailcow (dockerized) for two years and it was perfectly running until I decided to upgrade from PHP 7.4 to PHP 8.2. After this upgrade, I could not access mailcow any longer (not sure if that update is related, but something must have happened during this process). The domain name successfully points to the public www folder but I cannot access any docker container (mailcow). The ports do not respond.
For a few days I am now trying to find a solution to get my mail.domain.tld again to access mailcow UI and domain.tld/sogo to reach SoGo (right now: 404 error for SOGo). I sent a test e-mail to one of the inboxes on that mailcow server and it came back with an error.
I installed Portainer now where all containers are successfully listed, I installed NGINX (running besides Apache now) trying to manually set up a reverse proxy. Without success. I also just installed NGINX Proxy Manager in Portainer.
In Portainer I can access both the Portainer and NGINX Proxy Manager containers/apps using (clicking on) the port number (domain.tld:port). But trying the same with mailcowdockerized container ports results in error messages in the browser (“This site can’t be reached. [IP number] refused to connect.”).
As mentioned above, I manually tried to set up NGINX proxy following these instructions: https://docs.mailcow.email/post_installation/reverse-proxy/r_p-nginx/
After that, mail.domain.tld was pointing to an error page in the browser saying:
"What is happening?
Please do not stop the stack while we are initializing the database or do other preparations. (…)"
I tried out a lot but without success so far.
Can anyone help? Thanks!