Cloudron Forum

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.

As I have said, I'm deploying a FLO stack (with Cloudron at the core) into a startup that I'm building (as CIO/CTO). We have to be CMMC compliant. Making sure Cloudron works on a 100% compliant base system is the first milestone. While you may not consider them issues, they do need to be addressed to be compliant. That's "my problem". If a fully compliant base system causes an issue in Cloudron , that's "our problem". While you, and many Cloudron users may not care about CMMC/HIPPA/SOC/PCI compliance, I (and my board) do. I'm also building a small side business which will sell Cloudron as a service (pre setup/configured, all applications have admin password changed, admin passwords stored in Bitwarden) (the new Bitwarden SSO makes that possible without bootstrapping issues) and it will have CMMC/SOC/PCI/HIPPA compliance (at the higher tier).

Happy New Year to all of you! Many thanks for the great community here and we are very much looking forward to a new year of building much requested features for all of you

This is getting updated - https://git.cloudron.io/packages/vaultwarden-app/-/merge_requests/20

@sfeldkamp the API supports it via the aliasDomains property in the domains route but the UI only supports settings the primary domain right now. (not sure if this is what you are asking?)