Hi Lukas, I do appologize, I made a mistake with a filename. During all my tests I created different pem files with different names and in the end I mixed up all those names and had used a file name in the config file which doesn't exist.
Now, I built all again from scratch and voila, it is working fine. That leads me to a suggestion: the error message, when the pem file doesn't exist should be different form the error message when the file exists but is corrupt. However, thanks a lot for your great support. Yours Jürgen Am Mo 08 Jul 2013 09:47:25 CEST schrieb Lukas Tribus: > Hi Jürgen, > > >> Now I'm getting the error >> >> "unable to load SSL private key from PEM file" >> >> I checked the contents of the domain1.pem file and there is the >> following order included: >> - private key >> - domain certificate >> - 2 sections from the intermediate certificates pem file > > I don't understand why this fails, this should be correct. > > Can you try with just one certificate at the time? > Please double check there are now whitespace/newline issues > in those files. > Also, run a ´grep "\-\-\-" /var/proxy/certs/domain1.pem´ against > the failing certificate, and show us the output. > > > > Regards, > > Lukas
