I would test the certs on a apache web server and check that they
work. There is plenty of logging and documentation to work with.
Also have you tried with a web browser to access port 8443. That might
provide some debugging insight.
Oh and also check DNS. You need to have A and PTR records set
correctly for your server.
---Guy
(via iPhone)
On 5 Jan 2010, at 12:43, Mark Nipper <ni...@bitgnome.net> wrote:
I'm wondering if anyone else is seeing problems with SSL
working? I can connect fine via HTTP to the default test port of
8008. But trying to connect to 8443 in a browser gives me
repeated "connection reset" or "connection was interrupted"
errors.
I've tried using the certificate and key which come via
the subversion checkout, the default Debian snakeoil certificate
and key, and a valid, CA signed certificate (and corresponding
key). I've tried with both the downloaded version of PyOpenSSL
and the system installed version of python-openssl in Debian.
All of these combinations yield the same results.
Is there a good way to enable some kind of debugging
related to the HTTPS server? I've tried changing info to debug
in my configuration file, but this doesn't really yield any
additional information.
--
Mark Nipper
ni...@bitgnome.net (XMPP)
+1 979 575 3193
-
"A good traveller has no fixed plans and is not intent on
arriving."
-- Lao Tzu (570-490 BC)
_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
