From cloudron side, you can get an app password with mail access for the user. This is easy with REST API. On nextcloud side, you have to figure how to automate a mailbox set up for a user with that password .

@james Thanks - I did look, but it doesn't seem to be a consistent thing. Up until last week, they were all in the same camera pictures folder where most worked and some didn't. This weekend I picked another folder for auto upload, and I see about 80% of them actually uploaded but the sync didn't realize it properly so now it sees it as a conflict.

That did the trick! Thank you! We can close this topic now.

@jdaviescoates Pure gold! I just cleaned up 30ish GB I hope setting the max/min age to 30/7 should prevent this from building up anytime soon.

Thank you for your reply. I have disabled the Nextcloud standard login a while ago so for now users can only login via their Cloudron’s account (including me ). I will try to figure out how to revert that

I've been following the instructions in threads cited below, and it looks like notify_push is up and running configure nginx https://forum.cloudron.io/post/48343 run notify_push via script https://forum.cloudron.io/post/48298

Thank for the reply! I was able to resolve the issue. The external SSHFS volume was still registered in Cloudron, but the remote server was offline, causing the container to fail during startup. Since the mount point was stuck and not removable at first, I proceeded as follows: sudo rmdir /mnt/volumes/... mkdir /mnt/volumes/... cd /mnt/volumes/... By recreating an empty local folder at the exact path Cloudron expected, the app was finally able to start again. Once the app was running, I could remove the external volume cleanly from the Storage configuration in the Cloudron dashboard.

@SolarSimon I'd never even spotted those settings before but see e.g. here https://github.com/nextcloud/server/issues/53705#issuecomment-3012715584 In short, open the web terminal and run: occ config:system:set updatechecker --value=true --type=boolean It should then reappear for you: [image: 1764933999185-img_20251205_112552.jpg]

@vitalymp You can simply create a new user with some bot name and then make a POST call to your nextcloud instance using that users basic auth credentials after recieving data with a webhook. Something like this: { "nodes": [ { "parameters": { "method": "POST", "url": "https://cloud.tld.com/ocs/v2.php/apps/spreed/api/v4/chat/CHAT-ID", "authentication": "genericCredentialType", "genericAuthType": "httpBasicAuth", "sendQuery": true, "queryParameters": { "parameters": [ { "name": "message", "value": "=Message content" } ] }, "sendHeaders": true, "headerParameters": { "parameters": [ { "name": "OCS-APIRequest", "value": "true" }, { "name": "Content-Type", "value": "application/json" }, { "name": "Accept", "value": "application/json" } ] }, "options": {} }, "id": "3efc34ee-e77a-477f-9cbd-9e039f64e143", "name": "Post Message to NC Talk room", "type": "n8n-nodes-base.httpRequest", "typeVersion": 4.2, "position": [ 1872, 160 ], "credentials": { "nextCloudApi": { "id": "RQ8xpIKWFMblRfYZ", "name": "cloud.tld.com – bot" }, "httpHeaderAuth": { "id": "v09VrkQtu9eIAUEl", "name": "Header Auth account" }, "httpBasicAuth": { "id": "6ASiFBk1BEcktXcq", "name": "cloud.tld.com bot" } } }, { "parameters": { "path": "a907934a-19a1-4ced-b919-f1db35a4fa93", "options": {} }, "id": "f11e1143-0a6b-4867-abb2-f03a235e0ed0", "name": "Webhook", "type": "n8n-nodes-base.webhook", "typeVersion": 2, "position": [ 1424, 160 ], "webhookId": "a907934a-19a1-4ced-b919-f1db35a4fa93" } ], "connections": { "Webhook": { "main": [ [ { "node": "Post Message to NC Talk room", "type": "main", "index": 0 } ] ] } }, "pinData": {}, "meta": { "templateCredsSetupCompleted": true, "instanceId": "a382289a228a66b7e622210301ab5b6d8d06d93edb07378019866ea75d7e5793" } }

Hello @Jordy Be very careful with Nextcloud and migrating an OIDC setup. I know that Nextcloud does not play well with these type of migrations. Always test this with a clone from backup and a new installation with the same version where you select let the app handle accounts. There is this app https://apps.nextcloud.com/apps/user_migration for user migration but still, proceed with caution. I've looked into the LDAP to local user migration and have all SQL queries to do that, but not for OIDC to local user. How Nextcloud behaves if you simply change the OIDC provider I can't tell right now. So please keep us updated with findings.

@jdaviescoates so here is my config which works well and gets around the admin group issue. In the OIDC NC app config: [image: 1761898465348-d83b7885-4c11-4657-a8ec-04de244e47e7-image.png] Then you create a group folder per NC group, and when you add a user to Cloudron and add to a specific Cloudron group, it gets automatically added to the corresponding MC group and gets access to the group folder associated with that group. In addition, in order not to confuse users with the NC login form I now disable other login methods using this command: occ config:app:set --value=0 user_oidc allow_multiple_user_backends and set a custom end point to my Cloudron dashboard when people try to log out of Nextcloud: [image: 1761898688780-4316b19b-2691-44b7-b6ec-5fc19a0f335c-image.png]

oh! yes I forgot about that aspect of update control. Thanks for letting us know. I have set it now to show a stable update for all. Sorry for the confusion.

@nebulon said in Nextcloud Mail issues: Or are you worried about something else? Nope, not at all. Thanks again for your help and explanation. @jdaviescoates said in Nextcloud Mail issues: I guess it must've / might've had something to do with you moving the docker stuff around Yeah, I think that's the case. If I didn't already have a complex setup, I might consider just reinstalling Cloudron, but for now that's not an option. And to be honest, it doesn't make much sense to reinstall the whole system just because of a single Nextcloud app If it works for now, it works.

My comment to this thread maybe out of context, but as your information, I have tried for the last 1 year till today, Collabora as Nextcloud Office with Nextcloud Community Edition ,since I have no idea how good Collabora running on NC Enterprise Edition, is not reliable, i've been using onlyoffice and seems onlyoffice is much mature in stability and reliability especially running with NC Community Edition

@nebulon Thanks. I chose to do a restore, since I could manually replace files that were updated/changed during these days. Edit: will you pull the update? Or should I set my Nextcloud instance to stop auto updating? I still have two issues remaining, but these have probably been there a long time: WebSocket server URL is not configured. Real-time collaboration requires a separate WebSocket server. Basic whiteboard functionality works without it. For more details see the documentation ↗. No High-performance backend configured - Running Nextcloud Talk without the High-performance backend only scales for very small calls (max. 2-3 participants). Please set up the High-performance backend to ensure calls with multiple participants work seamlessly. For more details see the documentation ↗.

@andreasdueren thanks, that might be the way to go. I guess perhaps recordings could also be potentially achieved by inviting some external AI bot to come and record too

Looks like its back up, all

Okay, thanks! Just switched to the Cloudron app, and it is working nicely so far.