@nebulon Hi, I'm loving Cloudron so far! Could you please approve me as well so I can vote on the app wishlist?

Not sure if many are aware of the Cloudron status page https://status.cloudron.io/status/cloudron, so I am just leaving this here.

Hello @tadeas Is this still an issue or can this topic be marked as solved?

Hello @webliska After our private chat and the suggestion to add IPv6 is this still an issue, or can I mark this topic as solved?

Marking this topic as solved since no more input was given from user @jorrg

Hello @mbarria Since there was no more update in this topic can I assume this resolved itself?

Hello @Lomeu Did you figure this out or is this still an issue?

Closing this since no more user details were given.

Closing this issue for now since no further details where provided.

Hello @JueBam Did you get this resolved or is further assistance required?

@girish @james Thanks!

@David-0 the Service Account Username should be set to cn=admin,ou=system,dc=cloudron and Service Account Password should be the Bind password. There are two separate LDAP servers - internal one and an external one. The external facing one can be authenticated against by the one and only "virtual admin user" i.e the admin CN above. Cloudron admin and Cloudron users don't have the permissions to search for other users in the external facing server.

Given the confidential nature of this, please write to us at support@cloudron.io if they need some information on our side.

Fixed here - https://git.cloudron.io/platform/box/-/commit/ac7001b96e176e540ede9bb81e3fcb17ae7f6416

@webliska Is this resolved now?

Hello @CaeruleusAqua Please assist me in understanding this issue better. I want to figure out if is just a single filename or path and filename causing this issue. For this please go into the web terminal of your nextcloud and go into your /app/data/ folder. cd /app/data/ Please run the following command. It will find the deepest path and the longest filename. With these details I can further debug this issue. find . -type d | awk -F/ '{if(NF>max){max=NF; path=$0}} END{print "Max depth:", max-1, "Path:", path}'; \ find . -type f | awk -F/ '{if(length($NF)>max){max=length($NF); file=$0}} END{print "Longest filename length:", max, "File:", file}' Also can you please provide details about your backup provider?

From a deeper investigation, it seems that is has to do with backups and not with Syncthing or Photos app. 4 times a day, Uptime Kuma is backed up, and each time the heartbeat table is dumped into syslog, growing the syslog by 1-2GBs each time. More details in https://forum.cloudron.io/post/112261

See: https://forum.cloudron.io/post/52997

Right, as you already figured out, you have to resize the fs manually. https://docs.cloudron.io/storage/#aws-ebs . Cloudron was more of an app deployment platform. Though after many years depending on which problems are often reported, we are putting in server management features (maybe we will add fs resize at some point).

You can check if the server itself is particularly low on memory by running free -m . Can you give nextcloud much more memory (in the Resources section) ? What is it at currently ?