Unable to login to app after update to 6.0
-
@robi I know, as I said in my original message I don't really care about the problem for this app. But as a developper myself, i know how this kind of problem can sometimes be the tip of the iceberg of a more profound issue, and when it's hard to reproduce it's really a pain in the a** to debug ^^ So this is more of a report so they can investigate if they want, and I can give them access to an instance that has the issue in question and run tests & stuff
-
Could you lay in any more detail about the LDAP libraries you're trying to use in that code? My custom LDAP stuff in Ruby via OmniAuth-LDAP has been fine, at least, but particularities of certain libraries/versions could be the issue, I suppose. I've seen things down to capitalization become issues for LDAP-handling code depending on how much work whatever's in the middle is/isn't doing.
-
@jimcavoli I can do you one better https://git.cloudron.io/mehdi/orthanc/-/blob/master/server/ldap.js
I am 100% sure this code works. It worked in this app before the update, it works right now in another instance of the app I just installed, it worked before and still works in other custom apps.
-
@robi said in Unable to login to app after update to 6.0:
but that shouldn't matter as the update doesn't touch Apps afaik, but box code.
true, updating cloudron doesn't touch the apps, but they're all getting reconfigured after the update, maybe that's what's missing with the stopped app. @mehdi did you try reconfiguring it?
-
In Cloudron 6, we had reworked the IP address allocation and one possibly might have been that some networking issue. But this is rule out since
ldapsearch
works.What you can do quickly to debug is edit this file, https://git.cloudron.io/cloudron/box/-/blob/master/src/ldap.js#L455 and console.log (don't use debug() because they are disabled for that file) the username and password and
systemctl restart box
. Is it correct? -