Submitted by izoox on Fri, 12/10/2010 - 12:55
I am not sure where the issues lies with this situation. I have installed an SSL using the virtualmin manage ssl page. I then copied the ssl to webmin and it works perfectly. However the ssl is not recognized by apache. The SSL is a wildcard ssl now, but before that I had a normal ssl installed, and it still didn't work correctly in Apache. The domains that have issues all follow this example: shared1-west.izoox.net. Do you think the '-' could be the problem. If so, is there a solution?
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Fri, 12/10/2010 - 13:04 Comment #1
The dash shouldn't be an issue.
What do you mean by the cert is not recognized by Apache exactly? What error message are you getting?
Submitted by izoox on Fri, 12/10/2010 - 13:38 Comment #2
When I visit the secure site in apache it looks like it is pulling some self signed cert. But the cert that I copied using the copy to webmin button works great in virtualmin.
Submitted by JamieCameron on Fri, 12/10/2010 - 13:57 Comment #3
Do you have a separate IP address for each of your domains that are using SSL?
Submitted by izoox on Fri, 12/10/2010 - 15:06 Comment #4
Well this is the only domain on that IP that has an ssl. Does it have to have a completely separate ip?
Submitted by JamieCameron on Fri, 12/10/2010 - 15:19 Comment #5
No, it is OK as long as there is only one SSL domain per IP.
What is the actual domain name in question? I'd like to try connecting to it myself ..
Submitted by izoox on Fri, 12/10/2010 - 15:37 Comment #6
An example one is https://shared1-west.izoox.net/webmail/
If you go to https://shared1-west.izoox.net:10000 you'll see what the ssl is supposed to show as.
Submitted by JamieCameron on Fri, 12/10/2010 - 15:44 Comment #7
Looks like apache is still using the self-signed cert. Perhaps apache needs to be restarted?
I'd have to login to your system myself to see what is going wrong here.
Submitted by izoox on Fri, 12/10/2010 - 15:54 Comment #8
I just sent remote login privileges.
Submitted by JamieCameron on Fri, 12/10/2010 - 17:39 Comment #9
Thanks .. I fixed the problem. For reasons totally unknown to me, Apache was using the SSL cert defined in /etc/httpd/conf.d/ssl.conf , and not the cert for your domain!! I commented out the SSL directives from that file, restarted Apache, and it is OK.
I suspect this is a side-effect of having an SSL website on the default shared IP.
Submitted by izoox on Fri, 12/10/2010 - 17:53 Comment #10
Weird, so it's likely a bug in Apache?
Submitted by JamieCameron on Fri, 12/10/2010 - 17:56 Comment #11
Maybe .. or a lack of understanding of how Apache SSL works on my part.
Submitted by izoox on Fri, 12/10/2010 - 18:00 Comment #12
Ha, I'm not sure how likely that is. You are the man. It definitely did it on all my servers that I have setup like this.
Submitted by Issues on Fri, 12/24/2010 - 18:04 Comment #13
Automatically closed -- issue fixed for 2 weeks with no activity.