Hello,

I am in desperate need for some help involving SSL and web host manager. Here's the story:

I was finally able to setup SSL on my main domain about 2 months ago (editing httpd.conf, etc). Everything was working fine, untill this morning, when I added another user to WHM. After that, I started getting these "Could not connect" messages in my browser. So I figured out that apache was down, and would not restart. So, I went through and figured out (I think) that when I added the new user, I gave him the IP address that I was using as the secure server. So, I commented out the SSL virtual host, and restarted apache. Now I no longer get the "Could not connect" messages, but I don't have SSL anymore either.

Here's the weird part. Now, when I try to change the IP address used with the SSL, I get errors when trying to restart apache. I'm getting "unknown command on line 1440 - SSLVerify. " (or something like that).

So... I am in desperate need of some help here, and am willing to pay someone to setup the SSL. It should be REALLY easy (I'm probably just missing something stupid) So please contact me if you are interested!

Thanks,
Matt Pope
matt71123@home.com

Contact me

herps@ewsnl.com

I might be able to help

If there is anyone with experience working with WHM, it would be great, as I think this may be a WHM problem.

Thanks,
Matt

Make sure it's listening to port 443. Also, in place of start, restart or graceful, try "startssl" while in a shell session. Just ignore WHM for now and see if that works. Likely, the reason why it stopped working before, was beecause you didn't have the "NameVirtualHost ip_here:portnumber_here" directive for both 80 or 443 and it was confused. Also, run configtest in place of "start" to see what it outputs, without actually trying to start it.

Thanx for the help
but I solved his problem already :stickout

Thanks though

So how did you solved it?

Yes, Leslie from ewsnl.com fixed it for me (and for free I might add :) ). So, thanks Eagle for your help.

Tim - I actually tried that startssl thing (I read an earlier post that suggested to do this). I think it helped, and I would suggest anyone with this problem to try that. I did have the <virtualhost ip:port> for both, but I think one of them had the wrong IP. (or something) :rolleyes:

Anyways, thanks everyone for you help!

Matt Pope

No problem mate,
I'm happy I could solve your problem