Open joshoram80 opened 1 year ago
Hi. NO_HTTPS=true
will definitely prevent the certs from being generated and/or being used. There's a simple if
clause in the entrypoint script that manages this: https://github.com/wheelybird/ldap-user-manager/blob/40ec4a151c8451f5d56f007d817206862d0f4279/entrypoint#L35
I can't recreate your issue, so I imagine that for some reason NO_HTTPS
isn't being passed into the container. Perhaps try removing the quotes around true
in the environment:
section? Or alternatively try passing in the env values as a dictionary (https://docs.docker.com/compose/compose-file/compose-file-v3/#environment), e.g.:
environment:
- SERVER_HOSTNAME: 'https://lum.my.domain'
- LDAP_URI: 'ldap://openldap'
- NO_HTTPS: 'true'
What's stranger is that the cert generation is failing. Perhaps there are files already in the $DOCKERDIR/appdata/lum/opt/ssl
causing issues? If you're not planning to use SSL within the container then you might as well remove the volume mount.
Hope that helps.
The main problem is the way docker compose handles the format:
environment:
- NO_HTTPS="true"
Which will set the variable to literally "true" and not true (without the quotes)
The correct way to set this variable is:
environment:
- NO_HTTPS=true
Running LUM from latest Docker image, behind Traefik.
My error logs are showing
I'm not sure why LUM is trying to generate certificates to begin with as NO_HTTPS=true should prevent it? I already has Traefik setup to get certificates from LetEncrypt which it does, and the entire domain is behind Cloudflare. Could this be the issue?
As far as I can tell, my OpenLDAP container is running correctly