# Error LDAP - 3.0.0

**URL:** <https://community.datagerry.com/t/error-ldap-3-0-0/781>\
**Category:** Report a Bug\
**Created:** [August 21, 2025, 9:02am UTC](https://community.datagerry.com/t/error-ldap-3-0-0/781 "2025-08-21T09:02:22Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![Luca](https://avatars.discourse-cdn.com/v4/letter/l/51bf81/32.png) [@Luca](https://community.datagerry.com/u/Luca)\
**Post date:** [November 2, 2025, 6:46pm UTC](https://community.datagerry.com/t/error-ldap-3-0-0/781/13 "2025-11-02T18:46:17Z")

</div>

That with the port 4000 looks like a bigger problem, that is not bound to LDAP. We have the same issue: [Issue with Datagerry on Kubernetes with Envoy – Redirect to Port 4000](https://community.datagerry.com/t/issue-with-datagerry-on-kubernetes-with-envoy-redirect-to-port-4000/785/) . We found a workaround by patching the hard-coded port values in the code and build the container ourselves. Maybe it can help you too, even if an upstream fix is clearly needed here.

---

_[View the full topic](https://community.datagerry.com/t/error-ldap-3-0-0/781)._