NextCloud can't start after v5.8.4 update

[joseph]

Could it be that you have disabled the OIDC plugin? Clearly it's installed (the lines above it). Can you use the occ tool to enable the plugin manually?

[potemkin_ai]

@joseph said:

Could it be that you have disabled the OIDC plugin? Clearly it's installed (the lines above it).

99.9999% not. I'll leave 0.0001% for the case if UFO manipulated my brain somehow...

Can you use the occ tool to enable the plugin manually?

I've changed the script with vi and executed it - so, yeah, I guess I can

Would you mind guiding me?

[james]

Hello @potemkin_ai
Here you can find instructions on how to enable or disable apps in Nextcloud https://docs.cloudron.io/packages/nextcloud#fixing-a-broken-install

[joseph]

I am thinking may be sudo -u www-data php /app/code/occ app:enable user_oidc . @james should we fix the package to always enable oidc (not just install)?

[potemkin_ai]

@joseph thank you!
I've tried that (during LLM research phase):

# sudo -u www-data php /app/code/occ app:enable user_oidc
App "OpenID Connect user backend" cannot be installed because it is not compatible with this version of the server.

We got stuck with LLM - from what I recall, we didn't find why the extension can't be updated to support the latest version as well.

[joseph]

@potemkin_ai strange . i cannot reproduce this here - nextcloud 34.0.1 supports the latest oidc app .

[potemkin_ai]

@joseph said:

@potemkin_ai strange . i cannot reproduce this here - nextcloud 34.0.1 supports the latest oidc app .

I can't reproduce it anywhere (and I have some instances running)!

What do I do to restore that / to get it working?

[potemkin_ai]

I'm sorry... Anyone?

[jdaviescoates]

@potemkin_ai have you tried running the appropriate commands via the web terminal? or just using the File manager to completely delete the related plugin folder?

[potemkin_ai]

@jdaviescoates I've tried quite a lot...

delete the related plugin folder

do you mean the auth plugin, that actually let me login at all?

[jdaviescoates]

@potemkin_ai yes, I mean (clone your broken app and then) delete the user_oidc app to see if it then starts-up. If it does, you'll know for sure it's something about that app that is the issue.

In fact, what I think I'd try first (I'm just thinking out loud here) would be to rename the folder to user_oidc.backup as that would likely disable it too. And then deleting it completely if that doesn't work.

And if it does start up without that app, try copying the same user_oidc folder from one of your working Nextcloud installs into it's place. And if the cloned app then starts up and you can login, repeat the process on your original broken app.

Can't hurt to give that a try?

[potemkin_ai]

@jdaviescoates thank you, appreciate it.

If support (@joseph , @james ) won't support me in this case - that is what I will have to do, yes... =(

[jdaviescoates]

@potemkin_ai tbf I'm not sure what they could do really, other than suggest similar stuff. Unless you enable remote access and email support@ asking them to take a look.

[potemkin_ai]

Viva la LLM:

The container is healthy now — 1 running, 0 unresponsive. The Cloudron update worked:
- New image: cloudron/com.nextcloud.cloudronapp:202607231345050000
- Nextcloud: 34.0.2 (up from 34.0.1)
- user_oidc: 8.10.1 — working!
How extensions should be updated in Nextcloud under Cloudron
The proper way is:
1. occ app:update — updates from Nextcloud app store to /app/data/apps/ (persistent across restarts)
2. Nextcloud web UI → Apps — same effect
3. Cloudron app package update — what you just did; the vendor bundles newer versions in the image
The root issue was that the old image (202606251555380000) bundled user_oidc 8.3.0 which had max-version="33" — incompatible with Nextcloud 34. The startup script's $occ user_oidc:provider command couldn't register. The data volume still had our manually-installed 8.10.1 from earlier.
The new image (202607231345050000) likely bundles a compatible version, or my 8.10.1 on the data volume is now taking effect.