Cloudron Forum

@DualOSWinWiz I don't know if that helps. We had a similar project at this year's Cloudfest hackathon. A frontend connected to a Directus backend. The repo is here -> https://github.com/CMS-Garden/ftm

The website is hosted on a Cloudron instance -> https://www.follow-the-money.org/

Cloudron doesn't support having app's database outside of Cloudron. It will break much functionality like backup/restore/import etc. I think if you want the db outside of Cloudron, you have to host Directus outside Cloudron as well.

@nebulon a checklist of current apps will be ideal scenario

Thank you for the help

@DualOSWinWiz yes, correct. This looks like some kernel related issue or some missing ubuntu package. Can you try to make the NFS mounting work with just the CLI . This will remove Cloudron out of the equation. I think it is possible some missing package or miscompiled kernel.

Yes after upgrading it solved

That seems like mail did not start up properly for some reason. When you find the time, if you run another update and see the box logs or docker logs -f mail , it will help figure what the issue is.

@nebulon Yes i confirmed all 4 n8n containers are updated and working thank you.

Again: https://forum.cloudron.io/post/79353

@DualOSWinWiz With release 1.17.0, there is now a 5-second delay between failed login attempts.

The only way Minio operates with externals is if it is being used as a mirror, or, "bucket replication". Even then, the destination of the replicated bucket has to also be on a Minio system. Your best approach is to install ONE Minio system, externally, and then setup Cloudron to backup (and backup it's backups) to THAT external Minio.

@girish yes its working now thank you i will observe

@girish thank you problem solved

@robi new cloudron release

@girish no it was just on ip:port so i installed today nginx proxy and it worked through that with hrms.domainname.com wild card certificate

There are basically two apps in one with Typebot. There's the "builder" app which is the admin interface used to create and manage bot flow (this has the auth tied to it), and the "viewer" app, which is where published bots can be viewed by the public. I don't think you can add auth to the viewer URLs.

CleanShot 2023-09-03 at 19.24.05.jpeg

Yeah, second this.

Wazuh has a great docker image that's maintained by the project itself.

https://documentation.wazuh.com/current/deployment-options/docker/wazuh-container.html
https://github.com/wazuh/wazuh-docker

I have not used VMWare tools extensively, but I think you can do the below

Take a full Cloudron backups before you do anything. I think the best approach is to simply use VMware snapshots. Snapshot the VM. Move/copy the snapshot to the end destination and create a new VM again from snapshot. Depending on your setup, maybe the move/copy is redundant. As I said, I don't really know much about the VMware tools. Change the IP address of the dashboard my.cloudron.example to the new IP manually. i.e via your DNS provider. Start the the new VM. You should be able to visit my.cloudron.example already and login Once you visit, go to Domains -> Sync DNS. This will resync all the DNS entries with the new IP automatically.

That should be it, I guess.

If something goes bad, please let us know here and you can always start up the old instance immediately and continue.

@girish Hi i recieved today's email which you sent i am reverting back to 1.17.1 thank you.