I didn't thought of any specific LDAP server. It would be great to connect Cloudron to any external LDAP server, that would manage groups and users. For example, connect a Cloudron server to another one so that only one Cloudron server manages the users and groups for both servers.

As a company, we use a self-hosted dolibarr on an external server. It would be really usefull to have it directly in Cloudron!

Yes, this would be really great!

Hi,

When creating the event, a mail is sent from Cloudron server with the author mail. Then, when an attendee answers from its client, it sends a mail to the author's cloudron mailbox.

Is there a way to link this answer mail to the nextcloud calendar so the attendee status is automatically updated?

Thanks!

Hi,

I think there should be a way to use an external LDAP provider for Cloudron. It would enable Cloudron to be more easily integrated into a greater architecture. It links to another suggestion, to make LDAP groups accessible.

Thanks!

Hi,

I think there should be more options to plan the server backuping. Instead of pre-defined options for delays, let the user choose the hours / days both for backup interval and conservation delay, and the moment it should backup.
And even more, make an option to delete old backup except some.
For example, I would like to backup my server every day at 10pm, and keep only :

• the 7 previous days backup
• the first day of each weeks of the current month
• the first day of each previous monthes

I know this is a complex case, but there should be a way to let the user make a custom backup plan.

Thanks!

Hi,

I've got an issue when I want to restore a Cloudron backup on another server. I want to clone my Cloudron server A on another server B : it's what the doc calls "migration" .
I did that to test a complete backup of my main server, while keeping it alive.

What is going on:

• Backup of Cloudron A (running on Ubuntu 16.04)
• Installation of same version Cloudron on ther fresh server B (Ubuntu 18.04)
• Copying Cloudron A backup on server B
• Setting up the DNS of Cloudron B
• Using "Looking to restore" and providing all information
• Near the end, a message saying "Not found" is displayed
• Going to my.<server B>, login prompt is displayed, but it redirects to my.<server A>/login_callback.html?token=<??>&state=<??>
• Subdomains B are unreachable, returning 404 errors
• After rebooting, my.<server B>/#/apps is reachable
• Cloudron B has the same Cloudron ID as Cloudron A
• Subdomains are reachable, but all application are in "Restoring (pending)" status
• When doing cloudron inspect:
  • apiEndpoint is <server B>
  • every <app>.domain is set to <server A> and <app>.fqdn are <app>.<server A>
• Users on server B are correct as well as groups
• When going to "Domains & Certs", an "Internal Error" message appears and "Domains" section is empty
• When adding domain <server B> with a wildcard DNS API provider, it still displays "Internal Error" and an empty domain list
• When repairing applications and setting their domain to <server B>, they are still in "error" status
• When changing all database entries where <server A> was mentionned to <server B>, they are still in "error" status
• Deleting all application then restoring one by one from backup seemed to work, but not for a long time. After a few day, more than half of the applications were in "error" status.

One should be able to clone a Cloudron server easily from a backup, even if the DNS is different. And what are the issue of having two different Cloudron servers with the same ID ?

I submit a new issue for this.

Hello,

It could be great and really usefull for many apps (Nextcloud, DokuWiki, Git...) to make the Cloudron groups accessible on LDAP.

Could it be possible?

Thanks!

@darkben Well, that's exactly what I did, but it ends with the OAuth error. I just fixed it (see my last answer ).

Ok, thanks to a fellow cloudron user on the chat (many thanks robi !), I just made my admin page up again. I just copied my webadmin directory on my server to a dashboard directory on the same level, and yay! the OAuth error just disapeared!