-
Notifications
You must be signed in to change notification settings - Fork 969
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot rerun with customized certificate at 1.1.1 #36
Comments
Hi, |
After many times trying, I found something more specific: At This fails on
Weirdly, there's no problem for both The script that I do the
|
I had same issue with 1.1.1, upgrade to 1.1.2 solves the crash (
After deleting contents of both folders |
+1 on this. Recovered by manually importing LDIF's from the old cn=config and LDAP database. |
guys, i have a bad new, this probably comes from To fix this you need to manually edit /etc/ldap/slapd.d/cn=config.ldif for example in my tests i had a file like :
so i had to remove the line with the lonely I will try to fix startup.sh asap :) |
My cn=config.ldif file had:
but removing the
|
I had the problem of the corrupt cn=config.ldif file, so I went in and manually removed the bad line as described, but now I'm getting the same issue as @drebes:
I also noticed that I had |
Still not solved ? What happe if a cert name is "wildcard.domain.com.crt" ? |
-- edit : didn't read answer from osixia. My bad. I had the problem today, as a simple workaround, use short filenames, like cert.key or cert.crt, which is within ldif max line length boundaries. |
Hi @osixia, can we know if the long name certificate issue is solved? I am willing to use long name and I am not sure if it is gonna break everything. Thanks in advance, |
Hi,
After moving to 1.1.1, I cannot rerun a container with my own certificate as I did on 1.1.0. I've also tried this on a newly created container (empty, with default settings) and it failed. There's no problem rerunning one with the default certificate though.
The text was updated successfully, but these errors were encountered: