Thank you @james We performed these steps and it was successful: Add these lines in env.sh export NODES_EXCLUDE="["ExecuteCommand", "LocalFileTrigger"]" Restarted N8N Performed the test using these steps: (+) - Execute command Execute Once: ON Command: ffmpeg -version Test step Check the OUTPUT - ok (screenshot attached) [image: 1767355746616-screenshot-from-2026-01-02-13-03-11-resized.png]

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 :).

Hello @zonzonzon The current latest version in the Cloudron app store 2.1.2 is not effected. Also, the latest N8N version for the old 1.123.7 is also not effected. If you have your N8N updated to the last 1.123.7 or 2.1.2 version, then you are save.

I have found the way to enable the chat hub, just go to filemanager in Cloudron, open env.sh file and add this "export N8N_ENABLED_MODULES=chat-hub" and you will see the chat module in left sidebar

Great you found a solution before I even got to read the thread And thanks for sharing it in detail here for others also!

@joseph I just tried "App -> Repair -> Try task again" ... and it fixed both apps. ... Is now a good time to feel stupid? Asking for a friend...

@hakunamatata Can you try the telnet command via SSH first (instead of web terminal) ? I think maybe a machine in DMZ is unable to connect to itself using the public IP ? Can you try `telnet cloudron-lan-ip 993 ?

Just posted this alt, some of you might like to upvote: https://forum.cloudron.io/topic/14544/agno-python-based-open-source-alternative-to-n8n

@james safe as in I want to avoid corruption this is way I pick database number 1 because if; Redis is shared between all the container and attribute different database to each of them then if manually I use a database number (such as 1) I might shoot data and disrupt one of my services. PS: I don't really know Redis but I presume, as in any database, data integrity is important.

Hello @Valexico This is something we would have to look into.

@umnz I have asked here - https://community.n8n.io/t/track-github-or-npm-for-stable-releases/197205

Hello @alexftth and welcome to the Cloudron forum Some questions so we can bet a better picture. Did any app updates happen in the timeframe of this issue arising Did you restart the server since then? If no, please restart the server once When restarted, please ssh into your server and as root run: cloudron-support --troubleshoot Check if it is working now. If not, share the output of this command and also run: cloudron-support --send-diagnostics This will generate a URL with details about your server, share this URL with us here as well. (this also includes IPs and DNS names, if you don't wish to post this publicly, send this with a DM to me) Also re-run the commands you used inside the container and run them from root.

Thanks for the feedback @zonzonzon We could use more feedback from heavy users of N8N to determine if the redis change truly was helpful.

It is not unusual that the memory usage for a service like postgres is filled up. Generally if memory is available it is good to be utilized, however since a database engine doesn't know what else is on the system, we have that limit, otherwise it might just use up everything for caching.

@firmansi latest version was pushed to Cloudron

Hello @JueBam Sometimes, it can be that simple. Good to read, that it is now working for you.