openvpn-connect-1.8.3.347 :unable to obtain session id from

barun

Hi

I have successfully installed OpenVPN Access Server with 2 nos of free clients under CentOS 6.3 . The ip address of the server is :10.1.10.123 . When I try to connect to the assess server from any client using openvpn-connect-1.8.3.347 , the following error occurs :

10.1.10.123 disconnected

unable to obtain session ID from 10.1.10.123 , ports=443: XML-RPC:Other SSL errors:[('SSLroutines','SSL23_READ','ssl handshake failure')]

. The Access Server web UIs are working fine .

Admin UI : https://10.1.10.123:943/admin

Client UI : https://10.1.10.123:943/

Pls help .

regards

barun

barun

Hi

Can any one help me in resolving this openvpn-connect issue ..

regards

barun

barun

Hi

Pls help me in resolving the issue of OpenVPN connect .

When I try to connect to the assess server from any client using openvpn-connect-1.8.3.347 , the following error occurs :

10.1.10.123 disconnected

unable to obtain session ID from 10.1.10.123 , ports=443: XML-RPC:Other SSL errors:[('SSLroutines','SSL23_READ','ssl handshake failure')]

. The Access Server web UIs are working fine .

Admin UI : https://10.1.10.123:943/admin

Client UI : https://10.1.10.123:943/

pls help

regards

barun

elite_technical

Hi Barun

This is also affecting myself. at the moment i cannot find a fix. please can you advise if you ware having the same issue?

Thanks, Usman

CP

I'm having the same problem, everything works perfectly at home and I get the following error message at work:

<IP> disconnected
Unable to obtain Session ID from u'<IP>'; port(s)=443; XML-RPC: ('302', 'Moved Temporarily')
ovpntray.ex

The Johan

From the 302 response it's obvious to me that the web services of your Access Server cannot be reached at the address you have configured, but instead you reach some other web service that doesn't know what to do with the communication requests from the OpenVPN Connect Client and apparently is configured to redirect you to some other page, probably the home page of the website running on this web service. In any case, it doesn't look like you're talking to your Access Server, and so it fails.

2 options:
- Fix your shit so the actual web services of the Access Server are reachable at the address and port mentioned in the error message from this client system.
- Remove the server-locked profile from your Connect Client and replace it with either a user-locked profile or an auto-login profile. Both of those types do not need the web services for a connection.

blokeontheend

I was able to connect after entering the admin page and selecting the User Permissions tab, then checking the box for "Allow Auto-Login". In your case: https://10.1.10.123:943/admin/user_permissions