# 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:** 1

<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:** [September 28, 2023, 1:50pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/1 "2023-09-28T13:50:37Z")

</div>

The RC1 release of 27.1.2 is now available on our download server.

As always, help with testing is very much welcome!

We updated our servers, did our tests, and the release seem pretty decent. Still, give it a whirl and report back here so we’re even more sure that it’s good to go! If you notice anything out of order, please report back on the appropriate github repository! 🙇‍♀️

### Downloads

- [https://download.nextcloud.com/server/prereleases/nextcloud-27.1.2rc1.zip](https://download.nextcloud.com/server/prereleases/nextcloud-27.1.2rc1.zip)

## Changelog

- [Chore: Update `@nextcloud/dialogs` to 4.2.1 (server#40557)](https://github.com/nextcloud/server/pull/40557)
- [Let `occ trashbin:restore` restore also from groupfolders and add filters (server#40581)](https://github.com/nextcloud/server/pull/40581)
- [Ocm services (server#40586)](https://github.com/nextcloud/server/pull/40586)
- [Revert change that made `OC.Util.humanFileSize` return decimal sizes instead of binary (server#40605)](https://github.com/nextcloud/server/pull/40605)
- [Store size in int|float for 32bit support (server#40623)](https://github.com/nextcloud/server/pull/40623)
- [Fix(dav): expand recurrences when searching (server#40631)](https://github.com/nextcloud/server/pull/40631)
- [Fix jsunit tests (server#40638)](https://github.com/nextcloud/server/pull/40638)
- [Use proper app id in Version.vue (server#40640)](https://github.com/nextcloud/server/pull/40640)
- [Fix: encode uri for trashbin delete (server#40642)](https://github.com/nextcloud/server/pull/40642)
- [Fix(db): also chunk MariaDB deletes (activity#1312)](https://github.com/nextcloud/activity/pull/1312)
- [Re-enabled cypress tests (activity#1336)](https://github.com/nextcloud/activity/pull/1336)
- [Return if user is empty (firstrunwizard#953)](https://github.com/nextcloud/firstrunwizard/pull/953)
- [Chore(deps): Bump howler from 2.2.3 to 2.2.4 (notifications#1672)](https://github.com/nextcloud/notifications/pull/1672)
- [Bump cypress to v13 (photos#2057)](https://github.com/nextcloud/photos/pull/2057)
- [Fix(security): Bump semver (suspicious\_login#815)](https://github.com/nextcloud/suspicious_login/pull/815)
- [Fix(deps): update nextcloud abandoned (text#4756)](https://github.com/nextcloud/text/pull/4756)
- [Bugfix/duplicated load of yjs (text#4807)](https://github.com/nextcloud/text/pull/4807)
- [Feat: hide workspace if no readme.md (text#4811)](https://github.com/nextcloud/text/pull/4811)

---

<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:** [September 28, 2023, 2:31pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/2 "2023-09-28T14:31:02Z")

</div>

The update went flawless in the web updater of my beta installation. However, now I get this warning in the admin page:

`Dein Webserver ist nicht ordnungsgemäß für die Auflösung von "/ocm-provider/" eingerichtet...`

There is no ocm-provider in my installation, only ocs-provider. I use the apache webserver, what must be done?

---

<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:** [September 28, 2023, 4:01pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/3 "2023-09-28T16:01:42Z")

</div>

I copied the ocm-provider folder from another 27.1.1 installation into my 27.1.2 RC1 installation, and the warning is gone.

---

<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:** [September 28, 2023, 6:45pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/4 "2023-09-28T18:45:59Z")

</div>

The folder should not be there since [https://github.com/nextcloud/server/pull/40586](https://github.com/nextcloud/server/pull/40586) as this endpoint is now handled by a proper Controller in the regular business logic. We do not see this warning on our upgraded instances so far. Could you double check your web server config? I am also checking back with the developer.

---

<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:** [September 28, 2023, 7:38pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/5 "2023-09-28T19:38:42Z")

</div>

In my web server config I have no reference to that directory. The warning also did not show up before 27.1.2 RC1. However, the ocm-provider directory was present in my other stable installation, and copying it over to my beta installation solved the issue for me.

---

<div class="post-metadata">

**Author:** ![nickvergessen](https://help.nextcloud.com/user_avatar/help.nextcloud.com/nickvergessen/32/66965_2.png) [@nickvergessen](https://help.nextcloud.com/u/nickvergessen)\
**Post date:** [September 29, 2023, 6:44am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/6 "2023-09-29T06:44:59Z")

</div>

> [@eehmke](#):
>
> However, the ocm-provider directory was present in my other stable installation, and copying it over to my beta installation solved the issue for me.

The directory must not exist anymore in 27.1.2 RC1

Can you delete it again and instead try removing `ocm-provider|` from this line:

> <https://github.com/nextcloud/server/blob/f174e4a0575284fd6eb14ec2365962213093441f/lib/private/Setup.php#L540>

So the final line looks like:

```auto
$content .= "\n RewriteCond %{REQUEST_FILENAME} !/(ocs-provider|updater)/";

```

Afterwards run `sudo -u www php occ maintenance:update:htaccess`

And retry?

---

<div class="post-metadata">

**Author:** ![Uturn](https://help.nextcloud.com/letter_avatar/uturn/32/5_5575768a8748004e209b776fc1b2916d.png) [@Uturn](https://help.nextcloud.com/u/Uturn)\
**Post date:** [September 29, 2023, 8:53am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/7 "2023-09-29T08:53:23Z")

</div>

my setup (hosted at owncube) stalls with a

_ **Step 3 is currently in process. Please reload this page later.** _

message. How to get rid of that?

---

<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:** [September 29, 2023, 12:16pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/8 "2023-09-29T12:16:35Z")

</div>

This is strange. I did the change in Setup.php, deleted the ocm-provider directory and reloaded the page. The error was gone.

Then i detected your last line and did the  
`sudo -u www php occ maintenance:update:htaccess`

step, which was successful. **But now the error is present again!**

---

<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 2, 2023, 8:24pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/9 "2023-10-02T20:24:27Z")

</div>

Indeed. The setup change has only effect on the .htaccess recreation with the occ call. But did you actually state you are running Apache?

Do you see differences when you access the settings page with clean urls or without (without = having index.php in the URL)?

Also, is this instance placed in a subfolder (for instance `https://example.com/nextcloud/`)?

---

<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 2, 2023, 8:37pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/10 "2023-10-02T20:37:23Z")

</div>

I have index.php in the URL. I can’t tell any differences as I can’t access the settings page otherwise.

No the instance is not in a subfolder. I have a subdomain like [testcloud.tld.de](http://testcloud.tld.de)

---

<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 4, 2023, 10:16am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/11 "2023-10-04T10:16:18Z")

</div>

Thanks for the info! So do you use Apache, Nginx, or some other webserver?

---

<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 4, 2023, 10:17am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/12 "2023-10-04T10:17:24Z")

</div>

I use Apache, with a virtual host for the cloud service.

---

<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 4, 2023, 10:17am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/13 "2023-10-04T10:17:56Z")

</div>

> [@eehmke](#):
>
> Apache, with a virtual host for the cloud

Ok, good. And do you have the rewrite module enabled?

---

<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 4, 2023, 10:28am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/14 "2023-10-04T10:28:40Z")

</div>

Yes, but there are no rewrites in the cloud vhost.

---

<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 4, 2023, 10:42am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/15 "2023-10-04T10:42:44Z")

</div>

Alright. Could you add the highlighted line to your `.htaccess` (same location) and retry?

> <https://github.com/nextcloud/server/blob/a250250985e6517c1c3a1cc7cd28008948353cb3/.htaccess#L93>

---

<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 4, 2023, 10:48am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/16 "2023-10-04T10:48:04Z")

</div>

Great, that fixed it! Thank you for your patience.

I reloaded the apache server, if that matters.

---

<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 4, 2023, 10:50am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/17 "2023-10-04T10:50:44Z")

</div>

> [@eehmke](#):
>
> `sudo -u www php occ maintenance:update:htaccess`

Thank you for pointing it out all the help around it ❤

---

<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 4, 2023, 11:06am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/18 "2023-10-04T11:06:08Z")

</div>

May I ask you for one more favor? Could you provide us your whole .htaccess file in its current state?

---

<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 4, 2023, 11:15am UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/19 "2023-10-04T11:15:44Z")

</div>

Sure.

```auto
<IfModule mod_headers.c>
  <IfModule mod_setenvif.c>
    <IfModule mod_fcgid.c>
       SetEnvIfNoCase ^Authorization$ "(.+)" XAUTHORIZATION=$1
       RequestHeader set XAuthorization %{XAUTHORIZATION}e env=XAUTHORIZATION
    </IfModule>
    <IfModule mod_proxy_fcgi.c>
       SetEnvIfNoCase Authorization "(.+)" HTTP_AUTHORIZATION=$1
    </IfModule>
    <IfModule mod_lsapi.c>
      SetEnvIfNoCase ^Authorization$ "(.+)" XAUTHORIZATION=$1
      RequestHeader set XAuthorization %{XAUTHORIZATION}e env=XAUTHORIZATION
    </IfModule>
  </IfModule>

  <IfModule mod_env.c>
    # Add security and privacy related headers

    # Avoid doubled headers by unsetting headers in "onsuccess" table,
    # then add headers to "always" table: https://github.com/nextcloud/server/pull/19002
    Header onsuccess unset Referrer-Policy
    Header always set Referrer-Policy "no-referrer"

    Header onsuccess unset X-Content-Type-Options
    Header always set X-Content-Type-Options "nosniff"

    Header onsuccess unset X-Frame-Options
    Header always set X-Frame-Options "SAMEORIGIN"

    Header onsuccess unset X-Permitted-Cross-Domain-Policies
    Header always set X-Permitted-Cross-Domain-Policies "none"

    Header onsuccess unset X-Robots-Tag
    Header always set X-Robots-Tag "noindex, nofollow"

    Header onsuccess unset X-XSS-Protection
    Header always set X-XSS-Protection "1; mode=block"

    SetEnv modHeadersAvailable true
  </IfModule>
  # Add cache control for static resources
  <FilesMatch "\.(css|js|mjs|svg|gif|png|jpg|ico|wasm|tflite)$">
    <If "%{QUERY_STRING} =~ /(^|&)v=/">
      Header set Cache-Control "max-age=15778463, immutable"
    </If>
    <Else>
      Header set Cache-Control "max-age=15778463"
    </Else>
  </FilesMatch>

  # Let browsers cache WOFF files for a week
  <FilesMatch "\.woff2?$">
    Header set Cache-Control "max-age=604800"
  </FilesMatch>
</IfModule>

<IfModule mod_php.c>
  php_value mbstring.func_overload 0
  php_value default_charset 'UTF-8'
  php_value output_buffering 0
  <IfModule mod_env.c>
    SetEnv htaccessWorking true
  </IfModule>
</IfModule>

<IfModule mod_mime.c>
  AddType image/svg+xml svg svgz
  AddType application/wasm wasm
  AddEncoding gzip svgz
  # Serve ESM javascript files (.mjs) with correct mime type
  AddType text/javascript js mjs
</IfModule>

<IfModule mod_dir.c>
  DirectoryIndex index.php index.html
</IfModule>

<IfModule pagespeed_module>
  ModPagespeed Off
</IfModule>

<IfModule mod_rewrite.c>
  RewriteEngine on
  RewriteCond %{HTTP_USER_AGENT} DavClnt
  RewriteRule ^$ /remote.php/webdav/ [L,R=302]
  RewriteRule .* - [env=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
  RewriteRule ^\.well-known/carddav /remote.php/dav/ [R=301,L]
  RewriteRule ^\.well-known/caldav /remote.php/dav/ [R=301,L]
  RewriteRule ^remote/(.*) remote.php [QSA,L]
  RewriteRule ^(?:build|tests|config|lib|3rdparty|templates)/.* - [R=404,L]
  RewriteRule ^\.well-known/(?!acme-challenge|pki-validation) /index.php [QSA,L]
  RewriteRule ^ocm-provider/?$ /index.php [QSA,L]
  RewriteRule ^(?:\.(?!well-known)|autotest|occ|issue|indie|db_|console).* - [R=404,L]
</IfModule>

AddDefaultCharset utf-8
Options -Indexes
#### DO NOT CHANGE ANYTHING ABOVE THIS LINE ####

ErrorDocument 403 /index.php/error/403
ErrorDocument 404 /index.php/error/404

```

---

<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 5, 2023, 9:05pm UTC](https://help.nextcloud.com/t/first-rc-of-nextcloud-27-1-2/171104/20 "2023-10-05T21:05:48Z")

</div>

Alright, now I installed 27.1.2 final and the problem did not show up again.

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