Cloudron Forum

@sfeldkamp see https://forum.cloudron.io/post/117766 for aliasDomains in CloudronManifest.json

That seems wrong. Please send a message to support@cloudron.io and the team will check.

@joseph That is correct. Thanks for the feature support.

@robi interesting thought I'm not sure, but will have a play around.

I've tripled checked (created new key and secret) and it works...

Thanks for looking into it, @james . The situation is the same for me as for @jdaviescoates . Everything works as intended if I enter the address with a trailing slash. The issue only occurs when I don’t include the slash. I run two Yourls instances with the same issue. They are configured the same way. App version: Yourls 1.10.2 Package version: org.yourls.cloudronapp@1.11.2 User management option: Yourls’ own (not Cloudron) Date of installation: 2025-12-31 https://paste.cloudron.io/lixuxaqedo.php

@joseph is this a security enhancement that the Cloudron team can add to a future maintenance release? I would prefer to have Cloudron maintain control of the TURN service so it could enable it based on installed dependencies or leave it off if there are none. Much safer and won't create support issues if someone has disabled TURN ports themselves and then forgets to manage this properly externally.

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

@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