-
After upgrading NextCloud from 4.23.4 to 5.4, almost all folders and data are gone, unfortunately:
Top level folders are still there and even show the date of last modification (correct at least for one folder modified yesterday),
but every top level folder shows empty (cf. screenshots). No subfolders, no documents in subfolders are there.The long non-update phase (since February 6) was due to trouble with docker (invalid blocks due to “toomanyrequests”, seemingly related to IPv6 subnet blocking in our Frankfurt data center …), we only realized that last Friday and figured out this morning how to circumvent this (by disabling IPv6 – but the issue with our NextCloud installation persists after reenabling IPv6).
I have to admit that I don't have an idea where to start looking for errors / misconfiguration or where to start inspecting the containers.
Any idea anyone?Sidenote:
We have also installed RocketChat, for which there was also half a dozen updates – everything went fine here, as it seems.Regards,
ChristianPS:
Logins to NC did not work, probably also the OIDC issue reported by others; we logged in via Cloudron.Screenshots:
Top level folder list, with correct modification dates:
Empty folder Team, no subfolders, there should be half a dozen as well as some documents, one newly created yesterday:
Empty folder, about a dozen subfolders missing:
-
After upgrading NextCloud from 4.23.4 to 5.4, almost all folders and data are gone, unfortunately:
Top level folders are still there and even show the date of last modification (correct at least for one folder modified yesterday),
but every top level folder shows empty (cf. screenshots). No subfolders, no documents in subfolders are there.The long non-update phase (since February 6) was due to trouble with docker (invalid blocks due to “toomanyrequests”, seemingly related to IPv6 subnet blocking in our Frankfurt data center …), we only realized that last Friday and figured out this morning how to circumvent this (by disabling IPv6 – but the issue with our NextCloud installation persists after reenabling IPv6).
I have to admit that I don't have an idea where to start looking for errors / misconfiguration or where to start inspecting the containers.
Any idea anyone?Sidenote:
We have also installed RocketChat, for which there was also half a dozen updates – everything went fine here, as it seems.Regards,
ChristianPS:
Logins to NC did not work, probably also the OIDC issue reported by others; we logged in via Cloudron.Screenshots:
Top level folder list, with correct modification dates:
Empty folder Team, no subfolders, there should be half a dozen as well as some documents, one newly created yesterday:
Empty folder, about a dozen subfolders missing:
@kqcav said in All non-binary documents vanished after upgrade to 5.4, only top level folders left:
After upgrading NextCloud from 4.23.4 to 5.4, almost all folders and data are gone, unfortunately:
What versions are these? NC is on version 31... Cloudron is on version 8.3.
edit: don't mind me, I guess you mean the nextcloud package version
-
J joseph moved this topic from Support
-
One question:
for every step, there was a backup created, so that I have seven of them.
Is it „safe“ in whatever sense to restore to one of these backups, maybe even step by step, or does this not affect data / storage?I wonder if this could lead to finding the „point of failure“.
-
One question:
for every step, there was a backup created, so that I have seven of them.
Is it „safe“ in whatever sense to restore to one of these backups, maybe even step by step, or does this not affect data / storage?I wonder if this could lead to finding the „point of failure“.
@kqcav said in All non-binary documents vanished after upgrade to 5.4, only top level folders left:
Is it „safe“ in whatever sense to restore to one of these backups, maybe even step by step, or does this not affect data / storage?
yes, it's safe . but I recommend using clone instead of restore (it will create a new instance of nextcloud and you can test if that works). of course, a clone will take that amount of additional space and your server should have that space.
-
@kqcav for a start, I would open the Web Terminal or the File manager of Nextcloud and see if the files are actually there in the /app/data directory.
-
@joseph By ›File manager‹, do you mean the normal view of „all files“ in the NextCloud browser interface, accessed via the left navigation bar (screenshot)?
This is actually the only way we are using NC, no other clients, no WebDav, nothing.
-
Ah, interesting.
And yes, the File Manager shows the directory structure with the uploaded files, including the new subfolder from yesterday with its two files.That's good, I suppose.
Started a clone of backup 1 of this morning's upgrades, maybe I'll find a working version.
Thank you very much for your immediate replies + directions, Joseph! I expected way slower support, and you're even helping!
-
-
So, I was indeed able to restore yesterday's NC in version 30.0.5 on app version 4.23.4 by cloning, and this shows all data + files and also allows login.
I was also able to localize the responsible NC plugin: turns out it was not an active plugin, but one disabled by the upgrade process: user_ldap
Identified this by comparing the plugin lists in 4.23.4/30.0.5 and 5.4.0/31.0.1.After re-enabling user_ldap, all documents und subfolders were visible in NextCloud 31.0.1, too.
I suppose there was good reason for disabling it.
But at least one step seems to be missing in the shift from ldap to oidc.Thanks again, Joseph, your support was very helpful!
/Chris -
I don't know, frankly speaking.
We only login via Browserform provided by NextCloud – before & after the upgrade. (cf. Screenshot)For years, I used to be under the impression, these user accounts are somehow stored in a NC database or something like that, but last autumn I realized that our cloudron accounts are used. So I guess this is done via ldap?
Confusing thing this morning was that loging in via the button ›Login with Cloudron‹ granted access, but without giving the files.
-
I don't know, frankly speaking.
We only login via Browserform provided by NextCloud – before & after the upgrade. (cf. Screenshot)For years, I used to be under the impression, these user accounts are somehow stored in a NC database or something like that, but last autumn I realized that our cloudron accounts are used. So I guess this is done via ldap?
Confusing thing this morning was that loging in via the button ›Login with Cloudron‹ granted access, but without giving the files.
@kqcav said in All non-binary documents vanished after upgrade to 5.4, only top level folders left:
For years, I used to be under the impression, these user accounts are somehow stored in a NC database or something like that, but last autumn I realized that our cloudron accounts are used. So I guess this is done via ldap?
yes, nextcloud is using ldap to authenticate as cloudron account. but oidc is also the same but using oidc protocol. The LDAP setup will go away at some point. So, it would be good to understand why this is not working
-
Provided some guidance, I could assist with some debugging, logfiles, configuration excerpts.
I have two copies of the NC installation still there, but switched off – I could mess around in them without any disturbance or costs.In the running NC instance, OIDC seems to be configured, all 9 environment variables are given and have reasonable values, which are mentioned in https://docs.cloudron.io/packaging/addons/#oidc
curling the endpoints works, response is valid JSON at first glance.Do I need to verify in the user accounts in the Cloudron master?
-
Initially I thought maybe the user mapping would be off. Basically LDAP users in your instance won't get matched correctly by Nextcloud with the equivalent OpenID user, however after rereading this thread, you indicate that folders to exist but just no files, yet those files are in the filestore? If you use other nextcloud plugins/apps in those instances, do they have the data?
-
Interestingly (and annoyingly) our current NextCloud-Instance was not working again this morning, meaning that login was only possible via the „login with cloudron“redirection and that subfolders & documents were missing. The reason: user_ldap was disabled again …
Obviously NC was automatically upgraded to release 31.0.2 last night, and user_ldap got disabled in the process.
I have disabled auto-updates for now.So I can confirm that this is the reason for our „document loss“.
And yes, it looks like the connection from OpenID-authenticated users to NC documents + folders gets lost somehow/somewhere.
But it's not the case that there are „extra user accounts“ in NextCloud. They are the same (same name, same, password, same 2fa) before & after activation of user_ldap.I don't know how permissions are implemented „under the hood“ in NC.
We grant r/w access based on a group („staff“), not on a user base.I noted one difference between „with / without user_ldap“:
the „owner“ of the folders is slightly different:
With user_ldap enabled, it's the full name „Christian A Vogl“, whereas when it's disabled, it's the short login name „cav“. Maybe a hint, that some data fetching from the Cloudron master did not succeed, and maybe the same data fetching action that should get the user's groups?PS:
We do not use other plugins or apps in NC. But I could test one or the other, if you think that might help finding the cause. -
Probably I have – whatever is visible in the NC admin interface is available.
Are you suggesting that I should disable user_ldap again and check?But isn't the question rather this:
Given the fact that the user-group mapping is available in NC as soon as I enable user_ldap, isn't this a hint on „no cause in NC, but rather in the Cloudron mothernship“ (this being the OpenID provider)?
No update, no restart, just enabling user_ldap and login – even „on the fly“.
