New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SoGo not working after Update #1561
Comments
|
It waits for a table that would be created by opening the mailcow UI. |
|
Hm ok, but when opening the mailcow UI there is only a white screen. No UI There. Also no logs are written that yould give a hint on whats going on here 😕 |
|
That's bad. How did you update mailcow? Probably a merge conflict. Can you mail me AnyDesk access to info@servercow.de? |
|
I used the update bash script. |
|
Can you mail me or post the output of |
|
Git an empty diff. Nothing Changed The only diff i have is added stuff because SELinux was conflicting. Concerning the AnyDesk , you only need the ID right ? |
|
Yes, just the id. |
|
@andryyy Thanks for the aid 👍 , issue is likely related to own firewall configs. |
|
@andryyy It wasnt the FW, it was the umask. I Use a Umask of 0027 and that broke the update. |
|
You have custom rulesets that did override Dockers iptables rules, that is a big issue, too. :-( I will check the "disable ipv6" stuff. |
|
@andryyy Yea but its working now with 0022 and i suspect the stuff you saw in iptables are coming from my other 8 containers besides mailcow. For me this looks fine: Compose/Docker should also handle the firewall stuff via liks and networks and i did not mess with it except opening inbound ports with firewalld :) . Everything should be standard. |
After a Update SoGo cant connect to the DB anymore
I am on commit 1522b83 now
SOGO Logs
Mariadb Logs
Anyone has an idea ?
The text was updated successfully, but these errors were encountered: