httpd -startssl ./httpd: invalid option -- s

[Thanatos]

Is this a distro specific thing?

I'm trying to get my https:// working on my server with openSSL, and I'm following directions on http://www.linuxsecurity.com/feature_stories/feature_story-67.html
and when I get to this point, every time I type that in it gives me the -s invalid option thing. How do I fix this, any suggestions??? Thanks!

[Thanatos]

oh, and mandrake 9.0, apache 1.3.26, not sure of openSSL version but it came installed on drake 9.0

[Uncle Nancy]

Have you tried /usr/sbin/apachectl startssl ?

[z0mbix]

Didn't mrBen reply to this a few days ago in another post?

short command line arguments in GNU/Linux have one hyphen, where long arguments have two hyphens. e.g:

-h

or

--help

Try --startssl

[Thanatos]

If he did, I didn't see it-- TRUST ME, I searched as best I could.... :) lemme try those things!

[Thanatos]

Sadly, none of the above worked. I haven't checked the mandrake site to see if they have anything on this...I'll report back and let you guys know what I find! :)

[zoniguana]

I've checked to see that mod_ssl is there. Apache knows about mod_ssl.

When I type in apachectl startssl, I get a usage error, and startssl is not in the list of options. So, I'm wondering is I installed the RPM correctly, or if there is some other switch I need to throw, lever I need to pull, scotch I need to drink, or what... The third option would, of course, be the most pleasurable to me, but, I don't think it affects https.

Any word on the first two?

Mandrake 8.2 (planning an upgrade to 9.0, tonight)
Apache 1.3.23
OpenSSL 0.9.6c
mod_ssl 2.8.7

[zoniguana]

Here's where it gets weird...
eth0 has IP .13
eth0:1 has IP .18

The SSL is on .18
If I ping the SSLed domain from that specific machine, I get a reply from .18. This would indicate to me that Apache knows what IP it is supposed to be on.
If I ping the SSLed domain from any other machine, I get a reply from .13.

If I go to http://ssled domain, I get the most recently added name-based virtual domain.
If I go to https://ssled domain, I get "cannot be found."
If I go to http://.18, I get the default site on .13.
If I go to https://.18, I get cannot be found.
If I go to http://ssled domain:443, I get site cannot be found

Anybody else confused yet?
I type in as root "apachectl startssl", and I get a response for apachectl usage, with no option for startssl.

I look up system information, asking Apache what it knows about, and it shows mod_ssl. This *should* mean that I have access to the startssl option for apachectl, but that blows up.

If I start apache normally (apachectl start), it screams about the first SSL-related line in the SSLed domain directive.

So, at this point, I am wondering if the mod_ssl was correctly added, and whether or not Apache *really* knows how to serve up anything on :443. Can anybody confirm?