-
@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... =(
@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.
-
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.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login