@opensourced
Hello!

Is it possible, that you describe your way of connecting Cloudron with Truenas?

I'm using Cloudron on a VPS. In addition, I'm using TrueNAS at home. I want to use TrueNAS as backup space for Cloudron. Like you, I was thinking about NFS.

I'm wondering, if this connection is transport encrypted. Which port have you set in your firewall or are you using VPN? What user information have you set in TrueNAS?

I have experimented with Syncthing, to send my backups to Truenas. This works mostly fine. However, after a few days, I'm getting problems with permissions.

Greetings

Eismer

I have put a fix in https://git.cloudron.io/cloudron/box/-/commits/bfb233eca19df07a82e3b524812d8270371ed738 which should hopefully fix this.

I have put a fix in https://git.cloudron.io/cloudron/box/-/commits/bfb233eca19df07a82e3b524812d8270371ed738 which should hopefully fix this.

@Aizat Let's discuss at https://forum.cloudron.io/topic/6719/sftp-port-222-not-working-firewall-ufw-was-inactive

@girish Just wrote in. Thank you for your help.

See https://forum.cloudron.io/topic/6632/help-me-please-got-error-while-installing-the-cloudron-on-a-fresh-ubuntu-20-04-x64-server

Tested and confirmed fixed - thanks!

@girish That's not it. You have OOMs because people install all sorts of apps and try to abuse the system, like WP and trying out large plugins.

My system has 0 OOMs. None.

Mine also has enough of IO as I asked them to limit the number of new customers on the host system.

# dd if=/dev/zero of=/tmp/test1.img bs=1G count=1 oflag=dsync ; rm /tmp/test1.img 1+0 records in 1+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 5.50861 s, 195 MB/s

Doesn't explain 48GB mem spikes.

This only seems to be happening on 20.04 Cloudrons, not 18.04.

Btw, the main issue I think you're having is the choice of that NY datacenter, it's networking isn't great, they seem to allow burst traffic but then quickly throttle down or experience congestion.

Seattle has been way better for me.

@matthewdykstra it's turned has most features off by default. Why do you think it takes up memory/resources ?

@marcusquinn this is a duplicate of https://forum.cloudron.io/topic/6648/cannot-enforce-2fa-on-7-1-3

@girish I think it was ultimately a disk space issue - I restarted unbound and that seemed to do the trick. I have to move servers again because of a Vultr restriction (block storage not in the zone I had the VM in) that's unrelated to Cloudron so I'll see what happens. Thanks guys!

@girish Thanks Girish. I assume that'll be fixed in the next bug-fix release as it looks fixed already in the code from this bug report (referencing for others): https://git.cloudron.io/cloudron/dashboard/-/commit/b62da8ba70dd8b4a8964de5a2c01e6ff7afa0e99

That took a while but we are back in business - https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci

@vladimir-d said in LDAP not exposing outside:

Also I noticed that if I save Directory Server configuration several times, multiple duplicate rules added to iptables:

I was able to reproduce this, thanks for reporting. It's fixed in the next release - https://git.cloudron.io/cloudron/box/-/commit/d13905377c375823e7b6fd66bd248421544a1d2c .

The duplicate rules are harmless nevertheless.

@WaffleUncle So you are using the Import button in the app section, correct - https://docs.cloudron.io/backups/#import-app-backup ?

In your case, it looks like your backups were in the file system and not external. If that is the case, you have to fill up the 'Import Backup' dialog manually:

Upload the backup app_client.xxx.tar.gz to somewhere in the server like /tmp/app_client.xxx.tar.gz.

In the import UI, Choose Filesystem

Put the path as /tmp/app_client.xxx.tar.gz

It should import now.

@girish The issue was fixed with last automatic update.

Thank you!

@girish That's awesome, thank you. I was going to do it and post the screenshots here, but paused, not sure if even starting the process would "turn it on" and then what... This is super helpeful.

@JavaCraft Can you post the output of free -m ?

To move ahead, you can just edit the line readonly MINIMUM_MEMORY="974" to be something lower in the cloudron-setup script. It's at the top of the file around line 14 and run the setup script again.

@nebulon said in my.cloudron.tld is not accessible:

nosudo

thank you for eyes and help 😉
this is so weird and like you I don't know that option.

also; etckeeper as not being initiated on that server, so I'm unable to retrace when that change has been made

This happened to me to, and I had to do a full reboot to get the apps back up.