07-29-2004, 08:57 PM
|
|
Member
|
|
Join Date: Jun 2004
Location: Wellington, NZ
Posts: 13
|
|
one more thing...
errors that happen inside the OpenSSL libraries seem to give me this sort of thing:
Code:
2004-07-30 15:49:17.178 [DEBUG] Created new Listener [*:7080].
2004-07-30 15:49:17.178 [DEBUG] Created new Listener [*:80].
2004-07-30 15:49:17.178 [DEBUG] Created new Listener [192.168.1.29:443].
2004-07-30 15:49:17.178 [DEBUG] [SSL] Create SSL context for listener 192.168.1.29:443 with Certificate file: /mv/ssl/bnz-dev.private.marketview.co.nz.crt and Key File: /mv/app/dev/bnz/conf/priv.key.
2004-07-30 15:49:17.181 [ERROR] [SSL] Config SSL Context for listener 192.168.1.29:443 with Certificate File: /mv/ssl/bnz-dev.private.marketview.co.nz.crt and Key File:/mv/app/dev/bnz/conf/priv.key get SSL error: error:0B080074:x509 certificate routines:X509_check_private_key:key values mis
2004-07-30 15:49:17.185 [NOTICE] [AutoRestarter] child process with pid=20552 received signal=11, a core file is created!
2004-07-30 15:49:17.185 [NOTICE] [AutoRestarter] stop children processes and remove created unix sockets!
2004-07-30 15:49:17.293 [WARN] [AutoRestarter] forking too frequently, suspend for a while!
This means that when you restart the web server after changing the SSL configuration, you can be left with nothing but a "connection refused" message! Much better just to disable the listener with the fault...
Maybe you should link to a guide to making these keys from that dialog? Most users will find this tricky.
|