# First RC of Nextcloud 27.1.2

**URL:** <https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104>\
**Category:** 🎁 Releases\
**Tags:** beta, nc271, nc27\
**Created:** [September 28, 2023, 1:50pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104 "2023-09-28T13:50:37Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![ericfaure007](https://help.nextcloud.com/user_avatar/help.nextcloud.com/ericfaure007/32/55033_2.png) [@ericfaure007](https://help.nextcloud.com/u/ericfaure007)\
**Post date:** [October 6, 2023, 7:13am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/21 "2023-10-06T07:13:07Z")

</div>

I upgraded to the final 27.1.2 version yesterday and this problem is showing up.  
I also have an apache web server, but the difference is that nextcloud is in a subdir: www.domainname/nextcloud.  
I can confirm that the Rewrite rule in .htaccess file of nextcloud folder is existing:  
RewriteRule ^ocm-provider/?$ /index.php [QSA,L]

---

<div class="post-metadata">

**Author:** ![blizzz](https://help.nextcloud.com/user_avatar/help.nextcloud.com/blizzz/32/133_2.png) [@blizzz](https://help.nextcloud.com/u/blizzz)\
**Post date:** [October 6, 2023, 7:29am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/22 "2023-10-06T07:29:26Z")

</div>

> [@ericfaure007](#):
>
> nfirm that the Rewrite rule in .htaccess file of nextcloud folder is existing:  
> RewriteRule ^ocm-provider/?$ /ind

Did you run `occ maintenance:update:htaccess` after the upgrade?

---

<div class="post-metadata">

**Author:** ![ericfaure007](https://help.nextcloud.com/user_avatar/help.nextcloud.com/ericfaure007/32/55033_2.png) [@ericfaure007](https://help.nextcloud.com/u/ericfaure007)\
**Post date:** [October 6, 2023, 7:49am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/23 "2023-10-06T07:49:01Z")

</div>

Yes, I did.

---

<div class="post-metadata">

**Author:** ![CBiker](https://help.nextcloud.com/letter_avatar/cbiker/32/5_5575768a8748004e209b776fc1b2916d.png) [@CBiker](https://help.nextcloud.com/u/CBiker)\
**Post date:** [October 6, 2023, 8:51am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/24 "2023-10-06T08:51:17Z")

</div>

> [@ericfaure007](#):
>
> RewriteRule ^ocm-provider/?$ /index.php [QSA,L]

I also have my nextcloud in a subfolder.  
The ocm-provider folder does not exist for me.  
I edited the .htaccess and the line:  
RewriteRule ^ocm-provider/?$ /index.php [QSA,L] changed to  
RewriteRule ^\.ocm-provider/?$ /index.php [QSA,L].  
The error disappeared immediately.  
Is this the right approach?

---

<div class="post-metadata">

**Author:** ![ericfaure007](https://help.nextcloud.com/user_avatar/help.nextcloud.com/ericfaure007/32/55033_2.png) [@ericfaure007](https://help.nextcloud.com/u/ericfaure007)\
**Post date:** [October 6, 2023, 9:18am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/25 "2023-10-06T09:18:01Z")

</div>

The problem is still present on my side even with this change.

---

<div class="post-metadata">

**Author:** ![JoMatr](https://help.nextcloud.com/letter_avatar/jomatr/32/5_5575768a8748004e209b776fc1b2916d.png) [@JoMatr](https://help.nextcloud.com/u/JoMatr)\
**Post date:** [October 6, 2023, 9:49am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/26 "2023-10-06T09:49:33Z")

</div>

www.domainname/nextcloud/ocm-provider/

File not found.

www.domainname/nextcloud/index.php/ocm-provider/

Shows some json file

Apache Webserver with Nextcloud in subfolder.

---

<div class="post-metadata">

**Author:** ![Cult](https://help.nextcloud.com/user_avatar/help.nextcloud.com/cult/32/8547_2.png) [@Cult](https://help.nextcloud.com/u/Cult)\
**Post date:** [October 6, 2023, 10:13am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/27 "2023-10-06T10:13:56Z")

</div>

> [@CBiker](#):
>
> RewriteRule ^ocm-provider/?$ /index.php [QSA,L]

Is your .htaccess at the top root of your domain ?  
If so, try this one:

> ```
> RewriteRule ^ocm-provider/?$ /nextcloud/index.php [QSA,L]
> 
> ```

replace `/nextcloud/index.php` with the sub folder path of your setup

---

<div class="post-metadata">

**Author:** ![JoMatr](https://help.nextcloud.com/letter_avatar/jomatr/32/5_5575768a8748004e209b776fc1b2916d.png) [@JoMatr](https://help.nextcloud.com/u/JoMatr)\
**Post date:** [October 6, 2023, 10:25am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/28 "2023-10-06T10:25:56Z")

</div>

Yes, that was the solution. The warning message no longer exists. Thank you very much.

---

<div class="post-metadata">

**Author:** ![ericfaure007](https://help.nextcloud.com/user_avatar/help.nextcloud.com/ericfaure007/32/55033_2.png) [@ericfaure007](https://help.nextcloud.com/u/ericfaure007)\
**Post date:** [October 6, 2023, 11:43am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/29 "2023-10-06T11:43:54Z")

</div>

It’s strange, it’s still not working for me with .htaccess at the root of the domain…  
I don’t know how it should behave exactly?

---

<div class="post-metadata">

**Author:** ![Katzenklo](https://help.nextcloud.com/user_avatar/help.nextcloud.com/katzenklo/32/55047_2.png) [@Katzenklo](https://help.nextcloud.com/u/Katzenklo)\
**Post date:** [October 6, 2023, 12:18pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/30 "2023-10-06T12:18:59Z")

</div>

here the same problem without solution

---

<div class="post-metadata">

**Author:** ![Cult](https://help.nextcloud.com/user_avatar/help.nextcloud.com/cult/32/8547_2.png) [@Cult](https://help.nextcloud.com/u/Cult)\
**Post date:** [October 6, 2023, 1:00pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/31 "2023-10-06T13:00:23Z")

</div>

do you have rewrite enable ? do you allow Rewrite Rules in .htaccess ? is the .htaccess loaded/accepted by apache ? can you past the line you have in .htaccess related to ocm-provider ?

is there still a folder ‘ocm-provider’ in your nextcloud setup ?

---

<div class="post-metadata">

**Author:** ![ericfaure007](https://help.nextcloud.com/user_avatar/help.nextcloud.com/ericfaure007/32/55033_2.png) [@ericfaure007](https://help.nextcloud.com/u/ericfaure007)\
**Post date:** [October 6, 2023, 1:11pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/32 "2023-10-06T13:11:26Z")

</div>

Here is the .htaccess on the root:

```auto
<IfModule mod_rewrite.c>
RewriteEngine on
  RewriteRule ^\.well-known/carddav /nextcloud/remote.php/dav [R=301,L]
  RewriteRule ^\.well-known/caldav /nextcloud/remote.php/dav [R=301,L]
  RewriteRule ^\.well-known/webfinger /nextcloud/index.php/.well-known/webfinger [R=301,L]
  RewriteRule ^\.well-known/nodeinfo /nextcloud/index.php/.well-known/nodeinfo [R=301,L]
  RewriteRule ^ocm-provider/?$ /nextcloud/index.php [QSA,L]
</IfModule>

```

The other rules are working, because if I remove them I get some warnings from nextcloud.  
The ocm-provider folder is no longer existing.

---

<div class="post-metadata">

**Author:** ![Cult](https://help.nextcloud.com/user_avatar/help.nextcloud.com/cult/32/8547_2.png) [@Cult](https://help.nextcloud.com/u/Cult)\
**Post date:** [October 6, 2023, 1:14pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/33 "2023-10-06T13:14:25Z")

</div>

can you send me ([maxence@nextcloud.com](mailto:maxence@nextcloud.com)) the address of your nextcloud so I can run a curl request myself ?

---

<div class="post-metadata">

**Author:** ![CBiker](https://help.nextcloud.com/letter_avatar/cbiker/32/5_5575768a8748004e209b776fc1b2916d.png) [@CBiker](https://help.nextcloud.com/u/CBiker)\
**Post date:** [October 6, 2023, 2:29pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/34 "2023-10-06T14:29:32Z")

</div>

My .htaccess is not at the top root of my domain.  
Yes, your solution works too.  
Both types:  
RewriteRule ^\.ocm-provider/?$ /index.php [QSA,L] as well  
RewriteRule ^ocm-provider/?$ /nextcloudfolder/index.php [QSA,L].  
But the question is which variant makes more sense or what effect  
the first variant with “\.” at the beginning?  
Thank you

---

<div class="post-metadata">

**Author:** ![jschneider](https://help.nextcloud.com/letter_avatar/jschneider/32/5_5575768a8748004e209b776fc1b2916d.png) [@jschneider](https://help.nextcloud.com/u/jschneider)\
**Post date:** [October 6, 2023, 3:44pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/35 "2023-10-06T15:44:56Z")

</div>

Same problem here. nextCloud is installed in a subfolder, ocm-provider rewrite rule is in site config. If I comment ocm-provider line in subfolder .htaccess, the warning disappears, but then of course core integrity check fails for .htaccess. Any suggestions?

---

<div class="post-metadata">

**Author:** ![KittyMeow](https://help.nextcloud.com/letter_avatar/kittymeow/32/5_5575768a8748004e209b776fc1b2916d.png) [@KittyMeow](https://help.nextcloud.com/u/KittyMeow)\
**Post date:** [October 6, 2023, 5:13pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/36 "2023-10-06T17:13:09Z")

</div>

I have the same problem. Nextcloud is installed in a subdirectory. The rewrite rules mentioned in this thread did not solve the problem.

---

<div class="post-metadata">

**Author:** ![ratatoskr](https://help.nextcloud.com/letter_avatar/ratatoskr/32/5_5575768a8748004e209b776fc1b2916d.png) [@ratatoskr](https://help.nextcloud.com/u/ratatoskr)\
**Post date:** [October 6, 2023, 5:28pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/37 "2023-10-06T17:28:44Z")

</div>

> [@CBiker](#):
>
> I also have my nextcloud in a subfolder.  
> The ocm-provider folder does not exist for me.  
> I edited the .htaccess and the line:  
> RewriteRule ^ocm-provider/?$ /index.php [QSA,L] changed to  
> RewriteRule ^.ocm-provider/?$ /index.php [QSA,L].  
> The error disappeared immediately.  
> Is this the right approach?

Same problem, same fix. The problem disappeared immediately. But I am a noob and I don’t know what this does. Is it a “stable solution”, doesn’t it break something in the future?  
Thanks everybody! 🙂

---

<div class="post-metadata">

**Author:** ![Malta-Support](https://help.nextcloud.com/user_avatar/help.nextcloud.com/malta-support/32/2530_2.png) [@Malta-Support](https://help.nextcloud.com/u/Malta-Support)\
**Post date:** [October 6, 2023, 6:37pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/38 "2023-10-06T18:37:34Z")

</div>

Same here - for me it doesnt solve the problem too

---

<div class="post-metadata">

**Author:** ![KittyMeow](https://help.nextcloud.com/letter_avatar/kittymeow/32/5_5575768a8748004e209b776fc1b2916d.png) [@KittyMeow](https://help.nextcloud.com/u/KittyMeow)\
**Post date:** [October 6, 2023, 6:48pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/39 "2023-10-06T18:48:56Z")

</div>

So I got rid of the warning by modifying .htaccess and changing the line to

```auto
RewriteRule ^.ocm-provider/?$ /index.php [QSA,L]

```

Initially I tried putting this in my Apache config for my Nextcloud setup but for some reason any rewrite rules I put in there seem to have no affect.

---

<div class="post-metadata">

**Author:** ![eehmke](https://help.nextcloud.com/user_avatar/help.nextcloud.com/eehmke/32/8934_2.png) [@eehmke](https://help.nextcloud.com/u/eehmke)\
**Post date:** [October 6, 2023, 6:59pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/40 "2023-10-06T18:59:16Z")

</div>

This may work for you when you have nextcloud in a subdirectory. I use nextcloud in a subdomain like [cloud.mydomain.de](http://cloud.mydomain.de) and when I put your change into my .htaccess the warning pops up again. It was gone with the former solution.

[Previous page](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104.md?page=1)

[Next page](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104.md?page=3)