Nextcloud 21 is out
-
@girish @nebulon For users who are using Nextcloud + Nextcloud Talk for remote, collaborative work, the two Nextcloud HPB's (the Spreed SFU/ signalling HPB + this new notifications HPB binary) are very important.
My largest (non-Cloudron) Nextcloud has 22 remote users; the Spreed SFU (available as-a-service for 40 euro per month) enables them to hold their all-hands Monday video meetings. They love the new notifications binary too because it makes the Nextcloud Talk notifications "instantaneous"... especially, when receiving a call, etc. They are now doing many group audio calls.
With these two HPB's enabled, Nextcloud is arguably the best, open source, self-hostable, remote-work collaboration tool available today. Without them....well, it great for managing files....like Owncloud, Pydio, etc.
If Cloudron devs intend their Nextcloud installation to be used for collaborative, remote work, then the notifications HPB binary needs to be enabled by default. It requires a decent amount of of server-side jugglery.
-
@oj I think @doodlemania2 is making good progress with the High Performance Back-end for Talk.
I can see you've already upvoted that here:
https://forum.cloudron.io/post/8642And I've just added an App Wishlist post for the High Performance Back-end for Nextcloud Files too:
https://forum.cloudron.io/post/29236 -
@nebulon you've probably spotted this already, but I just noticed 21.0.1 is now out - so I think that means time to update the Cloudron package, right? (I really want to try out the new whiteboard
) -
@jdaviescoates right, I've just updated the v20 app package and will then start testing v21 tomorrow.
-
-
@nebulon said in Nextcloud 21 is out:
We have released the 21 package now and will be rolling it out slowly over the next week.
Installed and now problems so far. Will you update to the "high-performance-backend" in the future as described here: https://github.com/nextcloud/notify_push?
-
@nebulon said in Nextcloud 21 is out:
We have released the 21 package now and will be rolling it out slowly over the next week.
Just updated to the new version, when you go to settings > administration > overview, you see several configuration “warnings”:
Security & setup warnings
It's important for the security and performance of your instance that everything is configured correctly. To help you with that we are doing some automatic checks. Please see the linked documentation for more information.There are some warnings regarding your setup.
Your web server is not properly set up to resolve "/.well-known/webfinger". Further information can be found in the documentation.
Your web server is not properly set up to resolve "/.well-known/nodeinfo". Further information can be found in the documentation. -
@nebulon said in Nextcloud 21 is out:
We have released the 21 package now and will be rolling it out slowly over the next week.
Logs still not working, could this be a package bug?
-
@imc67 said in Nextcloud 21 is out:
@nebulon said in Nextcloud 21 is out:
We have released the 21 package now and will be rolling it out slowly over the next week.
Just updated to the new version, when you go to settings > administration > overview, you see several configuration “warnings”:
Security & setup warnings
It's important for the security and performance of your instance that everything is configured correctly. To help you with that we are doing some automatic checks. Please see the linked documentation for more information.There are some warnings regarding your setup.
Your web server is not properly set up to resolve "/.well-known/webfinger". Further information can be found in the documentation.
Your web server is not properly set up to resolve "/.well-known/nodeinfo". Further information can be found in the documentation.@nebulon did you find time to check the new app version for this warning? Also logs still don't work.
-
Apparently the htaccess file now has a few new rewrite rules:
RewriteRule ^\.well-known/host-meta /public.php?service=host-meta [QSA,L] RewriteRule ^\.well-known/host-meta\.json /public.php?service=host-meta-json [QSA,L] RewriteRule ^\.well-known/webfinger /public.php?service=webfinger [QSA,L] RewriteRule ^\.well-known/nodeinfo /public.php?service=nodeinfo [QSA,L]however they are all in the section where nextcloud itself says one should not modify them. Not sure how they have thought this to be handled for updates.
-
Some of the instances are hitting "Undefined class constant ‘MAJOR_VERSION’ after upgrade to 21" . This is a bug in the nextcloud plugin/app and you have to disable that plugin following the instructions at https://docs.cloudron.io/apps/nextcloud/#fixing-a-broken-install . It seems a lot of plugins are incompatible - https://github.com/nextcloud/vm/issues/1834#issuecomment-782832104 . If you use any of these plugins, either disable the plugin or disable automatic updates to nextcloud.
You might think
It turns out that occ tool itself stops working and you cannot disable plugins anymore with the CLI tool since it fails with the following error:root@5795ea67-b3c2-4604-9710-88d1997920bd:/app/code# sudo -u www-data php -f /app/code/occ app:list An unhandled exception has been thrown: Error: Undefined class constant 'MAJOR_VERSION' in /app/code/3rdparty/guzzlehttp/guzzle/src/Utils.php:118 Stack trace: #0 /app/code/3rdparty/guzzlehttp/guzzle/src/functions.php(71): GuzzleHttp\Utils::defaultUserAgent() #1 /app/data/apps/files_external_gdrive/vendor/guzzlehttp/guzzle/src/Client.php(194): GuzzleHttp\default_user_agent() #2 /app/data/apps/files_external_gdrive/vendor/guzzlehttp/guzzle/src/Client.php(75): GuzzleHttp\Client->configureDefaults()It seems the fix is to put nextcloud in recovery mode and then
rm -rf /app/data/apps/<plugin>and then disable recovery mode. -
@girish
That‘s real stupid by NC
The occ command should be bulletproof. -
@necrevistonnezr right I was hoping for a --skip-plugins or equivalent but couldn't find one (the WP cli tool has something like that for skipping loading of themes and plugins).
