hi Jean,
thanks for your answer.
i did stop greenlight with docker compose down.
then rsync or scp the folder with all files and the db and so on.
(both do not work as it seems)
on the other side changed the save host in .env to the new
hostname
and started gl with docker compose up.
I am thankful for any hint where the error might be that I am overseeing. ;-)
cheers
Martin
--
You received this message because you are subscribed to the Google Groups "bigbluebutton-greenlight" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-gree...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-greenlight/71d3069c-047b-497e-a0bd-0fd69ed20f57n%40googlegroups.com.
Thanks for your answer.
I already posted the complete logs I get on the login attempt.
Greenlight does work normally just the ldap does not authenticate. It just gives "email or password wrong"
I can request the users from the rails console without any problems.
Or even list their rooms via the rails console.
as the db works I do not see what it should help to dump it again. The ldap auth does not need the db at all, does it?
If noone has further ideas I might set up a new greenlight v2 and try ldap out there ... but as it loads the container on startup I can't see where the difference should be ...
thanks
Martin
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-greenlight/2a4df98c-f01c-41e2-9678-d4b78df0717dn%40googlegroups.com.
did start a clean greenlight (only copied the .env settings that are correct)
starts up and gives the same "wrong user or password" on ldap auth.
wtf ...
I really have no idea what I might do wrong here.
:-(
Martin
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-greenlight/9ada44a4-42f8-4fae-9366-122b324a59bd%40mtsonline.at.
ok got it.
the newer docker version needed '' arround the values in the .env file
because of that the ldap bind password was not correctly set.
i don't understand why greenlight cannot give an error on that - instead it gives the error, that hints to wrong user data.
anyway, as gl v2 is no longer supported this won't be fixed anymore ;-)
if someone still has to use gl v2 and ends in this problem, that was the solution.
best
Martin
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-greenlight/9bd10c07-8b80-4967-a165-228c16eb6d2d%40mtsonline.at.
Jean,
thanks for your reply.
the logs are from the greenlight-v2 container and this was the output during the login attempt.
this is exactly what I am missing, that this gl-v2 container outputs some logs regarding the failed ldap bind (of course caused by an docker error, due to non quotet values - so not caused by greenlight itself, but should be noticed by it)
in the logs you see, that gl is not giving any logging regarding the ldap bind or auth. That made investigating of the issue very hard ;-)
anyway, as gl v2 is not supported anymore and ldap was not included in v3 - nothing to solve here I guess :-)
but if someone hits the problem the solution should be found here ... always - of course - caused by an update of docker version at the same time of moving gl to another host.
thanks for trying to help!
best
Martin
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-greenlight/b9e820cc-bb2e-48f0-898c-3de430bf60ean%40googlegroups.com.