tarball
> config setprop modSSL crt /home/e-smith/ssl.crt/{domain}.crt
> config setprop modSSL key /home/e-smith/ssl.key/{domain}.key
Remember to follow the above commands with a
signal-event console-save
What happened was william_syd's post and mine "crossed in the mail," and his suggestion was there to be read by the time I posted mine above. Changing the location of the cert seemed to make sense, so I tried it on a test server here at home and it seemed to work. So, encouraged, I made a folder inside ssl.crt and ssl.key, moved the files inside them, and ran the above commands, except that I mistyped the path (first mistake). Then I ran signal-event post-upgrade ; signal-event reboot instead of your suggestion (second mostake), knocking a production server off line from home at 10pm. No one ever accused me of being a genius.
Yesterday morning (unusually early) I logged in locally and entered the correct paths and rebooted. http and https are working OK, but now that I read your subsequent post I realize that I never did do signal-event console-save.
Is it OK to do it a day later?
Also, am I correct in understanding that as long as I run those commands it is unnecessary to move the cert and key to a non-standard location? I'll move them back and rerun the commands (all of them this time) if so.
The httpd error logs are telling me that "mail.blah.blah.jp does NOT match server name!" even though that info is actually correct, so it seems that I've still got something wrong.
Thanks for the responses.
tarball