On Aug 9, 2007, Dragon (nospam-dragon@xxxxxxxxxxxxxxxxxxxxx) typed: Dragon: S.A. Birl wrote: Dragon: > Greetings all: Dragon: > Dragon: > I recently upgraded my server from Solaris 9 to Solaris 10. Dragon: > I restored my self-signed CRT and privkey.pem from backup, Dragon: > and restored all of my Apache files (minus the binaries) from Dragon: > backup too. Re-compiled httpd (just in case) and started it up. Dragon: > Dragon: > Apache asked for the passphrase and accepted it, but my web browsers Dragon: > wont connect to it. SeaMonkey says "Data Transfer Interrupted" Dragon: > Dragon: > https://concept.temple.edu/ Dragon: > Dragon: > Generating a new CSR and CRT with openssl 0.9.8e and tried again. Dragon: > Same result. Dragon: > Dragon: > Nothing in the error log; nothing in the access log, but lsof says Dragon: > httpd is listening on 443. Dragon: > Dragon: > Im baffled. What could I be over-looking? Dragon: > Dragon: > Dragon: > Thanks Dragon: > Birl Dragon: ---------------- End original message. --------------------- Dragon: Dragon: The site came up in my browser (IE7) but showed a certificate error. Dragon: The error is that the certificate is not signed by a trusted authority. Yes, that's why I said in the OP that it was "self-signed". Interesting that it came up in IE7, as I confirmed it myself. So other than it being self-signed, what other reason could there be? All my other self-signed certificates worked in the past with the same version of Apache, but an earlier version of openssl. Thanks Birl Please do not CC me responses to my own posts. I'll read the responses on the list. Archives http://mail-archives.apache.org/mod_mbox/httpd-users/ --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|