I upgraded to 0.24 today and the roundcube interface is no longer working. The login page loads fine but upon clicking the login button, in Chromium I get:
This page isn’t working
example.com is currently unable to handle this request.
HTTP ERROR 500
and in Firefox, I get a blank page. Rebooting did not fix it. Any ideas? The rest of the MIAB seems to work – I can send and receive email using Thunderbird. Thanks in advance!
Note: Changed title because in addition, emails that used to go to gmail without problems seem to have some problem now. See post further down the chain. Never mind, it appears to have been a temporary problem as subsequent emails went through fine.
You can check the php7.0-fpm.log file in /var/log/ and the access.log and error.log files in /var/log/nginx to hopefully get more info about what’s going on. On my systems they are called access.log.1 and error.log.1 for some reason.
It’s strange because the access.log shows a http 500 response, which is an error. The error.log should have more information on it. The php log is empty for me as well, it seems like we’d have to enable logging first. Most likely in /etc/php/7.0/fpm/php.ini.
Can the affected user log in successfully at https://example.com/cloud ?
Still having php5 installed shouldn’t be a problem. It’s the same on my system. I don’t know if it can be uninstalled safely.
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
log_errors = On
Own/Nextcloud broke a while ago and in order to get upgrades to work, I modify the setup program to skip installation (I don’t use Own/Nextcloud anyway).
Other than that, everything is out-of-the-box.
And apparently, something about 0.24’s security has changed and email is automatically flagged as spam or rejected outright. From an email sent to a Gmail account:
Why is this message in Spam? It’s from an address in the example.com domain but has failed example.com’s required tests for authentication.
The status page also shows that everything appears to be fine although it does warn that the domain’s DNSSEC DS record has not been set (it is not a TLD where DNSSEC is available).