Hmmm, this is interesting. I played around with the settings a bit, and it
seems to work once I disable IPv6 support! Very weird, perhaps a bug of
----- Original Message -----
From: Stefan de Konink
To: Jim Isaacs
Cc: Daniel Lo Nigro ; "[email protected]"
Sent: Friday, 7 October 2011 10:18 AM
Subject: Re: [Cherokee] SSL not working - Serving plain HTTP on port 443?
Is everyone in this thread absolutely sure that:
General Settings > Ports to listen looks like:
TLS/SSL port is ticked?
On Thu, 6 Oct 2011, Jim Isaacs wrote:
> I just got this working the other day on a Fedora system, same cherokee
> So it could be with the debian package, the certificate or key, or maybe
> 2011/10/6 Daniel Lo Nigro :
>> Already did that as it's mentioned in the documentation (and I had to do
something similar when using Lighttpd). It still doesn't work. As I
mentioned, even the self-signed certificate isn't working. :(
>> ----- Original Message -----
>> From: Jędrzej Nowak
>> To: Daniel Lo Nigro
>> Cc: "[email protected]"
>> Sent: Thursday, 6 October 2011 11:46 PM
>> Subject: Re: [Cherokee] SSL not working - Serving plain HTTP on port
>> cat ssl.crt sub.class1.server.ca.pem > ssl_chained.crt
>> You need to use ssl_chained.crt as a cert file :)
>> Jędrzej Nowak
>> On Thu, Oct 6, 2011 at 2:42 PM, Daniel Lo Nigro wrote:
>>> Hi everyone,
>>> I'm trying to configure Cherokee to host a site over SSL. However, for
some reason, Cherokee is serving plain HTTP over port 443, and not HTTPS.
In other words, https://springfield.youareaninja.com/
doesn't work, but http://springfield.youareaninja.com:443/
>>> My configuration:
>>> - Cherokee 1.2.99 from the unstable Debian repository (installed on
>>> - SSL/TLS back-end set to OpenSSL/libssl
>>> - Port 443 added as a port, and "TLS/SSL port" ticked
>>> - Certificate and certificate key specified in vserver Security tab
>>> This server only has one virtual host, the default host. I initially
tried with a StartSSL certificate, but I tried "Tasks -> SSL/TLS testing"
in rule management and it has the same issue. At the moment, it's set to
use the self-signed certificate.
>>> Any suggestions or ideas?
>>> Cherokee mailing list
>>> [email protected]
>> Cherokee mailing list
>> [email protected]
> Cherokee mailing list
> [email protected]
Cherokee mailing list