Hi community, I create this Wiki post to help users to find solutions for frequent issues after update to NC29. This should avoid flooding forum with similar topics and help others identify and solve known issues.
this is a WIKI article - everybody is welcome to contribute. if you feel there is a repeated topic related to nc29 update please add it to the list
Github issues
htaccess issue
The way how Nextcloud check if the data directory might be accessible from remote changed and for this reason new setup_warning is shown:
English:
Your data directory and files are probably accessible from the internet. The .htaccess file is not working. It is strongly recommended that you configure your web server so that the data directory is no longer accessible, or move the data directory outside the web server document root.
German:
Dein Datenverzeichnis und Deine Dateien sind wahrscheinlich vom Internet aus erreichbar. Die .htaccess-Datei funktioniert nicht. Es wird dringend empfohlen, Deinen Webserver dahingehend zu konfigurieren, dass das Datenverzeichnis nicht mehr vom Internet aus erreichbar ist oder dass Du es aus dem Dokument-Root-Verzeichnis des Webservers bewegst.
related threads:
- Admin Overview Error .htaccess file not working / data directory accessible
- After upgrade from 28 to 29 I have "Data directory and your files are probably accessible from the Internet"
- Data directory accessible from the internet
- [FIXED] Htaccess file is not working
- How to test if my files are not accessible from the internet?
Troubleshooting steps:
- review your
trusted_domainsandoverwrite.cli.urlvalues in config.php
(second one is important in case the server has no internet access and could point to internal URL)
well-known issue
English:
Your web server is not properly set up to resolve .well-known URLs, failed on: /.well-known/caldav For more details see the documentation
French:
Votre serveur web n’est pas configuré correctement pour résoudre les URL .well-known, a échoué sur : /.well-known/caldav Pour plus d’information, voir la documentation
problem is missing trailing slash in /remote.php/dav/ reverseproxy rewrite settings.
Nginx proxy manager (notice trailing /)
location = /.well-known/carddav {
return 301 $scheme://$host:$server_port/remote.php/dav/;
}
location = /.well-known/caldav {
return 301 $scheme://$host:$server_port/remote.php/dav/;
}
related threads:
- https://github.com/nextcloud/server/issues/45033
- Nextcloud Hub 8 (29.0.0) Weird error messages
- Nach Update Warning wegen well-known unter nginx
- .well-known warning with external CalDAV provider after upgrade to NC 29
cron not running
Error: Class “OC\BackgroundJob\TimedJob” not found in ..
different apps which are not ready for nc29 now cause the error so far music, backup, old richdocuments (8.4.0-beta.1)
- Unable to connect to 'trusted_domains' error after upgrade to 29.0 beta - #3 by Alexander_Robinson1
- Nextcloud Office breaks cron with call to OC\BackgroundJob\TimedJob · Issue #3523 · nextcloud/richdocuments · GitHub
- Php cron job fails on Nextcloud 29.0.0 Beta · Issue #36 · julien-nc/phonetrack · GitHub
- Cron background job not working after update to 29
cron memory warning
“Used memory grew by more than 10 MB when executing job”
- NC29: Cron warning memory increase
- Warning: "Used memory grew by more than 10 MB when executing job ... UpdateAvailableNotifications"
Random logouts
After upgrading to Nextcloud 29 (and 28.0.5) users get randomly logged out of the instance and have to login again.
A fix is available at
- fix(session): Avoid race condition for cache::get() vs. cache::hasKey() by nickvergessen · Pull Request #45093 · nextcloud/server · GitHub.
and will be included in 29.0.1. - Web Interface forcing logout after upgrade to 28.0.5
The other two are for testing and demonstration / training (both of which run on non standard ports).