# Problems after upgrading to version 29 **URL:** \ **Category:** ℹ️ Support\ **Tags:** update\_problems, nc29\ **Created:** [May 27, 2024, 4:02am UTC](https://help.nextcloud.com/t/problems-after-upgrading-to-version-29/193304 "2024-05-27T04:02:40Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![procoprobocop](https://help.nextcloud.com/user_avatar/help.nextcloud.com/procoprobocop/32/53580_2.png) [@procoprobocop](https://help.nextcloud.com/u/procoprobocop)\ **Post date:** [May 27, 2024, 4:02am UTC](https://help.nextcloud.com/t/problems-after-upgrading-to-version-29/193304/1 "2024-05-27T04:02:41Z")
After upgrading to Next CloudHub version 8 (29.0.1), I get an error: > The data directory and files may be accessible from the Internet. The “.htaccess” file does not work. It is strongly recommended to configure the web server so that the data directory is not accessible from the external network, or to move the data directory outside the root directory of the web server My data is here: `/var/www/nextcloud-data` When transferring them to the /var/nextcloud-data directory and updating the path in the file config.php I’m getting an error: > The data directory is set incorrectly. Make sure that there is a file in the root of the data directory. “ocdata”. The data catalog is not writable. Although I have assigned recording rights: `chown www-data:www-data -R /var/nextcloud-data` ---
**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 27, 2024, 6:25am UTC](https://help.nextcloud.com/t/problems-after-upgrading-to-version-29/193304/2 "2024-05-27T06:25:36Z")
please use [search](https://help.nextcloud.com/%20https://help.nextcloud.com/search) - this issue was discussed often already - likely you find a solution e.g. > [@Data directory accessible from the internet](https://help.nextcloud.com/t/data-directory-accessible-from-the-internet/14507): > > Seems lots of chatter about this on github etc but no real solution? Admin page has warning: “Your data directory and your files are probably accessible from the internet. The .htaccess file that ownCloud provides is not working. We strongly suggest that you configure your webserver in a way that the data directory is no longer accessible or you move the data directory outside the webserver document root…” Any update on this? > [@\[FIXED\] Htaccess file is not working](https://help.nextcloud.com/t/fixed-htaccess-file-is-not-working/4225): > > Hello, Fresh install of NC 10 latest on Debian 8.6 following the install manual and getting this error that I have never seen before. Did anyone fix this in the past. “Your data directory and your files are probably accessible from the Internet. The .htaccess file is not working. We strongly suggest that you configure your web server in a way that the data directory is no longer accessible or you move the data directory outside the web server document root.” I tried to create a text file in th… [Frequent Nextcloud 29 (Hub 8) update issues](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897) ---
**Author:** ![procoprobocop](https://help.nextcloud.com/user_avatar/help.nextcloud.com/procoprobocop/32/53580_2.png) [@procoprobocop](https://help.nextcloud.com/u/procoprobocop)\ **Post date:** [May 27, 2024, 6:29am UTC](https://help.nextcloud.com/t/problems-after-upgrading-to-version-29/193304/3 "2024-05-27T06:29:57Z")
I have read these recommendations, but they are about configuring based on the Apache web server. I use the Nginx web server, and these recommendations do not suit me. ---
**Author:** ![jtr](https://help.nextcloud.com/letter_avatar/jtr/32/5_5575768a8748004e209b776fc1b2916d.png) [@jtr](https://help.nextcloud.com/u/jtr)\ **Post date:** [May 27, 2024, 12:46pm UTC](https://help.nextcloud.com/t/problems-after-upgrading-to-version-29/193304/4 "2024-05-27T12:46:56Z")
> [@procoprobocop](#): > > After upgrading to Next CloudHub version 8 (29.0.1), I get an error: v29 runs these tests from the server-side rather than the client. If you weren’t getting this warning before, there’s a high probability the underlying cause is related to a somewhat different config matter in your environment that wasn’t visible before. Specifically: The check runs tests against each of your configured `trusted_domains` and your `overwrite.cli.url`. It’s important that each of these domains: - is valid - are resolvable in DNS _on_ your server (or from _inside_ your container, if using Docker) - go to the same place on your server as they do externally ---
**Author:** ![chrissi55](https://help.nextcloud.com/user_avatar/help.nextcloud.com/chrissi55/32/4286_2.png) [@chrissi55](https://help.nextcloud.com/u/chrissi55)\ **Post date:** [May 27, 2024, 2:16pm UTC](https://help.nextcloud.com/t/problems-after-upgrading-to-version-29/193304/5 "2024-05-27T14:16:45Z")
> [@procoprobocop](#): > > When transferring them to the /var/nextcloud-data directory and updating the path in the file config.php I’m getting an error One hint is the ownership (you said you have changed the rights to www-user) OK but the second hint in data dir needs to be a file called “.ocdata” - is that fullfilled as well? It is a dot in the file name =\> hidden file (do you copy that over to the new directory as well? It is a 0 byte file ---
**Author:** ![procoprobocop](https://help.nextcloud.com/user_avatar/help.nextcloud.com/procoprobocop/32/53580_2.png) [@procoprobocop](https://help.nextcloud.com/u/procoprobocop)\ **Post date:** [June 1, 2024, 6:29pm UTC](https://help.nextcloud.com/t/problems-after-upgrading-to-version-29/193304/6 "2024-06-01T18:29:36Z")
In trusted\_domains, I left only the DNS name, deleting the local ip, but it didn’t help ---
**Author:** ![procoprobocop](https://help.nextcloud.com/user_avatar/help.nextcloud.com/procoprobocop/32/53580_2.png) [@procoprobocop](https://help.nextcloud.com/u/procoprobocop)\ **Post date:** [June 1, 2024, 6:31pm UTC](https://help.nextcloud.com/t/problems-after-upgrading-to-version-29/193304/7 "2024-06-01T18:31:15Z")
File .ocdata is present, I copied it from the old directory ---
**Author:** ![procoprobocop](https://help.nextcloud.com/user_avatar/help.nextcloud.com/procoprobocop/32/53580_2.png) [@procoprobocop](https://help.nextcloud.com/u/procoprobocop)\ **Post date:** [June 1, 2024, 6:32pm UTC](https://help.nextcloud.com/t/problems-after-upgrading-to-version-29/193304/8 "2024-06-01T18:32:49Z")
I’m coming to the conclusion that this is a bug of the 29th version. It was not fixed in 29.0.1 either. Moreover, in a clean installation, it does not play, and when updating an existing instance of NextCloud, it plays. Comparing configs did not add understanding. ---
**Author:** ![jtr](https://help.nextcloud.com/letter_avatar/jtr/32/5_5575768a8748004e209b776fc1b2916d.png) [@jtr](https://help.nextcloud.com/u/jtr)\ **Post date:** [June 1, 2024, 9:42pm UTC](https://help.nextcloud.com/t/problems-after-upgrading-to-version-29/193304/9 "2024-06-01T21:42:42Z")
> [@jtr](#): > > The check runs tests against each of your configured `trusted_domains` and your `overwrite.cli.url`. It’s important that each of these domains: As I said, your original warning was likely due to a change in the setup checks in v28+. You did not fill out the original support template so it’s challenging to provide further help. If you’re using containers, confirm DNS resolution for your trusted\_domains in the container are the same as when outside the container. That’s \>50% of the cause across the environments I’ve seen. What install method did you use? ---
**Author:** ![procoprobocop](https://help.nextcloud.com/user_avatar/help.nextcloud.com/procoprobocop/32/53580_2.png) [@procoprobocop](https://help.nextcloud.com/u/procoprobocop)\ **Post date:** [June 3, 2024, 3:31am UTC](https://help.nextcloud.com/t/problems-after-upgrading-to-version-29/193304/10 "2024-06-03T03:31:28Z")
I used a NON-container installation method. In trusted\_domains, I only have the DNS name of my cloud and nothing else. ---
**Author:** ![procoprobocop](https://help.nextcloud.com/user_avatar/help.nextcloud.com/procoprobocop/32/53580_2.png) [@procoprobocop](https://help.nextcloud.com/u/procoprobocop)\ **Post date:** [June 3, 2024, 4:08am UTC](https://help.nextcloud.com/t/problems-after-upgrading-to-version-29/193304/11 "2024-06-03T04:08:12Z")
I solved this problem by using wildcard characters in **config.php**. Example: ```auto 'trusted domains' => array ( 0 => '*.domain.com ', ), ``` ---
**Author:** ![fyah](https://help.nextcloud.com/letter_avatar/fyah/32/5_5575768a8748004e209b776fc1b2916d.png) [@fyah](https://help.nextcloud.com/u/fyah)\ **Post date:** [June 3, 2024, 12:28pm UTC](https://help.nextcloud.com/t/problems-after-upgrading-to-version-29/193304/12 "2024-06-03T12:28:25Z")
Hello, it worked for me as well, but I would like to understand why !! ---
**Author:** ![procoprobocop](https://help.nextcloud.com/user_avatar/help.nextcloud.com/procoprobocop/32/53580_2.png) [@procoprobocop](https://help.nextcloud.com/u/procoprobocop)\ **Post date:** [June 4, 2024, 9:23am UTC](https://help.nextcloud.com/t/problems-after-upgrading-to-version-29/193304/13 "2024-06-04T09:23:16Z")
to understand, you need to know how server-side validation is performed ---
**Author:** ![system](https://help.nextcloud.com/user_avatar/help.nextcloud.com/system/32/29333_2.png) [@system](https://help.nextcloud.com/u/system)\ **Post date:** [June 12, 2024, 9:23am UTC](https://help.nextcloud.com/t/problems-after-upgrading-to-version-29/193304/14 "2024-06-12T09:23:47Z")
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.