Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
C

corevoid

@corevoid
About
Posts
1
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • LDAP directory service not running or exposed after update to 8.0.3
    C corevoid

    Since the update to 8.0.3, multiple of our Cloudron instances are no longer listening for LDAP connections. We have the Directory Server enabled under the User Directory section. There is a bind password set and the server URL matches the DNS for the server(ldaps port 636).

    From looking on the server, it looks like the port 636 is forwarded to port 3004. On those servers, there is nothing listening on that port. On another Cloudron we have, we can see that a 'node' process binds that port. We never see that on the updated instances. We have tried changing the bind password and made sure the correct IPs are in the restriction list.

    The main node process never binds that port though. How can we fix this? Are there any known issues or tricks for this? We have several external services relying on it. Let me know if I can provide any further info at all.

    Support ldap directoryserver
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search