Bug: Checking "SSL" does not enble SSL for the site

Hello,

I have ISPConfig 3.0.2 setup on Debian Lenny using the "Perfect setup" howto-forge docs (and I have upgraded it to 3.0.2.1).

I have a web site, working fine, it's on a secondary IP address and no other site is on that IP (and it is not marked as a name based vhost IP). It's working correctly.

We decided we needed to have an SSL on it so as the admin user, I sent to the site's settings, and checkd the box "SSL". Clicked save, and waited quite a while, but the apache config files have not changed - the site is not listening on 443, it's still set to :80 and there's no apache SSL Directives in the config file for this vhost.

I was able to generate the keys in the ISP config interface and it looks like they were made correctly. But the site is not configured to use them.

Isn't this a bug? What am I supposed to do to fix or work around this?
I can edit the vhost file by hand but I'm afraid that will break thing. Also, some of my clients don't have the technical skills to do manual configuration - I need them to be able to click the button and have it work.

Please advise.

Thanks,

JW

 

I've done some testing and discovered that even a brand new site does not get configured in apache for SSL when the SSL box is checked from the beginning?

Am I missing something?

What is the correct way to setup an SSL website in ISPConfig 3?

 

Same Problem Here

I'm using 3.0.2.1 and it's the same issue. It does not do anything checking the SSl option.
Create Certificate does create it, but it never changes the Vhost configuration to use the certificate file.

 

Till: You said "You just missed to create a ssl cert, without a ssl cert, the website can not be configured for ssl of course or apache will stop."

Ah but I did make an ssl cert - I setup test sites and tried making (creating) the certs both before and after, and neither way works. Now that I have a cert made I can turn the SSL checkbox on and off and it makes no difference.

Till also said "First, make sure that you selected a dedicated IP address for this website ind not * as SSl does not work with *."

Yes, I did do that. It is a dedicated IP, it is setup properly on the host OS, it is setup ("added") in ISPconfig, and it it NOT marked as a NameBasedVirtualHost IP.

Till also said: "Then after you enabled ssl for the website, go to the ssl tab, enter the details for the ssl cert and select "create" as action. Then after 1 - 2 minutes, the website will be enabled for ssl."

But I have done exactly that, also I tried doing it in reverse order. Tried it multiple times, took it off and put it back on, tried a whole separate site on another IP, waited many minutes between each "change" and still SSL is never enabled.

charlesrg said:
"Same Problem Here
I'm using 3.0.2.1 and it's the same issue. It does not do anything checking the SSl option.
Create Certificate does create it, but it never changes the Vhost configuration to use the certificate file. "

Exactly, that's how it is for me.

Till - if there's some information I am missing that you want to know, please tell me. But I have done all the things you suggested, as best I can tell, and it is not working.

Thanks,

JW

 

I am having the same issue. but my certs are the same as my site is named. I even did the fix for it. The issue is when i check the SSL box they vhost file is never changed it only still lists just port 80. Apache does not even have a port 443 listed for listening. any and all help is appreciated i need to get SSL going on this one site for the shopping cart.