# RC5 of Nextcloud 28.0.2 **URL:** \ **Category:** 🎁 Releases\ **Tags:** beta, nc28\ **Created:** [January 29, 2024, 3:30pm UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292 "2024-01-29T15:30:09Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Altahrim](https://help.nextcloud.com/letter_avatar/altahrim/32/6_22734026db12803ebb3e059622ac3534.png) [@Altahrim](https://help.nextcloud.com/u/Altahrim)\ **Post date:** [January 29, 2024, 3:30pm UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/1 "2024-01-29T15:30:09Z")
The Maintenance release of 28.0.2 is coming next Thursday, and a fifth RC 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 candidates 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-28.0.2rc5.zip](https://download.nextcloud.com/server/prereleases/nextcloud-28.0.2rc5.zip) ## Changelog ### 28.0.2 RC5 - [Update `@nextcloud/dialogs` to 5.1.1 (server#43150)](https://github.com/nextcloud/server/pull/43150) - [Fix(files): disable `Unshare` until proper fix (server#43169)](https://github.com/nextcloud/server/pull/43169) - [Fix(mention): use new url schema (text#5304)](https://github.com/nextcloud/text/pull/5304) ---
**Author:** ![atanasov123](https://help.nextcloud.com/user_avatar/help.nextcloud.com/atanasov123/32/51403_2.png) [@atanasov123](https://help.nextcloud.com/u/atanasov123)\ **Post date:** [January 29, 2024, 7:24pm UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/2 "2024-01-29T19:24:41Z")
На пн, 29.01.2024 г., 18:41 Altahrim via Nextcloud community \<[noreply@nextcloud.com](mailto:noreply@nextcloud.com)\> написа: ---
**Author:** ![aforrer999](https://help.nextcloud.com/letter_avatar/aforrer999/32/6_22734026db12803ebb3e059622ac3534.png) [@aforrer999](https://help.nextcloud.com/u/aforrer999)\ **Post date:** [January 30, 2024, 10:14am UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/3 "2024-01-30T10:14:42Z")
Hi All Thank you for this latest version. I installed on a shared hosting and gained so far the experience as described below. Setup: Nextcloud located in a subfolder: ~public/nextcloud with one user Operating System: **Linux 4.9.0-0.bpo.12-amd64 x86\_64** CPU: **Intel(R) Xeon(R) CPU E5-2630L v4 @ 1.80GHz (20 cores)** Memory: **94.21 GB** Server time: **Tue Jan 30 10:04:04 CET 2024** No root access **Apache** : 2.4.51 **PHP:** Version: _8.1.26_ Memory limit: _1.3 GB_ Max execution time: _3600_ Upload max size: _800 MB_ OPcache Revalidate Frequency: Extensions: _Core, date, libxml, openssl, pcre, sqlite3, zlib, bcmath, bz2, calendar, ctype, curl, dom, hash, fileinfo, filter, ftp, gd, gettext, gmp, json, iconv, SPL, intl, session, ldap, mbstring, standard, pcntl, PDO, mysqlnd, pdo\_sqlite, pgsql, Phar, posix, readline, Reflection, imap, SimpleXML, soap, sockets, sodium, pdo\_mysql, exif, tidy, tokenizer, xml, xmlreader, xmlwriter, xsl, mysqli, cgi-fcgi, imagick, mailparse, mcrypt, memcached, mongodb, OAuth, raphf, ssh2, timezonedb, uploadprogress, yaz, zip, http_ **DB** Type: _mysql_ Version: _10.4.18_ Size: _6.4 MB_ **Nextcloud:** 28.0.2 RC5: …/index.php/apps/files/files and access to many other apps are fine However these two have an access-problem through index.php: …/index.php/apps/notes …/index.php/apps/dashboard where only the main menu-bar and a part of the navigation pane are visible. The main app-functionalities are not available A path without “index.php” like …/apps/notes works fine **Nextcloud:** 27,1,5,1: …/index.php/apps/files/files wasn’t working while …/apps/files did The same for: …/index.php/apps/dashboard/ …/index.php/apps/notes/ **Note that “files” in now working in this latest version.** I experimented with all tips I found in the forums around htaccess, unfortunately without success. Any tips where to conduct further investigations will be appreciated, as I do not know the code yet. Cheers, Andreas ---
**Author:** ![Ark74](https://help.nextcloud.com/user_avatar/help.nextcloud.com/ark74/32/2071_2.png) [@Ark74](https://help.nextcloud.com/u/Ark74)\ **Post date:** [January 30, 2024, 3:57pm UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/4 "2024-01-30T15:57:42Z")
There seems to be an issue with uploading (nginx/postgres) files using an Android 10.0 device using Google Chrome 120/121. It keeps hanging estimating the upload time, but never gets uploaded. Using the Nextcloud app works though, sadly it has some UI drawbacks against the online version. ---
**Author:** ![WechuTM](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wechutm/32/58236_2.png) [@WechuTM](https://help.nextcloud.com/u/WechuTM)\ **Post date:** [January 31, 2024, 7:41am UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/5 "2024-01-31T07:41:33Z")
Thank you for the new RC Unfortunately, the problem with changing the theme color in the administration panel with the “Disable user theming” function enabled is still present. [#43229](https://github.com/nextcloud/server/issues/43229) ---
**Author:** ![tim.s](https://help.nextcloud.com/user_avatar/help.nextcloud.com/tim.s/32/46546_2.png) [@tim.s](https://help.nextcloud.com/u/tim.s)\ **Post date:** [January 31, 2024, 11:41pm UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/6 "2024-01-31T23:41:30Z")
Thanks for the updates. The two main issues for every day work still present in RC5, from my point of view: - Calendar: “New subscription from link“ is still broken, the ics feed does not appear. Test it with e.g. [https://www.thunderbird.net/media/caldata/autogen/Germany-Holidays.ics](https://www.thunderbird.net/media/caldata/autogen/Germany-Holidays.ics) → there are several related issues on Github, mostly closed but still not working: [https://github.com/nextcloud/calendar/issues/5641](https://github.com/nextcloud/calendar/issues/5641) / [Subscription Calendar Events are not returned by REPORT dav request · Issue #42143 · nextcloud/server · GitHub](https://github.com/nextcloud/server/issues/42143) / [Subscription Calendar Events are not returned by REPORT dav request · Issue #42143 · nextcloud/server · GitHub](https://github.com/nextcloud/server/issues/42143) and others - Creating a share with expiration date does not work: it says the date was in the past, but it is actually in the future. (I have created an issue here: [[Bug]: NC 28.0.2 RC5 Trying to set expiration date for share – NC claims it's in the past · Issue #43243 · nextcloud/server · GitHub](https://github.com/nextcloud/server/issues/43243)) ---
**Author:** ![henningsieh](https://help.nextcloud.com/user_avatar/help.nextcloud.com/henningsieh/32/50472_2.png) [@henningsieh](https://help.nextcloud.com/u/henningsieh)\ **Post date:** [February 2, 2024, 11:20am UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/7 "2024-02-02T11:20:38Z")
> [@tim.s](#): > > Creating a share with expiration date does not work: it says the date was in the past, but it is actually in the future. I can confirm this bug, it is broken in 28.0.2 (latest/stable). Setting a future expiration date is NOT POSSIBLE. ---
**Author:** ![henningsieh](https://help.nextcloud.com/user_avatar/help.nextcloud.com/henningsieh/32/50472_2.png) [@henningsieh](https://help.nextcloud.com/u/henningsieh)\ **Post date:** [February 2, 2024, 12:52pm UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/8 "2024-02-02T12:52:23Z")
Fortsetzung der Diskussion von [RC4 of Nextcloud 28.0.2](https://help.nextcloud.com/t/rc4-of-nextcloud-28-0-2/179990/6): > [@RC4 of Nextcloud 28.0.2](https://help.nextcloud.com/t/rc4-of-nextcloud-28-0-2/179990/6): > > According to the description for RC3, the problem with the “Could not check for JavaScript support. Please check manually if your webserver serves `.mjs` files using the JavaScript MIME type.” message should disappear - unfortunately it does not disappear. It would be useful to have a parameter that would allow you to manually disable the message after the test (curl -I [https://your.nextcloud.tld/apps/settings/js/esm-test.mjs](https://your.nextcloud.tld/apps/settings/js/esm-test.mjs)) has been performed. > Should I create a new issue? [#43153](https://github.com/nextcloud/server/issues/43153) & [#42989](https://github.com/nextcloud/server/issues/42989) – Hey Nerds! 🤓 👋 I managed to get rid of all other error messages after updating to 28.0.2, but I do not understand how to resolve this one: ![grafik](https://help.nextcloud.com/uploads/default/original/3X/e/e/eee6e978ae29cd8625b7a4b809d56a1b44ea466c.png) I have also checked and read this according bug: [https://github.com/nextcloud/server/issues/42989](https://github.com/nextcloud/server/issues/42989) Output of my `curl` command is: ```auto ~# curl -I https://cloud.sieh.org/apps/settings/js/esm-test.mjs HTTP/1.1 200 OK Server: nginx Date: Fri, 02 Feb 2024 12:46:44 GMT Content-Type: text/javascript Content-Length: 109 Connection: keep-alive Vary: Accept-Encoding Referrer-Policy: no-referrer X-Content-Type-Options: nosniff X-Frame-Options: SAMEORIGIN X-Permitted-Cross-Domain-Policies: none X-Robots-Tag: noindex, nofollow X-XSS-Protection: 1; mode=block Last-Modified: Fri, 02 Feb 2024 08:37:21 GMT ETag: "6d-6106205424576" Accept-Ranges: bytes Vary: Accept-Encoding Cache-Control: max-age=15778463 Strict-Transport-Security: max-age=31536000; includeSubDomains ``` I don’t know, how to fix this. And - to be honest - I also don’t know, what the error message is trying to tell me! 🤔 ---
**Author:** ![devnull](https://help.nextcloud.com/user_avatar/help.nextcloud.com/devnull/32/27793_2.png) [@devnull](https://help.nextcloud.com/u/devnull)\ **Post date:** [February 2, 2024, 1:00pm UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/9 "2024-02-02T13:00:49Z")
> [@henningsieh](#): > > `Content-Type: text/javascript` Maybe you can change it in nginx to: > I fixed the issue by adding the .mjs extension to nginx.conf like this: | | types { | | --- | --- | | | application/javascript mjs; | | | } | [part of your link above](https://github.com/nextcloud/server/issues/42989#issuecomment-1922203648) ---
**Author:** ![koelle25](https://help.nextcloud.com/user_avatar/help.nextcloud.com/koelle25/32/6466_2.png) [@koelle25](https://help.nextcloud.com/u/koelle25)\ **Post date:** [February 2, 2024, 1:07pm UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/10 "2024-02-02T13:07:04Z")
If you are using NGINX as webserver see this example config from the nextcloud/docker repo: > ---
**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/6_22734026db12803ebb3e059622ac3534.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\ **Post date:** [February 2, 2024, 2:51pm UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/11 "2024-02-02T14:51:02Z")
Compare with the recommended nginx.conf in the documentation and report if there are still problems: [https://docs.nextcloud.com/server/stable/admin\_manual/installation/nginx.html](https://docs.nextcloud.com/server/stable/admin_manual/installation/nginx.html) And there are still outstanding PR for this issue: > > > \### Thanks for helping improve our documentation! > > \* There is always room for… improvement! > \* All contributions (changes and change ideas) - from the largest \*\*to the tiniest\*\* - help make Nextcloud better and easier to use! > > \--- > > > > Nextcloud 27 added support for \`mjs\` and with Nextcloud 28, some core components started to make use of it. This was a breaking change for webserver setups without Apache2 or when not making use of \`.htaccess\`, since requests to those files were rewritten to \`index.php\`. It would be beneficial to add a hint for admins to the upgrade guide of the docs: https://docs.nextcloud.com/server/latest/developer\_manual/app\_publishing\_maintenance/app\_upgrade\_guide/upgrade\_to\_28.html > > > > \--- > > \#### Notes > > \* Please be patient: this is a large open source project that is overseen by a mixture of volunteers and non-volunteers which are all ultimately busy. > \* If your suggestion is a troubleshooting scenario or one you're not 100% certain about, please post for feedback on the \[Nextcloud Help Forum\](https://help.nextcloud.com) first. > - \*Then\* return here to bring back your experience to help improve the documentation for clarity, etc. (and link back to the forum discussion in your report!) > > \#### Protip: If you want to help move things along (or just help out in other ways too) here are some suggestions: > \* Look for areas where you can assist - even seemingly unrelated areas - \*because doing so frees up resources for your favorite topics and ideas\*. > \* Submit a proposed change - that attempts to addresses your issue - as a pull request. > \* Participate in a discussion on some other unresolved \[submitted idea ("issues")\](https://github.com/nextcloud/documentation/issues) to help move it along. > \* Post a comment or review on someone else's \[proposed change ("pull request")\](https://github.com/nextcloud/documentation/pulls) to help move it along. to put more information in the upgrade documentation. ---
**Author:** ![politas](https://help.nextcloud.com/user_avatar/help.nextcloud.com/politas/32/33448_2.png) [@politas](https://help.nextcloud.com/u/politas)\ **Post date:** [February 2, 2024, 9:17pm UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/12 "2024-02-02T21:17:55Z")
I’m getting this same message, but I am using Apache webserver with an nginx upstream proxy. ```auto $ curl -I https://my.nextcloud.tld/apps/settings/js/esm-test.mjs HTTP/2 200 server: nginx/1.18.0 (Ubuntu) date: Fri, 02 Feb 2024 21:01:02 GMT content-type: text/javascript content-length: 109 referrer-policy: no-referrer x-content-type-options: nosniff x-frame-options: SAMEORIGIN x-permitted-cross-domain-policies: none x-robots-tag: noindex, nofollow x-xss-protection: 1; mode=block last-modified: Fri, 02 Feb 2024 20:45:10 GMT etag: "6d-6106c3028ad27" accept-ranges: bytes vary: Accept-Encoding cache-control: max-age=15778463 strict-transport-security: max-age=15552000; includeSubDomains ``` The configs given for fixing this are all for when using nginx on the nextcloud host, which I am not (It’s in a docker container). It’s not even obvious from this output whether the test is successful! I wasn’t getting this message on 28.0.1. ---
**Author:** ![jtr](https://help.nextcloud.com/letter_avatar/jtr/32/6_22734026db12803ebb3e059622ac3534.png) [@jtr](https://help.nextcloud.com/u/jtr)\ **Post date:** [February 2, 2024, 9:44pm UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/13 "2024-02-02T21:44:01Z")
@politas & @henningsieh - At least one of you mentioned Docker. The check runs from _in_ the container (or if not Docker, from the app/mod\_php/fpm-php server) itself. Are you running curl from there or somewhere else? ---
**Author:** ![politas](https://help.nextcloud.com/user_avatar/help.nextcloud.com/politas/32/33448_2.png) [@politas](https://help.nextcloud.com/u/politas)\ **Post date:** [February 2, 2024, 10:03pm UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/14 "2024-02-02T22:03:16Z")
I ran my curl outside the container. Would the check not also use the proxy address? ---
**Author:** ![jtr](https://help.nextcloud.com/letter_avatar/jtr/32/6_22734026db12803ebb3e059622ac3534.png) [@jtr](https://help.nextcloud.com/u/jtr)\ **Post date:** [February 2, 2024, 10:09pm UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/15 "2024-02-02T22:09:44Z")
It will try all the hostnames defined in `trusted_domains` trying to find one that works. ---
**Author:** ![politas](https://help.nextcloud.com/user_avatar/help.nextcloud.com/politas/32/33448_2.png) [@politas](https://help.nextcloud.com/u/politas)\ **Post date:** [February 2, 2024, 10:23pm UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/16 "2024-02-02T22:23:46Z")
Trying the curl command from inside the docker container, I get this: `curl: (7) Failed to connect to my.nextcloud.tld port 443 after 199 ms: Couldn't connect to server` pinging the hostname shows that it is resolving to the container’s internal network ip address, rather than the external DNS address ```auto "Networks": { "nextcloud_internal_network": { "IPAMConfig": null, "Links": null, "Aliases": [ "nextcloud-app", "app", "---------", "my.nextcloud.tld" ], "MacAddress": "----------------", "NetworkID": "------------------", "EndpointID": "------------------", "Gateway": "172.18.0.1", "IPAddress": "172.18.0.4", "IPPrefixLen": 16, "IPv6Gateway": "", "GlobalIPv6Address": "", "GlobalIPv6PrefixLen": 0, "DriverOpts": null, "DNSNames": [ "nextcloud-app", "app", "--------------", "my.nextcloud.tld" ] }, ``` ---
**Author:** ![politas](https://help.nextcloud.com/user_avatar/help.nextcloud.com/politas/32/33448_2.png) [@politas](https://help.nextcloud.com/u/politas)\ **Post date:** [February 2, 2024, 10:31pm UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/17 "2024-02-02T22:31:08Z")
My container is based off the [nextcloud Docker Official Image](https://hub.docker.com/_/nextcloud/) (Apache version), which I realise is no longer the supported docker method from Nextcloud, but I shudder at the thought of having to convert from my working setup to experimenting with an all-in-one that has very poor documentation. Also, it has a bunch of "can it do this? No, and it never will."s that rule it out for migrating. ---
**Author:** ![jtr](https://help.nextcloud.com/letter_avatar/jtr/32/6_22734026db12803ebb3e059622ac3534.png) [@jtr](https://help.nextcloud.com/u/jtr)\ **Post date:** [February 2, 2024, 10:54pm UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/18 "2024-02-02T22:54:13Z")
> [@politas](#): > > My container is based off the [nextcloud > Docker Official Image](https://hub.docker.com/_/nextcloud/) (Apache version), which I realise is no longer the supported docker method from Nextcloud Nothing has changed with that image. I use it. It’s the community Docker micro-services image. It’s widely used. They have different applications. Unless you’re _paying_ Nextcloud GmbH for support it’s also somewhat irrelevant. It sounds like you’ve got your URL hostname in an /etc/hosts file or defined as a static in your Compose file or something. EDIT: A forum admin should move this all to its own thread 🙂 ---
**Author:** ![politas](https://help.nextcloud.com/user_avatar/help.nextcloud.com/politas/32/33448_2.png) [@politas](https://help.nextcloud.com/u/politas)\ **Post date:** [February 3, 2024, 2:52am UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/19 "2024-02-03T02:52:27Z")
> [@jtr](#): > > EDIT: A forum admin should move this all to its own thread 🙂 Agreed. I did have the hostname in my docker-compose file, which I presume I did while wrestling with the migration into the container. Taking that out means the curl is now what I presume is a successful response. Hopefully nothing else will break as a result! ---
**Author:** ![rakekniven](https://help.nextcloud.com/user_avatar/help.nextcloud.com/rakekniven/32/67096_2.png) [@rakekniven](https://help.nextcloud.com/u/rakekniven)\ **Post date:** [February 3, 2024, 7:00am UTC](https://help.nextcloud.com/t/rc5-of-nextcloud-28-0-2/180292/20 "2024-02-03T07:00:31Z")
This topic was automatically closed after 4 days. New replies are no longer allowed.