This looks really interesting:

https://github.com/nitnelave/lldap

Has anyone looked into how it might be used with Cloudron?

From the github page:

A lightweight authentication server that provides an opinionated, simplified LDAP interface for authentication. It integrates with many backends, from KeyCloak to Authelia to Nextcloud and more!

It comes with a frontend that makes user management easy, and allows users to edit their own details or reset their password by email.

The goal is not to provide a full LDAP server; if you're interested in that, check out OpenLDAP. This server is a user management system that is:

• simple to setup (no messing around with slapd),
• simple to manage (friendly web UI),
• low resources,
• opinionated with basic defaults so you don't have to understand the subtleties of LDAP.

@girish It's fixed! Thank you very much.

@girish Thank you, this did the trick. In my case, I have Ubuntu 20.04 on a kvm inside my host, so I had to change the inotify watch limit for the "inner host". The warning message went away a few minutes after that.

This looks really interesting:

https://github.com/nitnelave/lldap

Has anyone looked into how it might be used with Cloudron?

From the github page:

A lightweight authentication server that provides an opinionated, simplified LDAP interface for authentication. It integrates with many backends, from KeyCloak to Authelia to Nextcloud and more!

It comes with a frontend that makes user management easy, and allows users to edit their own details or reset their password by email.

The goal is not to provide a full LDAP server; if you're interested in that, check out OpenLDAP. This server is a user management system that is:

• simple to setup (no messing around with slapd),
• simple to manage (friendly web UI),
• low resources,
• opinionated with basic defaults so you don't have to understand the subtleties of LDAP.

@girish It's fixed! Thank you very much.

@subven Yes, I did take a look there and my yml is still set to the default 20 MB. Is that what you mean for me to check for?

A couple of interesting notes:

• Reducing the size of the image to ~2 MB does not help
• But I can upload an image that is about 100KB

@girish Thank you, this did the trick. In my case, I have Ubuntu 20.04 on a kvm inside my host, so I had to change the inotify watch limit for the "inner host". The warning message went away a few minutes after that.

I get the following error when trying to attach/upload a 4.6 MB image to a Vikunja task:

413 Request Entity Too Large
nginx/1.18.0 (Ubuntu)

Reading a few other threads here related to this error message (but for different apps) one of the recommendations was to increase the RAM. I did so, from 256 MB to 1 GB; however, the error remains when trying to upload.

Any suggested solutions from here?

@necrevistonnezr said in ownCloud Infinite Scale:

Public Beta is out! https://owncloud.com/infinite-scale-beta/

Exciting! I'd love to see ownCloud hosted on Cloudron. We've been using SyncThing for files and while effective, it has proven difficult to get new members of the team set up with it. Of course, ownCloud has many additional features besides file sync that would be valuable as well.

I'm seeing the following warning/error message in my hosted syncthing web page:

Filesystem Watcher Errors

For the following folders an error occurred while starting to watch for changes. It will be retried every minute, so the errors might go away soon. If they persist, try to fix the underlying issue and ask for help if you can't.

Support Sync
failed to setup inotify handler. Please increase inotify limits, see https://docs.syncthing.net/users/faq.html#inotify-limits

Does this need to be modified on the host, or within docker? What is the recommended way to do this?