Strangely, a client connection to a different domain (and different wordpress instance) on the same server does not produce the error and the connection is established and usable.
I found this bug report:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/861137
and it illustrates how specifying SSLv3 (or diabling TLSv1) allows client side connects to the remote service to successfully authenticate. I read the link in the python-wordpress-xmlrpc docs to specifying a custom transport to xmlrpc, but no mention of SSL or TLS are made.
A script using python-wordpress-xmlrpc started giving this error when trying to make the client connection:
SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error
Strangely, a client connection to a different domain (and different wordpress instance) on the same server does not produce the error and the connection is established and usable.
I found this bug report: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/861137 and it illustrates how specifying SSLv3 (or diabling TLSv1) allows client side connects to the remote service to successfully authenticate. I read the link in the python-wordpress-xmlrpc docs to specifying a custom transport to xmlrpc, but no mention of SSL or TLS are made.
Any ideas would be appreciated.