cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Handshake failed. Status: -260

Highlighted
Visitor

Handshake failed. Status: -260

Hi,

We managed to install a Thingworx server 8.0 but we are unable to communicate with it. This is the error:

[DEBUG] 2017-07-12 16:20:12,772 TlsStream:: doopen: Setting SO_RCVTIMEO

[ERROR] 2017-07-12 16:20:12,776 TlsStream::doopen: Handshake failed.  Status: -260. Cleaning up stale SSL session.

[ERROR] 2017-07-12 16:20:12,777 WsStream::connect: Exception while dispatching request to thingworx.local.libelium.com. Error: SSL Handshake Failed [thingworx.local.libelium.com:443]

[DEBUG] 2017-07-12 16:20:12,777 WsStream::execute: Attempting to connect to thingworx.local.libelium.com:443.

[WARN ] 2017-07-12 16:20:12,777 WsStream::execute: Connection failed.  Attempting again in 10 seconds

Any help will be appreciated.

3 REPLIES 3
Highlighted

Re: Handshake failed. Status: -260

Hello,

My understanding is that the REST API defaults to listening on localhost:8000, but that it defaults to HTTP not HTTPS.  You can enable HTTPS in config.json.  Look at the "http_server" section.

-- Craig A.

Highlighted

Re: Handshake failed. Status: -260

Hello,

Thanks for your help, but the "http_server" section is used to allow a WS EMS to accept local calls from the machine or device code that may be running in a different process, such as the Lua Script Resource:

http://support.ptc.com/help/thingworx_hc/thingworx_edge/index.html#page/twx_edge_sdks_ems_534%2Fems_...

Our problem is the connection between the EMS and the Thingworx server. If the connection is secure (insecure communication works well) the EMS is unable to communicate with Thingworx server 8.0.

Regards

Highlighted

Re: Handshake failed. Status: -260

We believe that the problem is in the configuration of the Thingworx Server.

This is the log of the web server:

[Wed Jul 12 16:20:32.728432 2017] [ssl:debug] [pid 10980:tid 139647757801216] ssl_engine_kernel.c(570): [client 192.168.3.110:51304] AH02255: Changed client verification type will force renegotiation

[Wed Jul 12 16:20:32.728445 2017] [ssl:info] [pid 10980:tid 139647757801216] [client 192.168.3.110:51304] AH02221: Requesting connection re-negotiation

[Wed Jul 12 16:20:32.728462 2017] [ssl:debug] [pid 10980:tid 139647757801216] ssl_engine_kernel.c(770): [client 192.168.3.110:51304] AH02260: Performing full renegotiation: complete handshake protocol (cli

ent does not support secure renegotiation)

[Wed Jul 12 16:20:32.728530 2017] [ssl:error] [pid 10980:tid 139647757801216] [client 192.168.3.110:51304] AH02225: Re-negotiation request failed

[Wed Jul 12 16:20:32.728608 2017] [ssl:error] [pid 10980:tid 139647757801216] SSL Library Error: error:14080152:SSL routines:SSL3_ACCEPT:unsafe legacy renegotiation disabled

And this a screenshot of the TCP trace:

Cloud.jpg

Announcements

Thingworx Navigate content has a new home! Click here to access the new Thingworx Navigate forum!