SSL with Dedicated IP (Page Not Found)

zelf

Active Member
Dec 6, 2005
30
0
156
I've added a dedicated IP for a FQDN through WHM. nslookup confirms that this FQDN is pointing to my added IP. Typing in the FQDN using http:// shows also that it is pointing to my server. However, typing in the FQDN using https:// returns page not found.

I have installed the ssl crt, key through WHM and the FQDN is listed as an SSL Host in WHM. In httpd.conf I have the following, which all looks correct. What step have I missed for setting up a dedicated ip ssl through WHM? I've gone over it a 100 times and all seems exactly as it should be. Except for the dedicated IP it looks exactly the same as my shared ssl cert, which is working great. First time setting up dedicated ip ssl. Any ideas???
Code:
<IfDefine SSL>
<VirtualHost xx.xx.xx.xxx:443>
ServerAdmin [email protected]
DocumentRoot /home/mydir/public_html
ServerName my.fqdn.tld
UserDir public_html

<IfModule mod_userdir.c>
  Userdir disabled
  Userdir enabled mydir
</IfModule>

<IfModule mod_php4.c>
  php_admin_value open_basedir "/home/mydir:/usr/lib/php:/usr/local/lib/php:/tmp"
</IfModule>
<IfModule mod_php5.c>
  php_admin_value open_basedir "/home/mydir:/usr/lib/php:/usr/local/lib/php:/tmp"
</IfModule>

User myuser
Group myuser
ScriptAlias /cgi-bin/ /home/mydir/public_html/cgi-bin/

SSLEnable
SSLCertificateFile /usr/share/ssl/certs/my.fqdn.tld.crt
SSLCertificateKeyFile /usr/share/ssl/private/my.fqdn.tld.key
SSLCACertificateFile /usr/share/ssl/certs/my.fqdn.tld.cabundle
SSLLogFile /usr/local/apache/domlogs/my.fqdn.tld-ssl_data_log
CustomLog /usr/local/apache/domlogs/my.fqdn.tld-ssl_log combined
SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown
</VirtualHost>
</IfDefine>
 

chirpy

Well-Known Member
Verifed Vendor
Jun 15, 2002
13,437
33
473
Go on, have a guess
Two things to try:

1. Check the DNS entry at dnsreport.com/dnsstuff.com to make sure it has propagated

2. Stop and restart httpd - a graceful restart isn't enough usually:

httpd stop
httpd startssl
 

zelf

Active Member
Dec 6, 2005
30
0
156
chirpy said:
1. Check the DNS entry at dnsreport.com/dnsstuff.com to make sure it has propagated
Yes, it has propagated.
chirpy said:
2. Stop and restart httpd - a graceful restart isn't enough usually:

httpd stop
httpd startssl
Tried it already. Still same results. What else can I try Chirpy?
 

zelf

Active Member
Dec 6, 2005
30
0
156
Shekhar said:
May be a NameVirtualHost entry missing in the httpd.conf file for the dedicated IP
There was no NameVirtualHost for the dedicated IP. I added it xx.xx.xx.xxx:443 directly under the Shared IP and did a httpd stop httpd startssl. Everything started fine, but still times out calling the domain in a browser on https.

This is driving me insane. I've deleted the ssl host and recreated it. I've triple checked the cert and key and they are exactly what they should be, meaning the key used to create the CSR is the same as the key used to setup the SSL host and install the crt through WHM. My shared ssl cert is working perfectly. My dedicated ip cert is setup exactly the same in httpd.conf as the shared cert except for the DocRoot User and IP of course. This should be working by everything I've read. I'm at my wits end on this.

Anyone have any more ideas for me on this? I need to get this up and running like yesterday. What really ticks me off is it is not rocket science to set this up and everything looks exactly the way it should be. :(