Cloudron Forum

@girish This makes a lot of sense for HashiCorp Vault, since it acts as a central trust component and supplies credentials to applications hosted separately. It also fits reasonably well for Uptime Kuma, where servers send heartbeat signals, though that’s a lighter use case. Another strong case is when Cloudron itself is used as the OIDC provider for other applications.

Hello @estudios507 Thank you for the detailed report. I will try to assist you to my best capabilities. @estudios507 said in Cloudron rejects iCloud forwarding only when “Delete after forwarding” is enabled (SMTP 550 on MAIL FROM): Identify which Cloudron restriction/policy is triggering “Mail from domain ‘X’ is not allowed from your host” in this scenario. Regarding why this is happening. When iCloud forwards messages in delete mode, iCloud uses the original sender’s MAIL FROM (envelope-from) unchanged instead of rewriting it. If that original sender domain is hosted on the same Cloudron server, Cloudron sees an external connection (from iCloud’s outbound IP) claiming to send mail from its own domain. Cloudron treats that as spoofing and rejects it. @estudios507 said in Cloudron rejects iCloud forwarding only when “Delete after forwarding” is enabled (SMTP 550 on MAIL FROM): Confirm whether there is a supported and safe way in Cloudron to allow this specific flow (forwarding from iCloud with delete enabled) without broadly weakening anti-spoofing protections. There is also another topic regarding this issue with iCloud, see: https://forum.cloudron.io/topic/1998/mail-error-after-sending-message-mail-from-domain-example-com-is-not-allowed-from-your-host A fix is to add the iCloud servers to the domain A's SPF record. Your current SPF record is: dig TXT estudios507.com +short "v=spf1 a:mail.estudios507.com include:_spf.safewebservices.com ~all" You can edit that to include apple: "v=spf1 a:mail.estudios507.com include:_spf.safewebservices.com include:_spf.apple.com ~all" after that edit it can take some time to propagate, but this should resolve your issue.

I have just pushed an update (fixing some ZM UI rendering) latest docker image build : tcmbp132021/cloudron-zoneminder:v2.0.27 Anyone with an existing installation of CCAI-P and using that to deploy : press logout connect import catalogue select Zoneminder and ensure the build is v2.0.27

Technical update: LDAP authentication is now working. The fix was to move the whole LDAP setup into start.sh and make it fully deterministic: • wait for the MySQL service to be reachable • inject the LDAP configuration directly into glpi_authldaps using Cloudron-provided env vars • clear GLPI cache • run an explicit ldap:sync This avoids init-time race conditions and inconsistent behavior observed with glpi:ldap:create alone. Current repo reflects the working implementation.

@jdaviescoates can you ping him and ask how hard the upkeep would be for a new fork the way we need it? Perhaps call it Snicketteer

@marcusquinn said in Option to Restore or Toggle the Old Cloudron UI Layout: To be fair, the Notifications UX has regressed. Hoping the old way of navigating that comes back at some point. I'm also always wanting for minimal clicks, and max keyboard navigation. OMG yes, the keyboard nav has been a wishlist item for so long!

@girish thanks, I've only just realised the hosted version seems to have disappeared https://linksta.cc/ Indeed it seems nearly all (but not all) instances are down https://linkstack.org/instances/

@james Thanks for the info

Hello @potemkin_ai @potemkin_ai said in Can't connect to NextCloud console: The Cloudron is behind a proxy This is a mayor detail which you should have mentioned earlier since it is outside the default Cloudron spectrum. Is it the whole Cloudron or just Nextcloud? Please explain in detail what you mean with Cloudron is behind a proxy.

Also matomo and umami and many others work with Ghost. It's just the native integration in the dashboard of Ghost that makes it interesting.

A small suggestion for formatting your wish list: --- ## **Title**: Flowise on Cloudron - Build AI Agents Visually *** * **Main Page**: https://flowiseai.com * **Git**: https://github.com/FlowiseAI/Flowise * **Licence**: Apache License Version 2.0 * **Dockerfile**: Yes * **Demo**: https://flowiseai.com (Free tier available with 2 flows) *** * **Summary**: Flowise is an open-source generative AI development platform that enables building AI agents and LLM (Large Language Model) applications visually, without coding. The tool offers a drag-and-drop interface to create custom workflows, integration with various LLM providers (OpenAI, Anthropic, Azure, etc.), RAG (Retrieval-Augmented Generation) support, conversational memory management, and multi-tool agent capabilities. It features a modular architecture with Node.js backend, React frontend, and third-party integration components. *** * **Notes**: Flowise is an excellent alternative for those looking to implement AI solutions without complex programming. It offers advanced features such as Document Stores, vector databases (Pinecone, Qdrant, Chroma, etc.), response streaming, and monitoring with OpenTelemetry/Prometheus/Grafana. Supports deployment via Docker, Docker Compose, and includes Redis queue configuration for scalability. The community is active with over 21 contributors to the main repository. Concerns include managing credentials for external APIs and the need for proper storage configuration for data persistence. *** * **Alternative to / Libhunt link**: https://www.libhunt.com/r/Flowise * **Screenshots**: - Official logo: https://github.com/FlowiseAI/Flowise/blob/main/images/flowise.png - Demo GIF: https://github.com/FlowiseAI/Flowise/blob/main/images/flowise_agentflow.gif - Additional screenshots available in the GitHub repository and official documentation *** **Additional Technical Information:** - Default port: 3000 - Supports SQLite, MySQL, PostgreSQL as database - Storage: Local, AWS S3, Google Cloud Storage - Requires Node.js 18.15.0 or higher - Available on Docker Hub as official image

@joseph Thanks for this update. I see no point (for me) in going further with Postiz. I would support looking for a better alternative.

@nebulon there seems to be none of the dead ones: ubuntu@cloudron:~$ sudo docker ps -a | grep sqlite | wc -l 1 ubuntu@cloudron:~$ sudo docker ps -a | grep sqlite bbb52ef9e686 cloudron/louislam.uptimekuma.app:202511081423470000 "sqlite3 /app/data/d…" 2 weeks ago Created sqlite-be0be218-57bf-427b-abb6-b7660943eaf6 There are not that much non-running containers - only 2 nextcloud workers with exit(0) and another service, that I have stopped explicitely.

@andreasdueren Provider for minio? AT any rate, I posted the above after just installing formbricks to see if I could help the OP, then I uninstalled it. I'm no help now!

@girish that's good analysis. That's good example of why we need review before adopting it into AppStore. Honestly ... I didn't encounter the issues you raised, simply because I never work in the way that I sign up to the SaaS aspect. I just use the UI, save a PNG or screenshot and throw away the design. Only use it for quick sketches and explainer diagrams. My package was purely to get it off my Traefik/docker-compose VPS onto Cloudron, because might shut down the Traefik VPS. Yes, entirely viable to just use the main website and did that for a while. Should it go in the AppStore ? I don't have a strong view. Others might, because, as you say, privacy issues. But they don't crop up for me in this app.