# Web updater issues (plural!) **URL:** \ **Category:** ℹ️ Support\ **Tags:** update\_problems, github\_issue\_exists, nc27\ **Created:** [October 6, 2023, 7:40am UTC](https://help.nextcloud.com/t/web-updater-issues-plural/171610 "2023-10-06T07:40:06Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![dev-b2a](https://help.nextcloud.com/letter_avatar/dev-b2a/32/6_22734026db12803ebb3e059622ac3534.png) [@dev-b2a](https://help.nextcloud.com/u/dev-b2a)\ **Post date:** [October 6, 2023, 7:40am UTC](https://help.nextcloud.com/t/web-updater-issues-plural/171610/1 "2023-10-06T07:40:06Z")
Just updated a Nextcloud Server (Apache) installation from v27.1.1 to v27.1.2 via web updater. The first thing I noticed was that four files were classified as ‘extra’, although they are part of the original installation package: `package-lock.json`, `package.json`, `composer.lock` and `composer.json`. Also, the entire `dist` directory has been categorized as ‘extra’ for some time now, but is included in the installation package as well. What _really_ gave me a headache today was the warning message after the update: > “Your web server is not properly set up to resolve “/ocm-provider/”. This is most likely related to a web server configuration that was not updated to deliver this folder directly. (…)” However, it turned out that this was not a configuration error at all, but that the `ocm-provider` directory is no longer included in the v27.1.2 installation package (it was still in v27.1.1 though)! Looks like the check routines of both the web updater and the post-update check in the ‘Security & setup warnings’ section of the administration overview could use a revision. For the time being, I have manually restored the `ocm-provider` directory from the v27.1.1 package because I couldn’t find any other solution in a hurry. But: can this lead to problems? Thanks for any reply. RJ ---
**Author:** ![egglestn](https://help.nextcloud.com/letter_avatar/egglestn/32/6_22734026db12803ebb3e059622ac3534.png) [@egglestn](https://help.nextcloud.com/u/egglestn)\ **Post date:** [October 6, 2023, 3:28pm UTC](https://help.nextcloud.com/t/web-updater-issues-plural/171610/2 "2023-10-06T15:28:17Z")
I also have this problem, but have left it be…If someone can explain to me how to restore the missing directory, I’d be grateful ---
**Author:** ![mahdi.7839](https://help.nextcloud.com/letter_avatar/mahdi.7839/32/6_22734026db12803ebb3e059622ac3534.png) [@mahdi.7839](https://help.nextcloud.com/u/mahdi.7839)\ **Post date:** [October 6, 2023, 10:20pm UTC](https://help.nextcloud.com/t/web-updater-issues-plural/171610/3 "2023-10-06T22:20:15Z")
I have the same problem, can you explain the restore process? tanks ---
**Author:** ![egglestn](https://help.nextcloud.com/letter_avatar/egglestn/32/6_22734026db12803ebb3e059622ac3534.png) [@egglestn](https://help.nextcloud.com/u/egglestn)\ **Post date:** [October 7, 2023, 11:28am UTC](https://help.nextcloud.com/t/web-updater-issues-plural/171610/4 "2023-10-07T11:28:09Z")
I found it by wandering around the forums I am using ubuntu linux Download and extract the file 27.1.1 to a home directory. Drop into a shell sudo mv /home/extracted file/ocm-provider/ var/www/html/nextcloud/ocm-provider/ HTH But PLEASE check first before you do anything that might break your system ---
**Author:** ![egglestn](https://help.nextcloud.com/letter_avatar/egglestn/32/6_22734026db12803ebb3e059622ac3534.png) [@egglestn](https://help.nextcloud.com/u/egglestn)\ **Post date:** [October 7, 2023, 11:29am UTC](https://help.nextcloud.com/t/web-updater-issues-plural/171610/5 "2023-10-07T11:29:22Z")
I have done the same, and restarted apache2…didnt make a blind bit of difference…Did you solve the problem? ---
**Author:** ![dev-b2a](https://help.nextcloud.com/letter_avatar/dev-b2a/32/6_22734026db12803ebb3e059622ac3534.png) [@dev-b2a](https://help.nextcloud.com/u/dev-b2a)\ **Post date:** [October 9, 2023, 6:50am UTC](https://help.nextcloud.com/t/web-updater-issues-plural/171610/6 "2023-10-09T06:50:56Z")
@egglestn, @mahdi.7839 I manually created the directory `ocm-provider` and the single file `index.php` in it as user ‘www-data’, opened the latter in the editor, then simply copied and pasted the few lines of PHP code from the `index.php` of v27.1.1 and saved the file. After restarting Apache the warning message was gone. @egglestn Could the problem on your side be that the `ocm-provider` directory and the included `index.php` have the wrong ownership (namely ‘root’)? The real question, however, is why the warning message appears in Nextcloud at all when the directory in question is no longer provided in the official download package. Is this now an error in the delivery or rather in the test routine? ---
**Author:** ![egglestn](https://help.nextcloud.com/letter_avatar/egglestn/32/6_22734026db12803ebb3e059622ac3534.png) [@egglestn](https://help.nextcloud.com/u/egglestn)\ **Post date:** [October 9, 2023, 8:12am UTC](https://help.nextcloud.com/t/web-updater-issues-plural/171610/7 "2023-10-09T08:12:51Z")
I tried that , and sadly, it didn’t work. I downloaded a full version of 27.1.1 and copied the relevant files over However by tweaking the .htaccess file as suggested here > > > \### ⚠️ This issue respects the following points: ⚠️ > > \- \[X\] This is a \*\*bug\*\*, no…t a question or a configuration/webserver/proxy issue. > \- \[X\] This issue is \*\*not\*\* already reported on \[Github\](https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3Abug) OR \[Nextcloud Community Forum\](https://help.nextcloud.com/) \_(I've searched it)\_. > \- \[X\] Nextcloud Server \*\*is\*\* up to date. See \[Maintenance and Release Schedule\](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) for supported versions. > \- \[X\] I agree to follow Nextcloud's \[Code of Conduct\](https://nextcloud.com/contribute/code-of-conduct/). > > \### Bug description > > When updating to 27.1.2 the server says that the ocm-provider paths are incorrect. > I checked the .htaccess shipped with 27.1.2, but the config in there is incorrect. > Deleting the config path from there is leading to a working ocm-provider path (checked in the browser). I do have 2 redirects in the apache-conf: > > Redirect 301 /ocm-provider /nextcloud/ocm-provider > Redirect 301 /ocs-provider /nextcloud/ocs-provider > > Nevertheless, the nextcloud admin page is still telling me that the ocm-provider path is setup incorrect, why? > The ocs-provider is fully fine. There was no error in the .htaccess and my redirect worked out of the box. > > > \### Steps to reproduce > > 1. Upgrade from 27.1.1 to 27.1.2 > 2. Open Admin Page > 3. > > > \### Expected behavior > > That it is working like on 27.1.1 without any errors > > \### Installation method > > Community Manual installation with Archive > > \### Nextcloud Server version > > 27 > > \### Operating system > > Debian/Ubuntu > > \### PHP engine version > > PHP 8.2 > > \### Web server > > Apache (supported) > > \### Database engine version > > MariaDB > > \### Is this bug present after an update or on a fresh install? > > Updated from a MINOR version (ex. 22.1 to 22.2) > > \### Are you using the Nextcloud Server Encryption module? > > None > > \### What user-backends are you using? > > \- \[X\] Default user-backend \_(database)\_ > \- \[\] LDAP/ Active Directory > \- \[\] SSO - SAML > \- \[\] Other > > \### Configuration report > > \`\`\`shell > not needed for this issue > \`\`\` > > > \### List of activated Apps > > \`\`\`shell > not needed for this issue > \`\`\` > > > \### Nextcloud Signing status > > \`\`\`shell > all works fine > \`\`\` > > > \### Nextcloud Logs > > \`\`\`shell > No relevant erros in the log > \`\`\` > > > \### Additional info > > \_No response\_ the problem went away… I don’t have the expertise to say why one worked when the other didn’t, and certainly permissions have been the source of 80% of all problems in Nextcloud… In any case, alls well that ends well… thanks for the help ---
**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:** [December 14, 2024, 2:16pm UTC](https://help.nextcloud.com/t/web-updater-issues-plural/171610/8 "2024-12-14T14:16:21Z")