I broke my compose installation trying to update from 6.2 to 7.1. I can't get it to work anymore. How can I fix it?

[ensapra]

It's a local installation running on a small laptop for personal use. It's not connected to the global internet and I just use tailscale to access it. So there's no special setup. Only one user and it's admin

I tried updating from 6.2 to 7.1 and I somehow broke everything. My files are still intact but I just can't login. I get error 500 credentials invalid. Initially idm seemed to be unable to connect, now it connects but it seems I no longer have an user? To do it I removed opencloud_compose-opencloud-config (with chatgpt help)

Obviously that seemed to delete all users and I just can't log in.

At this point I would be happy being able to do a clean reinstall but i just can't seem to do that either. Anyway i can create a new user and get it working? I have full admin access obs and can modify/delete anything.

[micbar]

@ensapra Hi!

Sorry to hear.

The upgrade does not touch user data, but it may look like there are no spaces. Just let it run some time. https://github.com/opencloud-eu/opencloud/releases/tag/v7.0.0

The config upgrade is documented here https://docs.opencloud.eu/docs/admin/maintenance/upgrade/upgrade-guide/#verify-configuration-changes
That is related to the config changes. You need to run the init --diff command.

Can you restore your config volume? You need these configs to access your user database in idm/idm.boltdb.

[micbar]

You can keep the user data, but then you need the same user IDs.

[ensapra]

How can i create/recreate the same user IDs in a new installation?

[micbar]

That can only work if you do not delete the user database.

[leoyinjou]

Just to chime in a little here, to help anyone in the future... I've successfully upgraded from the "simple" version of opencloud v6.2 to v7.1, which is not documented in the official website. (No Traefik, no Collabora, no WOPI)
However, the upgrade flow is exactly as stated in the official documentation's upgrade guide here. Though you need to know what you are doing and not follow blindly. For example, I have been using the opencloudeu/opencloud-rolling images instead of the "production stable" ones opencloudeu/opencloud, so adapt in your docker compose accordingly.
In short, the only change needed for me from rolling v6.2 to rolling v7.1 were adding 3 lines in the $MNTPOINT/opencloud-config/opencloud.yaml as shown in the opencloud init --diff command:

sharing:
   events:
-    tls_insecure: true
+    tls_insecure: false
+  service_account:
+    service_account_id: somerandomgibberishcalledanaccountid
+    service_account_secret: somerandomgibberishcalledasecrettoken

Note that the service_account_id can be found aplenty throughout the same yaml file, and must be the same; same applies to the service_account_secret, as you'd expect.
And as you see from this diff output, the diff will attempt to undo all the tls_insecure: true, insecure_backends: true and tls_skip_verify_client_cert: true to ensure that your setup is made secure -- however I'm doing this in a very tight private network and not exposed publicly I am aware of and can accept the risks etc. Just make sure that you truly know what you are doing, especially on the security side of things. It's very easy to change things to make it seemingly work for you, but you won't know how much loopholes you have opened up for bad actors in the process.
Happy self hosting and upgrading!

[micbar]

There is more docs available https://docs.opencloud.eu/docs/next/admin/maintenance/upgrade/upgrade-7.x.x