Cloudron Forum

I'll check when I can. FYI /admin/ with trailing slash works fine.

Hello @creative567145 You have been misguided by this video. ExecuteCommand and LocalFileTrigger have been disabled by default for N8N 2.0 and above, documented here: https://docs.n8n.io/2-0-breaking-changes/#disable-executecommand-and-localfiletrigger-nodes-by-default You can edit your /app/data/env.sh file and add export NODES_EXCLUDE="[]" save the file and restart your N8N app, to re-enable all disabled nodes. But be advised, ExecuteCommand and LocalFileTrigger nodes have been disabled by default because they pose security risks since N8N on Cloudron is running inside docker and not on the system itself you will not find ffmpeg on the system but inside the docker container of N8N. After you have followed step 1. above, following up referring to the video, you can skip to the last part and test it with ExecuteCommand and ffmpeg -version since ffpmeg is installed in docker. I have confirmed this is working with the Cloudron N8N package version 4.1.1 (screenshot below number (1)) packaging N8N version 2.1.4 (screenshot below number (2)). [image: 1767280617873-86fc2996-59e6-47d1-9039-3ae78fceef49-image-resized.png] Running ffpemg -version in the Cloudron app after adding export NODES_EXCLUDE="[]" to /app/data/env.sh and restarting the app. [image: 1767280572185-4f871639-81ff-492f-9d35-1cccbc260e78-image-resized.png]

Hello @luisegundo Have you looked at the official Chatwoot documentation for this? https://developers.chatwoot.com/self-hosted/configuration/features/integrations/instagram-channel-setup If so, have you tried following these steps, and if failing, please describe in detail the steps you have taken to reproduce your issue.

Announcing ... CCAI-P : Cloudron CustomApp Installer Personal Edition Recognising that many users are reluctant to enter their cloudron credentials on an open url, I have adapted the current "open" CCAI custom app installer, into a "closed" app using cloudron ProxyAuth for authentication, and a token for installations. While a one-time install of the Personal CustomApp Installer is needed, manually or using the hosted CCAI, after that, the user is secure with their own app deployment, and credentials do not need to be entered on a 3rd party site. The Personal Edition has a button to import the master app catalogue when needed. The Personal Edition feels a lot faster as no login code / 2FA is needed. My Git Repo : https://git.cloudron.io/timconsidine/cloudron-customapp-installer-personal Built Docker Image : tcmbp132021/cloudron-customapp-installer-personal:v1.0.0 Available on the open CCAI site https://ccai.appx.uk

Err ... a disclaimer / alert is needed that Pydio uses MinIO under the hood. Given the MinIO changes, I don't know (haven't checked) how this might affect the acceptability of Pydio Cells as a solution. Might depend on your personal stance. But Pydio 5 is coming and that might change things. Yes, Pydio Cells uses MinIO under the hood. Here is the breakdown: Storage Layer : Pydio Cells treats all storage (even local files) as object storage. Internal Usage : It embeds a forked version of MinIO to manage the data layer. When you create a "local" datasource, Cells actually spins up an internal MinIO gateway/server to manage those files as if they were in an S3 bucket. API : This allows Pydio to use the standard S3 API for file operations (uploads, downloads, multipart) internally and externally, regardless of whether the actual data is on a local disk, an actual S3 bucket, or Azure Blob storage. You do not need to install MinIO separately; it is bundled and managed automatically by the Cells binary.

@girish don't forget the App Store description

https://git.cloudron.io/packages/dawarich-app/-/merge_requests/12

Same here on Brave Desktop. This is a very recent behaviour, so something must have changed.

Cool, thank you! I also use an app called LocalSend which works across desktop and mobile when you are on the same network/vlan. Cheers

Sounds good and reminds me of this legendary cyclist: https://en.wikipedia.org/wiki/Miguel_Induráin

Ok, so after looking into open ports a bit more, it turns out that there is nothing listening on port 587. As such, there is no SMTP server running or listening to any port whatsoever. I figure that an SMTP server may only start running if I enable incoming emails (setting which was not enabled, purposefully). When I enabled incoming email setting, sudo netstat -tlnp | grep 587 was finally returning something and n8n configuration worked fine. So to sum up, if my understanding is correct, when only using outbound mail, there isn't an actual SMTP server running, but only some kind of abstraction that containerized apps can use to send email directly through the mail relay (the internals of this are fuzzy to me...), so I need to enable incoming emails in order to send emails... But I'm glad I was at least able to make this work before going into 2026. Thanks for the help and for putting me on the right path here. Thank you for all the great work you do Cloudron Team, and wishing you all the best for the new year :).

@james this won’t fix the issue of logging everyone out though I assume? Edit: just saw the newest update.

i went into a problem if DB is accessed by 3rd party the backup failed with error as its accessed by someone else @joseph @girish any thoughts can we force db to close all connections at time of backup request came kind of like a script in dummy application

@james said in Cloudron App Install Update Error Bug: Hello @dualoswinwiz Please use registry.docker.com as the docker hub server address. This should resolve the issue. i was using like this registry.hub.docker.com --- changing this to registry.docker.com solved the problem

Thank you, I didn't know! I have now set it up using Owntracks and it seems to work.