# Frequent Nextcloud 29 (Hub 8) update issues **URL:** \ **Category:** ℹ️ Support\ **Tags:** nc29, htaccess, setup\_warning\_wellknown, setup\_warning, ram\ **Created:** [April 29, 2024, 8:15pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897 "2024-04-29T20:15:28Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [April 29, 2024, 8:15pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/1 "2024-04-29T20:15:28Z")
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 [Github tag 29-feedback](https://github.com/nextcloud/server/labels/29-feedback) # #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: ```auto 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](https://help.nextcloud.com/t/admin-overview-error-htaccess-file-not-working-data-directory-accessible/189807) - [After upgrade from 28 to 29 I have "Data directory and your files are probably accessible from the Internet"](https://help.nextcloud.com/t/after-upgrade-from-28-to-29-i-have-data-directory-and-your-files-are-probably-accessible-from-the-internet/189882) - [Data directory accessible from the internet](https://help.nextcloud.com/t/data-directory-accessible-from-the-internet/14507) - [[FIXED] Htaccess file is not working](https://help.nextcloud.com/t/fixed-htaccess-file-is-not-working/4225) - [How to test if my files are not accessible from the internet?](https://help.nextcloud.com/t/how-to-test-if-my-files-are-not-accessible-from-the-internet/193397) Troubleshooting steps: - review your `trusted_domains` and `overwrite.cli.url` values in config.php (second one is important in case the server has no internet access and could point to internal URL) # well-known issue ```auto 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.~~ trailing slash is optional from 29.0.4 [fix(settings): make trailing slash for caldav/carddav redirects optional by MichaIng · Pull Request #46079 · nextcloud/server · GitHub](https://github.com/nextcloud/server/pull/46079) > **Nginx proxy manager (notice trailing /)** > > ```auto > 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](https://github.com/nextcloud/server/issues/45033) - [Nextcloud Hub 8 (29.0.0) Weird error messages](https://help.nextcloud.com/t/nextcloud-hub-8-29-0-0-weird-error-messages/189667) - [Nach Update Warning wegen well-known unter nginx](https://help.nextcloud.com/t/nach-update-warning-wegen-well-known-unter-nginx/188978) - [.well-known warning with external CalDAV provider after upgrade to NC 29](https://help.nextcloud.com/t/well-known-warning-with-external-caldav-provider-after-upgrade-to-nc-29/193280) # 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](https://help.nextcloud.com/t/unable-to-connect-to-trusted-domains-error-after-upgrade-to-29-0-beta/184696/3) - [Nextcloud Office breaks cron with call to OC\BackgroundJob\TimedJob · Issue #3523 · nextcloud/richdocuments · GitHub](https://github.com/nextcloud/richdocuments/issues/3523) - [Php cron job fails on Nextcloud 29.0.0 Beta · Issue #36 · julien-nc/phonetrack · GitHub](https://github.com/julien-nc/phonetrack/issues/36) - [Cron background job not working after update to 29](https://help.nextcloud.com/t/cron-background-job-not-working-after-update-to-29/190321) # cron memory warning “Used memory grew by more than 10 MB when executing job”. should be less visible from 29.0.4 as 10MB is debug and 300MB info level from 29.0.4 [https://github.com/nextcloud/server/pull/45530](https://github.com/nextcloud/server/pull/45530) - [NC29: Cron warning memory increase](https://help.nextcloud.com/t/cron-warning-memory-increase/189417) - [Warning: "Used memory grew by more than 10 MB when executing job ... UpdateAvailableNotifications"](https://help.nextcloud.com/t/warning-used-memory-grew-by-more-than-10-mb-when-executing-job-updateavailablenotifications/190168) # 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](https://github.com/nextcloud/server/pull/45093). and will be included in 29.0.1. - [Web Interface forcing logout after upgrade to 28.0.5](https://help.nextcloud.com/t/web-interface-forcing-logout-after-upgrade-to-28-0-5/189651) # maintenance mode (Polls) - [Nextcloud Maintanance Mode upgrading to NC29 (due to Polls 7.1.0)](https://help.nextcloud.com/t/nextcloud-maintanance-mode-upgrading-to-nc29-due-to-polls-7-1-0/194963) - [Maintenance mode after update to Polls 7.1.0 · Issue #3551 · nextcloud/polls · GitHub](https://github.com/nextcloud/polls/issues/3551) # mimetype migration issue ```auto One or more mimetype migrations are available. Occasionally new mimetypes are added to better handle certain file types. Migrating the mimetypes take a long time on larger instances so this is not done automatically during upgrades. Use the command `occ maintenance:repair --include-expensive` to perform the migrations. ``` basically the message ships the answer already: > Use the command `occ maintenance:repair --include-expensive` to perform the migrations. but seems to be a bug in 29.0.5 so many users struggle with the issue - [Mimetype Migration Issue After Updating to 29.0.5](https://help.nextcloud.com/t/mimetype-migration-issue-after-updating-to-29-0-5/201318) ---
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [April 29, 2024, 8:16pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/2 "2024-04-29T20:16:58Z")
---
**Author:** ![AJV](https://help.nextcloud.com/letter_avatar/ajv/32/6_22734026db12803ebb3e059622ac3534.png) [@AJV](https://help.nextcloud.com/u/AJV)\ **Post date:** [April 30, 2024, 11:36am UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/3 "2024-04-30T11:36:26Z")
I have this issue on one of my three NC29 servers - my production server 😅 The other two are for testing and demonstration / training (both of which run on non standard ports). All three have been working perfectly prior to NC29. I have checked all the .htaccess and config.php files to no avail. In any case my data directory is not under the server root! FYI I am running on up to date openSUSE 15.5 - PHP 8.3.6 (fpm-fcgi) - Apache/2.4.51 - https enabled and enforced on all domains My assessment of the situation from reading and checking is this is probably a NC29 reporting bug and I believe it has been reported as such, looking for confirmation one way or another. ---
**Author:** ![AJV](https://help.nextcloud.com/letter_avatar/ajv/32/6_22734026db12803ebb3e059622ac3534.png) [@AJV](https://help.nextcloud.com/u/AJV)\ **Post date:** [April 30, 2024, 12:51pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/4 "2024-04-30T12:51:19Z")
Update the problem goes away by downgrading PHP to: PHP 8.2.15 (fpm-fcgi) Also don’t get the PHP warning anymore: PHP Deprecated: Optional parameter $userId declared before required parameter $path is implicitly treated as a required parameter in …/nextcloud/apps/deck/lib/Service/ConfigService.php on line 234 Hope this helps! ---
**Author:** ![jdsklajD](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jdsklajd/32/54943_2.png) [@jdsklajD](https://help.nextcloud.com/u/jdsklajD)\ **Post date:** [April 30, 2024, 11:38pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/5 "2024-04-30T23:38:30Z")
@AJV what specific command did you issue in terminal? Sudo? ---
**Author:** ![AJV](https://help.nextcloud.com/letter_avatar/ajv/32/6_22734026db12803ebb3e059622ac3534.png) [@AJV](https://help.nextcloud.com/u/AJV)\ **Post date:** [May 1, 2024, 5:23am UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/6 "2024-05-01T05:23:34Z")
Thanks for looking at this! Here you go, logged in as root command and warning: sudo -u wwwrun php occ setupchecks -vv PHP Deprecated: Optional parameter $userId declared before required parameter $path is implicitly treated as a required parameter in /srv/www/htdocs/nextcloud/apps/deck/lib/Service/ConfigService.php on line 234 ---
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [May 7, 2024, 7:38am UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/8 "2024-05-07T07:38:37Z")
both work with PHP: 8.2.18. Please create complete topic if you have further issues. ---
**Author:** ![besimux](https://help.nextcloud.com/user_avatar/help.nextcloud.com/besimux/32/47106_2.png) [@besimux](https://help.nextcloud.com/u/besimux)\ **Post date:** [May 11, 2024, 9:22pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/10 "2024-05-11T21:22:46Z")
Removing “fulltextsearch” resolves “cron not runnning” for me ---
**Author:** ![jtr](https://help.nextcloud.com/letter_avatar/jtr/32/6_22734026db12803ebb3e059622ac3534.png) [@jtr](https://help.nextcloud.com/u/jtr)\ **Post date:** [May 11, 2024, 9:33pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/11 "2024-05-11T21:33:14Z")
Notes v4.8.1 is very very old. It doesn’t even support v29. Something is strange about your environment since that version shouldn’t even be available to you. Your situation isn’t being caused by v29 itself. Can you please create a dedicated thread with your Server config details in it so that we can troubleshoot it outside of this thread? ---
**Author:** ![reset12](https://help.nextcloud.com/user_avatar/help.nextcloud.com/reset12/32/61657_2.png) [@reset12](https://help.nextcloud.com/u/reset12)\ **Post date:** [May 13, 2024, 6:00am UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/13 "2024-05-13T06:00:51Z")
I have many error after update to Nextcloud 29 like: sudo -u www-data php occ setupchecks -vv dav: ✓ DAV system address book: No outstanding DAV system address book sync. network: ✗ WebDAV endpoint: An exception occured while running the setup check: TypeError: OCA\DAV\SetupChecks\WebdavEndpoint::OCA\Settings\SetupChecks{closure}(): Argument #1 ($host) must be of type string, array given in /var/www/http/myweb/nextcloud/apps/settings/lib/SetupChecks/CheckServerResponseTrait.php:69 Stack trace: #0 [internal function]: OCA\DAV\SetupChecks\WebdavEndpoint-\>OCA\Settings\SetupChecks{closure}() #1 /var/www/http/myweb/nextcloud/apps/settings/lib/SetupChecks/CheckServerResponseTrait.php(69): array\_map() #2 /var/www/http/myweb/nextcloud/apps/settings/lib/SetupChecks/CheckServerResponseTrait.php(96): OCA\DAV\SetupChecks\WebdavEndpoint-\>getTestUrls() #3 /var/www/http/myweb/nextcloud/apps/dav/lib/SetupChecks/WebdavEndpoint.php(67): OCA\DAV\SetupChecks\WebdavEndpoint-\>runRequest() #4 /var/www/http/myweb/nextcloud/lib/private/SetupCheck/SetupCheckManager.php(51): OCA\DAV\SetupChecks\WebdavEndpoint-\>run() #5 /var/www/http/myweb/nextcloud/core/Command/SetupChecks.php(72): OC\SetupCheck\SetupCheckManager-\>runAll() #6 /var/www/http/myweb/nextcloud/3rdparty/symfony/console/Command/Command.php(298): OC\Core\Command\SetupChecks-\>execute() #7 /var/www/http/myweb/nextcloud/core/Command/Base.php(177): Symfony\Component\Console\Command\Command-\>run() My system run on : Betriebssystem: **Linux 6.5.0-28-generic x86\_64** Prozessor: **Intel(R) Core™ i5-7300U CPU @ 2.60GHz (4 cores)** Speicher: **7.62 GB** Server-Zeit: **Mon May 13 07:58:08 CEST 2024** Betriebszeit: **9 hours, 39 minutes, 1 seconds** |Distributor ID:|Ubuntu| |Description:|Ubuntu 23.10| |Release:|23.10| |Codename:|mantic| ---
**Author:** ![Snow](https://help.nextcloud.com/letter_avatar/snow/32/6_22734026db12803ebb3e059622ac3534.png) [@Snow](https://help.nextcloud.com/u/Snow)\ **Post date:** [May 20, 2024, 5:42pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/14 "2024-05-20T17:42:54Z")
Regarding the .htaccess file not working warning: The solution for me was to remove the ‘localhost’ entry from ‘trusted\_domains’ in `config.php`. Immediately the warning disappeared. ---
**Author:** ![joergschulz](https://help.nextcloud.com/user_avatar/help.nextcloud.com/joergschulz/32/55349_2.png) [@joergschulz](https://help.nextcloud.com/u/joergschulz)\ **Post date:** [May 21, 2024, 7:28pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/15 "2024-05-21T19:28:01Z")
there is a new version of fulltextsearch - cron should run now. ---
**Author:** ![besimux](https://help.nextcloud.com/user_avatar/help.nextcloud.com/besimux/32/47106_2.png) [@besimux](https://help.nextcloud.com/u/besimux)\ **Post date:** [May 21, 2024, 11:31pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/16 "2024-05-21T23:31:11Z")
It does thx ---
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [June 18, 2024, 7:59pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/17 "2024-06-18T19:59:39Z")
---
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [June 18, 2024, 7:59pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/18 "2024-06-18T19:59:53Z")
---
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [June 18, 2024, 8:00pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/19 "2024-06-18T20:00:54Z")
---
**Author:** ![drankinatty](https://help.nextcloud.com/letter_avatar/drankinatty/32/6_22734026db12803ebb3e059622ac3534.png) [@drankinatty](https://help.nextcloud.com/u/drankinatty)\ **Post date:** [July 5, 2024, 7:59pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/20 "2024-07-05T19:59:50Z")
> [@wwe](#): > > # well-known issue > > ```auto > 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. Note: this does NOT cover all similar issues. The finger well-known issue remains regardless of trailing slash or not. ---
**Author:** ![EternalHammer](https://help.nextcloud.com/letter_avatar/eternalhammer/32/6_22734026db12803ebb3e059622ac3534.png) [@EternalHammer](https://help.nextcloud.com/u/EternalHammer)\ **Post date:** [July 7, 2024, 4:21pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/21 "2024-07-07T16:21:45Z")
While digging around about this error I found this: `RewriteRule ^\.well-known/webfinger /public.php?service=webfinger [QSA,L]` Which you can find here: [server/tests/data/setUploadLimit/htaccess at master · nextcloud/server · GitHub](https://github.com/nextcloud/server/blob/master/tests/data/setUploadLimit/htaccess#L41) Sadly this also does not help with error. “Your web server is not properly set up to resolve `.well-known` URLs, failed on: `/.well-known/webfinger” ---
**Author:** ![mueller](https://help.nextcloud.com/letter_avatar/mueller/32/6_22734026db12803ebb3e059622ac3534.png) [@mueller](https://help.nextcloud.com/u/mueller)\ **Post date:** [July 16, 2024, 7:33am UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/22 "2024-07-16T07:33:02Z")
I am digging around in my configuration after update to NC 29.03. I also have the boring error about webfinger. None of all suggestions did help!?? What about the right settings for apache ? Wrote it to .htacces to my apache conf, nothing worked. Is this a bug? ---
**Author:** ![vantino](https://help.nextcloud.com/user_avatar/help.nextcloud.com/vantino/32/28809_2.png) [@vantino](https://help.nextcloud.com/u/vantino)\ **Post date:** [July 16, 2024, 12:22pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897/23 "2024-07-16T12:22:58Z")
metoo! Adding the suggested rewrite rule to apache2 config doesn’t work, because the local .htaccess overwrites it. I noticed, there are changes in apache2 version \> 2.4.5, it needs some flags to be set but that doesnt help either. Right now, I am a bit helpless on this error message in NC29. BUT: all the interfaces and web services are working, so it’s not an urgent issue. [Next page](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897.md?page=2)