Cloudron Forum

We have a Cloudron instance that we have been using for a good while as an LDAP provider. Since this latest upgrade, the LDAP service will not start and/or bind on the host. We have the Directory Server enabled under the User Directory page. The Server URL matches the host and is correct(ldaps and 636). There is a bind password set and we have IPs listed in the restrect access section. This configuration has not changed from before the upgrade, and the LDAP service was being used externally before that just fine.

I did note that, it looks like the the 636 port is being redirected internally(the Cloudron firewall config) on the host to port 3004 . However, that port is not exposed on the host at all. We cannot see any process or service binding that port. We have attempted to disable and re-enable the Director Server from the UI there, along with trying to change the bind password and adding/removing IPs from the list. None seem to impact this.

We do have other Cloudron hosts, and I have enabled it on one of them to test, and I do see that the 'node' process for Box looks to be what is binding the port 3004 on there. I do not see that getting bound on this host though.

Any ideas on how to resolve this? Anything we can try? Any known issues like this after the upgrade? Is there any further information I can provide at all? We do not see anything there in the logs when saving the Directory Server config in the UI. We really need this working, as there are multiple external services that use that for client services.

We've encountered two instances of a terrible bug which occurs due to the user's time zone.

The first time we encountered it was not setting any time zones in the app. As soon as the a task became overdue the app crashed. There was a specific error message in the logs but that's been lost .

The second time was on a new instance, which occured as soon as you set a time zone. I set mine to Mexico City.

The front end became blank with this error in dev console. No stdout logs.

index-e1a598c6.js:44 Uncaught (in promise) Error: Unknown variable dynamic import: ./lang/<unset>.json
    at index-e1a598c6.js:44:7406
    at new Promise (<anonymous>)
    at __variableDynamicImportRuntimeHelper (index-e1a598c6.js:44:7312)
    at setLanguage (index-e1a598c6.js:44:78484)
    at index-e1a598c6.js:817:112789

Luckily, it seems just to be the front end. I ended up download the vikunja desktop app.