You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clean install of Nextcloud through unraid community app store, latest stable version php 7. Unable to use LDAP integration as buttons do not have any response. No errors on docker logs or Nextcloud logs level 2. Tested LDAP configuration on clean install of official Nextcloud docker image and Owncloud both worked smoothly. Clicking Test DN or save credentials does nothing. Unable to complete setup as continue button grayed out.
Expected Behavior
Allow to enter and verify LDAP settings.
Current Behavior
You can enter in the required info but clicking on any options does nothing.
Steps to Reproduce
Enable LDAP/AD Integration app and attempt to enter info
Environment
**OS: UNRAID
**CPU architecture: x64
**How docker service was installed: Preinstalled via unraid
Command used to create docker container (run/create/compose/screenshot)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Compared to the Nextcloud 19.0 documentation for an NGINX setup (which the Linuxserver.io container uses), the Nextcloud 20.0 through latest documentation have the aforementioned line added to resolve issues with legacy AJAX endpoints:
# Required for legacy support
rewrite ^/(?!index|remote|public|cron|core\/ajax\/update|status|ocs\/v[12]|updater\/.+|oc[ms]-provider\/.+|.+\/richdocumentscode\/proxy) /index.php$request_uri;
This line is currently missing from this container's NGINX config file as it looks like #133 happened in January and February 2020 but Nextcloud 20.0 (which requires this extra line) came out in October 2020.
Adding that missing line results in the LDAP integration working again.
Activity
github-actions commentedon Feb 23, 2022
Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!
github-actions commentedon Mar 26, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
chrisbley commentedon Mar 27, 2022
same issue here! is this issue going to be addressed? cheers for all the good work!
BoavaNet commentedon Mar 29, 2022
ya having same issues here, damn was hopping to keep all my Authentication with LDAP
NobleKangaroo commentedon Apr 13, 2022
Same issue here. This used to work in the past, but multiple folks have had issues related to routing (1, 2, 3, 4, 5) since Nextcloud 20.0 released.
This looks to be related to a PR for Nextcloud 19 to clean up and standardize the NGINX config and remove redundancy. However it was found that the new config has issues with the legacy ajax endpoints of the user_ldap app. This line was subsequently reverted and added back to the NGINX config's documentation for 20.0 and later, and other projects such as NixOS added the line to their configs.
Compared to the Nextcloud 19.0 documentation for an NGINX setup (which the Linuxserver.io container uses), the Nextcloud 20.0 through latest documentation have the aforementioned line added to resolve issues with legacy AJAX endpoints:
This line is currently missing from this container's NGINX config file as it looks like #133 happened in January and February 2020 but Nextcloud 20.0 (which requires this extra line) came out in October 2020.
Adding that missing line results in the LDAP integration working again.
I'll fire up a PR to get this resolved.