Cloudron Forum

Ah, I had neglected to install Matrix with it's own user management, but had chosen, "Only allow the following users and groups"

@crazybrad my AI says (edited for brevity) : Based on the complexity of Zulip and the requirements of Cloudron packaging, I'd rate this a 7 or 8 out of 10 in terms of difficulty. For someone familiar with both Cloudron packaging and Docker, this could take 40-80 hours of work, depending on how smoothly the integration goes. So maybe a bit more optimistic but certainly a non-trivial project.

Hello @privsec Please ssh into your server and run the following commands and post the output of the commands here: cloudron-support --disable-remote-support cloudron-support --enable-remote-support Then: cloudron-support --troubleshoot

When will this auto-update on Cloudron? We'll all need some time to work through the full list of breaking changes (https://docs.n8n.io/2-0-breaking-changes/) before then.

Hello @allanbowe Please connect to your Cloudron server via ssh and run the following commands and post the output: cloudron-support --troubleshoot and cloudron-support --check-db-migration

I have the same issue after updating Cloudron. I had to re-attach the backup storage and new backups are working, but: the older backups are physically present on the StorageBox, I can see them in each app’s backup list, but they do not appear under Backup Sites, and trying to restore them results in an Task error Retry a failed installation, configuration, update, restore, or backup task. An error occurred during the restore operation: External Error: Error loading fsmetadata.json:ENOENT: no such file or directory, open '/home/yellowtent/appsdata/bebc848c-f9a9-41f9-aeb1-b1d8bf200d73/fsmetadata.json'

Thanks for the response. Pixelfed does have a Custom CSS option in the admin panel, but even with that it's currently not possible to override the logo. I'm also noticing other things not working. I have filtered registrations enabled, but I'm not receiving any emails about new signup requests. And when I try to edit /site/about, the changes don't show up at all. So it seems this is just the current state of Pixelfed. Hopefully the developers will fix these issues in future releases.

Ah I meant maybe more context around the logs of the failing update task.

@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" } }

Oh nice, this is incredible. Can you also make a guide @BrutalBirdie ? A PR to https://docs.cloudron.io/guides/ would be awesome . Not a PHP dev but when/where does one run "composer install" in the workflow ? Maybe in the action itself?

@ekevu123 can you please check for any error in the browser console?

Hi there, Sorry to dig this up but. Is it really disabled on the selfhosted app ? I managed to activate "workflows" in the settings page (/settings/admin/flags) [image: 1764161572348-e626f64d-c6a3-4ed4-95ad-3c7cd9452561-image-resized.png] I discover workflows don't run on themself and needed to be triggered by external cronjob, which I did via Cloudron : * * * * * curl -fsS -X POST -H "authorization: $CRON_API_KEY" http://localhost:3000/api/cron/workflows/scheduleEmailReminders > /dev/null 2>&1 I also discover it needed some env variables to work : ENABLE_TASK_SYSTEM=true CRON_ENABLE_APP_SYNC=true CRON_API_KEY=*** When calling this URL from the instance itself, I even got a status:200 code with a JSON response {"message":"No Emails to schedule"} And this is my problem now : it says no emails to schedule while there is actual emails scheduled (from workflow). It is visible in the postgres tables "WorkflowReminder" and "Task". I even see in the log that the task is set up for scheduling. But at the end, the workflow is never executed and I'm out of solutions. What a complicated journey just to get this feature working, even though it’s advertised as available in the free version (so I assumed it would work in self-hosted as well). Or am I missing something? Could you clarify this for me? Thanks.

@timconsidine you are welcome. You can always test on the demo server. And at least the second issue is easily solved via an expected version bump or just take out the check. Not sure why it's needed. Is it?

@ghosted @mdc773 sorry for the inconvenience, a fix is coming, most likely later today. In the meantime, if it's urgent, you can write to support@cloudron.io and we can patch your server individually for this bug. The issue happens when the import/restore form is filled up manually. If you use a backup config file, it works. To workaround: Download the backup config of any current app. App -> Backups -> Select backup -> ... -> Download Config to your desktop. Edit that config json file on your desktop and change the remotePath field. App -> Backups -> Import -> Upload a backup config . This works because the config file sets prefix to "" internally.