easyapache broke mod_ssl????

[pagedeveloping]

Hello,

I am having a bit of a hard time since I updated through easyapache. For starters it took me several tries to get apache up and running and I do mean several. This was a normal routine that turned into a night mare. I had to install each model on by one to get all the models I needed up and running but one mod seems to give me errors on the config check.

Here is the following error I get..

Syntax error on line 1385 of /usr/local/apache/conf/httpd.conf:
Invalid command 'SSLEnable', perhaps mis-spelled or defined by a module not included in the server configuration

mod_ssl uses this command and I never had any problems with it in the past. Although my sites are up and running fine I do have a problem with one of them.

when you click on a link inside this ssl enabled web site it brings up the cert for tht web site. and yes this happens to all people from all parts of the world. You have to click on the cert. several times to get to the next page.

here's the funny part. when I resart apache it goes away for the day and continues the next morning untill I restart apache again.


Do I have a broken mod_ssl? does any have a clue on how I can go about fixing this without the headache of running easyapache again.

Thank you for taking the time and reading into my problem here.

Peter

 

[AndyReed]

Syntax error on line 1385 of /usr/local/apache/conf/httpd.conf:
Invalid command 'SSLEnable', perhaps mis-spelled or defined by a module not included in the server configuration

Make sure that the SSL directives/syntax for every account with SSL cert is correct. I am referring to:

<IfDefine SSL>
<VirtualHost xx.xx.xx.xx:443>

BLAH BLAH
BLAH BLAH
BLAH BLAH

</VirtualHost>
</IfDefine>

Use Verbose mode to make sure that apache was compiled successfully, without errors.

 

[pagedeveloping]

Make sure that the SSL directives/syntax for every account with SSL cert is correct. I am referring to:

<IfDefine SSL>
<VirtualHost xx.xx.xx.xx:443>

BLAH BLAH
BLAH BLAH
BLAH BLAH

</VirtualHost>
</IfDefine>

Use Verbose mode to make sure that apache was compiled successfully, without errors.

Thanks for your reply..

I always check verbose mode to be on the safe side because php likes to fool you that it is compiling without problems if you don't.

verbose mode showd no errors and I checked it over a few times.

My directives are correct and I even compared them to my backup config and all seems to be in place. I have even removed the mods from my backup that I don't use now in the new and still get the same errors when I try to use it.

It puzzles me because I never had this problem untill I did this night mare update.

I have searched all the engines on this and not one person had any similar problems.

 

[pagedeveloping]

Well after doing another extensive envestigation on this i found that apache had insterted new lines such as NameVirtualHost ipaddress:443 including lines with :80 i had reamoved them and the errors went away. Now I am waiting to see tomorrow morning if it gives me any problems with the ssl web site.

thank you..

 

[AndyReed]

i found that apache had insterted new lines such as NameVirtualHost ipaddress:443 including lines with :80 i had reamoved them and the errors went away.

Did this happen after you re-compiled Apache? Are you checking the log files for errors? There are a few more procedurs to trace and fix this problem.

 

[felosi]

same here, gonna try and find an old config

UPDATE added the addmodule sdsl from an old config , seems like it worked a minuite then it didnt. I dont know whats up with it

UPDATE: got it where it dont give no errors, it just doesnt put the enablessl lines in conf. I had them in there once and it deleted them

UPDATE yet again, added the lines manually, working for now, installed another host. Lets hope it stays working


eww, it deleted the ssl lines from conf and didnt add the lines for the new host, like its overwriting the config or something each time

I give up