Mailcow admin white screen after update #4571
Comments
|
Have the same issue with a fresh install |
|
same here with existing installation after updating today |
|
Just encountered the same issue after upgrading today. Blank screen on /, when going to /SoGo it works without any issues. Sending and receiving email works. |
|
Same thing here. Fresh install today, and white screen for admin |
|
Same issue, fresh install, white page from FQDN and IP as well. Any way to revert to the previous version for the time being? |
|
Same thing here |
|
Same issue here. Also find that /admin would redirect back to a blank /. |
|
This is the error causing the blank page i dont know where this comes from Quick Workaround would be, giving permission with chmod to the folder data/web/templates |
|
Here it comes? |
|
And because of this commit: |
|
The folder data/web/templates -> cache got lost mkdir data/web/templates/cache |
I can confirm, this worked for me. |
|
Please update your mailcows again now... |
Ran the update script again and admin page can load successfully now. |
|
@pjv can you close the issue if it works for you as well? |
|
@DerLinkman I can’t do another update now because too much traffic on the server. I will do early AM tomorrow in my TZ. But I did manually create the directory and restart the stack and that worked, so I will close the issue now and re-open if any trouble with the update tomorrow. Thanks for the fix. |
|
In my case the directory cache had the wrong permissions |
|
I'm having the same issue. It started about 1 month ago or so, I'm not too sure as I don't use the admin page that often. Both /rspamd and /sogo work just fine, but the admin page is blank on any page I try to access (/admin, /user, etc). data/web/templates/cache/ is present and doesn't seem to have any issues. anyone got any ideas, or should I open a new issue? |
|
Today my VM where mailcow ran on freezed and I had to hard reset it. After I did that, I got the same problem was described here. After some time I just changed the cache folder to /tmp in the twig php file and suddenly it worked again. No matter what I do with this folder, delete and create new, chown 82:82, chmod 777, nothing works This folder is cursed Edit: It was the classic problem... partition was full. Extended it and everything works again. |
|
Hello i have the same issue mailcow/unbound:1.19 NGINX Logs : mailcowdockerized-nginx-mailcow-1 | 2023/09/05 09:41:09 [notice] 1#1: using the "epoll" event method PHP Logs REDIS Logs: MYSQL Logs: Except this two message : [/web/templates/cache/](find: /web/templates/cache/*: No such file or directory) mailcow "HEAD /settings.php" 304 I don't have any error i made a docker system prune i am lost |
|
For people encountering this after an update, below solved it for me: My timezone in |
|
I am encountering this issue updating my nightly. tried setting permissions to cache and restarting. Doesnt work. |
Contribution guidelines
I've found a bug and checked that ...
Description
I ran update.sh this morning (May 5) with no errors reported and the mailcow admin is now a blank white screen.
All containers are up and running, mail is working fine, Sogo is working fine.
I rebooted the server, re-ran update.sh, re-started the whole mailcow stack and no effect - still a white screen.
I think that it has been probably a month since the last time I updated mailcow (no issues at that time).
Logs
Steps to reproduce
System information
docker version)docker-compose version)Output of
git diff origin/master, any other changes to the code? If so, please post them:All third-party firewalls and custom iptables rules are unsupported. Please check the Docker docs about how to use Docker with your own ruleset. Nevertheless, iptabels output can help us to help you:
iptables -L -vn:
ip6tables -L -vn:
iptables -L -vn -t nat:
ip6tables -L -vn -t nat:
DNS problems? Please run
docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254(set the IP accordingly, if you changed the internal mailcow network) and post the output:The text was updated successfully, but these errors were encountered: