Nextcloud LDAP server not accepting Cloudron LDAP credentials Linode

[mycc]

@girish No. I have Nextcloud deployed as a Cloudron app on the same server. I do have a separate nextcloud server on a different server as Cloudron with the same problem.

[mycc]

@BrutalBirdie I white listed the Cloudron's IP address under the "Restrict Access" field in the Directory Server. Is there another location where I need to white list an IP address?

[mycc]

@mycc I tried making my base
cn=users, dc=[mydomain without .com],dc=[my subdomain]
This is also giving me errors.

I apologize, I am very new to ldap provisioning and might be making a trivial error.

[girish]

@mycc said in Nextcloud LDAP server not accepting Cloudron LDAP credentials Linode:

@girish No. I have Nextcloud deployed as a Cloudron app on the same server. I do have a separate nextcloud server on a different server as Cloudron with the same problem.

If the app is on Cloudron, you don't need to do any of this. Setting up LDAP/auth with Cloudron is automatic and part of Cloudron packaging. All you have to do is:

• Install nextcloud. When installing, you get the choice of installing with or without Cloudron user management. Select authentication against the Cloudron directory.
• Login with Cloudron credentials.

Did you do the above already? Did it not work for some reason?

(BTW, for the current app, if you just restart the app, the package re-configures LDAP on every start up. So, maybe you can just restart the app and try to login with Cloudron credentials.)

[mycc]

@girish Yes this solution worked for the Nextcloud server provisioned through Cloudron. However, I would also like to use Cloudron as a user management solution for Nextcloud's on different servers. I copied the pre-populated ldap settings that populated on the Cloudron's Nextcloud after restart.

I tried copying them to an external Nextcloud server. I did add both IP addresses to the white list.

The left is the ldap for the Cloudron Nextcloud server. The right is a separate server running Nextcloud.

[nebulon]

So the exposed LDAP server uses different settings. The apps on Cloudron will get their own credentials and local access to LDAP. So an externally run Nextcloud has to have different configs. Have you seen https://docs.cloudron.io/user-management/#directory-server already?

[mycc]

@nebulon Thank you. I followed the guidance in this post before but it still gave me problems.

I selected my own secret and loaded the credentials.

Here is a screenshot of my results.

For user DN cn=admin,ou=system,dc=cloudron

For Base DN I used:
dc=[sub domain]
dc=[domain]
dc=com (my domain ends in .com)

[nebulon]

From the two shown error bubbles in your screenshot, it may seem that nextcloud can't even connect to the server in the first place. Can you double check the IP in the allowlist there? Also do you see any further details in the nextcloud logs about the connection attempt?

[mycc]

@nebulon I went ahead and SSHed into my the server running my Nextcloud and performed an ldapsearch. It is connecting to the server but something is going wrong in Nextcloud or my inputs into the ldap fields in Nextcloud are incorrect.
I verified the server IP address was correct.

Here is a screenshot of the results of that ldap search.

[osobo]

@girish said in Nextcloud LDAP server not accepting Cloudron LDAP credentials Linode:

If the app is on Cloudron, you don't need to do any of this. Setting up LDAP/auth with Cloudron is automatic and part of Cloudron packaging. All you have to do is:

Install nextcloud. When installing, you get the choice of installing with or without Cloudron user management. Select authentication against the Cloudron directory.
Login with Cloudron credentials.

Hello @girish. I'm trying to setup Cloudron LDAP/auth for a Nextcloud app installed on Cloudron (on the same server). But the Nextcloud app was not initially installed with Cloudron user management. Can I change this now or I need to re-install NextCloud completely ? Thanks for your support.

[girish]

@osobo yes, on Cloudron, you cannot change the user management after installation. It's best to re-install from scratch . It's quite complicated and very app specific to migrate existing users to LDAP and vice-versa.

[osobo]

@girish Thank you. Well noted. I will re-instal it then.

PS: In my opinion, it would be worth highlighting this point on the installation screen of the application, as it is a fairly definitive choice.