# Your web server is not properly set up to resolve "/ocm-provider/". following upgrade to 27.1.2

**URL:** <https://help.nextcloud.com/t/your-web-server-is-not-properly-set-up-to-resolve-ocm-provider-following-upgrade-to-27-1-2/171678>\
**Category:** ℹ️ Support\
**Tags:** update\_problems, nc27, apache\
**Created:** [October 6, 2023, 4:58pm UTC](https://help.nextcloud.com/t/your-web-server-is-not-properly-set-up-to-resolve-ocm-provider-following-upgrade-to-27-1-2/171678 "2023-10-06T16:58:45Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![egglestn](https://help.nextcloud.com/letter_avatar/egglestn/32/5_5575768a8748004e209b776fc1b2916d.png) [@egglestn](https://help.nextcloud.com/u/egglestn)\
**Post date:** [October 8, 2023, 10:49am UTC](https://help.nextcloud.com/t/your-web-server-is-not-properly-set-up-to-resolve-ocm-provider-following-upgrade-to-27-1-2/171678/13 "2023-10-08T10:49:48Z")

</div>

> [@With Nextcloud update: "Not properly set up to resolve “/ocm-provider/” and “/ocs-provider/” on NGINX server](https://help.nextcloud.com/t/with-nextcloud-update-not-properly-set-up-to-resolve-ocm-provider-and-ocs-provider-on-nginx-server/158528/18):
>
> There is much chit-chat about this stuff in various nextcloud github issues related to upgrading to the latest 27.1.2 version. There seems to be a problem. I’m running an apache server with nextcloud in a sub-directory. The fix in this comment solved the problem for me: TL;DR - in the .htacces file found in your nextcloud root, drop the front slash of the index.php part of this line: RewriteRule ^ocm-provider/?$ index.php [QSA,L] I suspect you could also ignore the warning and it will be f…

Works for me!

---

_[View the full topic](https://help.nextcloud.com/t/your-web-server-is-not-properly-set-up-to-resolve-ocm-provider-following-upgrade-to-27-1-2/171678)._