Forum

Hello Hugo,

I need help regarding installing my SSL certificate in hiawatha.

I currently have an .pem file named /etc/hiawatha/ssl.pem, in /etc/hiawatha/hiawatha.conf - the following is configured:

Binding {
        Port = 443
        SSLcertFile = /etc/hiawatha/ssl.pem
}

My /etc/hiawatha/ssl.pem looks like:

-----BEGIN RSA PRIVATE KEY-----
Private certificate
-----END RSA PRIVATE KEY-----

-----BEGIN CERTIFICATE-----
Public certificate
-----END CERTIFICATE----

-----BEGIN CERTIFICATE-----
CA certificate
-----END CERTIFICATE-----

So, now when I restart hiawatha, hiawatha just shuts down and trys(?) to start, it doesnt start (hangs up).

Hiawatha version: 8.6
Operating System: Debian Squeeze 6 - AMD64

Have you an idea regarding the problem?

Thanks - Debi@n

Please, follow these instructions.

Hi Hugo,

i forced this check and i only see this in the output file:

==21573== Memcheck, a memory error detector
==21573== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==21573== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for copyright info
==21573== Command: /usr/sbin/hiawatha -d
==21573==

The check now runs 10 minutes, it cant be normal..

In that case, edit src/libssl.c and set ENABLE_DEBUG_LEVEL to 6 and recompile Hiawatha. Don't run it via valgrind. When it crashes again, send me the output of /var/log/hiawatha/system.log. That one should contain a log of PolarSSL debug lines.

Don't use Hiawatha with ENABLE_DEBUG_LEVEL set to 6 for production servers. It will produce a VERY large debug logfile.

Hi Hugo,

it was just not a bug of hiawatha, the company where I buyed my SSL certificate forgot an string in the endline of an certificate, now it runs very good!

Thank you for your time, Debi@an

Well, I still consider it a bug, because Hiawatha should have reported about a misformed certificate instead of crashing. At least now we know where it came from. I'll take a look at it. Thanks for reporting.