Nextcloud update pushed too early?

andreasb

Dear all
just to confirm: the update broke my installation, and the documented recovery procedures (https://docs.cloudron.io/packages/nextcloud/#fixing-a-broken-install) didn't work. The logs indeed showed issues with groupfolders. I restored backup and will be waiting for a second try

sponch

Just deleted group folders app an reinstalled it. Same error …

ntnsndr

Just adding that I'm having this same issue with the disappearing Group Folders (now called Team Folders). It is a bit of a disaster because our group folder is the most important data in the organization.

I notice that the apps "Teams" and "Team Folders" were both not enabled after the update. I was able to reactivate Teams. But enabling Team Folders produces this error in the UX:

An error occurred during the request. Unable to proceed.
json_decode(): Argument #1 ($json) must be of type string, null given

I'm grateful for how this community helps each other work through these issues together.

I'm working on backup/restore.

marcusquinn

I'm still seeing this message:

AppAPI deploy daemon
AppAPI default deploy daemon is not set. Please register a default deploy daemon in the settings to install External Apps (Ex-Apps).

The App Store seems to be missing a lot of apps, and the Collabora connection no longer works.

Not entirely sure how we ended up getting updates to v32.0.0, when I thought the Cloudron policy was to wait until 0.01 or 0.02 for whole version increment stability confirmation?

marcusquinn

Pretty new clean install, too.

Logs:

lucidfox

There seems to be a working patch for version 20.1.0 of group folders - https://github.com/nextcloud/groupfolders/issues/4037#issuecomment-3352521147

is this possible for us to implement on cloudron?

james

Hello @lucidfox
We have no control over the Nextcloud internal app store and thus can't add patches to apps from the Nextcloud App Store.

avatar1024

@marcusquinn said in Nextcloud update pushed too early?:

Not entirely sure how we ended up getting updates to v32.0.0, when I thought the Cloudron policy was to wait until 0.01 or 0.02 for whole version increment stability confirmation?

Probably just a mistake. But yes, @everyone, definitely be careful with this update. Even with the now functioning app store, I have some instance which have been able to update all apps and are now working fine on NC32, while others don't see any app updates and most apps are broken, and when trying to do play around with it, it broke Nextcloud completely.

jdaviescoates

I seem to be lucky (presumably as I'm not using affected apps) as my Nextclouds have updated but don't seem to have any issues.

But agreed this update shouldn't have been pushed as the Cloudron policy of waiting until the 0.01 is good and wise.

@Staff what happened? Can systems be put in place to ensure this doesn't happen again?

nebulon

yes that was an oversight on our end. Usually nextcloud update tests fail all the time until some adjustments are made, which raises attention. But this just slipped through. We will see how to special case nextcloud here in our update process to avoid this in the future

sponch

would be great if we could get some help. Restore is not possible because lots files have changed since Upgrade. Thanks everybody

marcusquinn

AppStore and Nextcloud/Collabora Office working again.

Didn't do anything, so I can only assume some required API calls working again.

Bit of an eye-opener that this self-hosted app can break in some ways from a 3rd-party API connection dependancy being unavailable.

andreasdueren

@marcusquinn said in Nextcloud update pushed too early?:

Bit of an eye-opener that this self-hosted app can break in some ways from a 3rd-party API connection dependancy being unavailable.

Yes I had the same thoughts. I did look a bit into it and you can apparently set a custom App Store address for example though.

lucidfox

just fyi, an update for team folders to 20.1.1 has been released and fixed the group folders issue for me.

necrevistonnezr

@marcusquinn said in Nextcloud update pushed too early?:

Bit of an eye-opener that this self-hosted app can break in some ways from a 3rd-party API connection dependancy being unavailable.

I have rambled about Nextcloud and its shortsighted design failure to allow core functionalities as „apps“ (e.g. search!!) more often than I can count. It’s stupid and makes Nextcloud unreliable at any new release.

sponch

@lucidfox said in Nextcloud update pushed too early?:

just fyi, an update for team folders to 20.1.1 has been released and fixed the group folders issue for me.

Yes. thx here too!!

avatar1024

The issue is resolved on most of my instances but on one of them (also updated to NC32), many apps are still running in their older version and the whole app store seems broken. Discover page displays “Nothing to show”, I see no update available and I cannot install any new apps.

If I disable an outdated app and try to re-enable it, it throws an error and then the whole instance breaks (cannot starts any longer). Weirdly though, several of the outdated apps are active and running fine (e.g. calendar).

I have tried to disable all outdated apps, restarted the instance but still the app store seems broken and does not update anything.

See my list of app below (and see how calendar, groupfolders etc. are out of date):

Enabled:
  - activity: 5.0.0-dev.0
  - admin_audit: 1.22.0
  - app_api: 32.0.0
  - bruteforcesettings: 5.0.0-dev.0
  - circles: 32.0.0
  - cloud_federation_api: 1.16.0
  - comments: 1.22.0
  - contactsinteraction: 1.13.1
  - dav: 1.34.2
  - federatedfilesharing: 1.22.0
  - federation: 1.22.0
  - files: 2.4.0
  - files_downloadlimit: 5.0.0-dev.0
  - files_external: 1.24.0
  - files_pdfviewer: 5.0.0-dev.0
  - files_reminders: 1.5.0
  - files_sharing: 1.24.0
  - files_trashbin: 1.22.0
  - files_versions: 1.25.0
  - firstrunwizard: 5.0.0-dev.0
  - logreader: 5.0.0-dev.0
  - lookup_server_connector: 1.20.0
  - nextcloud_announcements: 4.0.0-dev.0
  - notifications: 5.0.0-dev.0
  - oauth2: 1.20.0
  - password_policy: 4.0.0-dev.0
  - privacy: 4.0.0-dev.0
  - profile: 1.1.0
  - provisioning_api: 1.22.0
  - recommendations: 5.0.0-dev.0
  - related_resources: 3.0.0-dev.0
  - serverinfo: 4.0.0-dev.0
  - settings: 1.15.1
  - support: 4.0.0-dev.0
  - survey_client: 4.0.0-dev.0
  - systemtags: 1.22.0
  - text: 6.0.0-dev.0
  - theming: 2.7.0
  - twofactor_backupcodes: 1.21.0
  - updatenotification: 1.22.0
  - user_oidc: 7.4.0
  - user_status: 1.12.0
  - viewer: 5.0.0-dev.0
  - weather_status: 1.12.0
  - webhook_listeners: 1.3.0
  - workflowengine: 2.14.0
Disabled:
  - accessibility: 1.10.0
  - appointments: 2.4.6 (installed 2.4.6)
  - calendar: 5.5.3 (installed 5.5.3)
  - carnet: 0.25.6 (installed 0.25.6)
  - collectives: 3.1.2 (installed 3.1.2)
  - contacts: 7.3.0 (installed 7.3.0)
  - cookbook: 0.11.3 (installed 0.11.3)
  - dashboard: 7.12.0 (installed 7.1.0)
  - deck: 1.15.2 (installed 1.15.2)
  - drawio: 3.1.0 (installed 3.1.0)
  - encryption: 2.20.0 (installed 2.8.1)
  - end_to_end_encryption: 1.17.0 (installed 1.17.0)
  - event_update_notification: 2.6.1 (installed 2.6.1)
  - files_rightclick: 1.6.0 (installed 1.6.0)
  - files_videoplayer: 1.13.0
  - fileslibreofficeedit: 2.0.1 (installed 2.0.1)
  - forms: 5.1.2 (installed 5.1.2)
  - groupfolders: 19.1.3 (installed 19.1.3)
  - integration_whiteboard: 0.0.14 (installed 0.0.14)
  - mail: 5.4.0 (installed 5.4.0)
  - notes: 4.12.3 (installed 4.12.3)
  - notify_push: 1.2.0 (installed 1.2.0)
  - passwords: 2025.7.20 (installed 2025.7.20)
  - photos: 5.0.0-dev.1 (installed 5.0.0-dev.1)
  - polls: 8.4.6 (installed 8.4.6)
  - previewgenerator: 5.10.0 (installed 5.10.0)
  - quicknotes: 0.8.30 (installed 0.8.30)
  - richdocuments: 8.7.4 (installed 8.7.4)
  - richdocumentscode: 25.4.403 (installed 25.4.403)
  - sharebymail: 1.22.0 (installed 1.22.0)
  - suspicious_login: 10.0.0-dev.0 (installed 10.0.0-dev.0)
  - twofactor_nextcloud_notification: 6.0.0-dev.0
  - twofactor_totp: 14.0.0
  - user_ldap: 1.23.0 (installed 1.21.0)

Any help would be greatly appreciated at this stage. I’m ran out of ideas.

firmansi

So far I have no issues as mentioned above with latest update, my stack running with onlyoffice, nextcloud assistant, team folder, draw.io, groupware. My NC running with more than 100 users with Cloudron

avatar1024

I do see this show up several times in the log when that nextcloud instance starts:

Healtheck error: Error: connect ECONNREFUSED 172.18.18.24:80

nebulon

@avatar1024 that is to be expected. This is the Cloudron platform trying to reach the app to check if it is already up and running. When you see this, it just means the app isn't responding just yet.

Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.

Cloudron Forum

Nextcloud update pushed too early?