Skip to main content
3-Newcomer
August 16, 2024
Question

KepServerEX v6.1 to Thingworx v9.3 could not initialize a secure socket connection

  • August 16, 2024
  • 1 reply
  • 1416 views

I'm having problems connecting KepserverEX v6.1 to Thingworx v9.3

 

I can confirm that the pc that kepware is installed on can see the Thingworx server (I'm able to access composer and port query confirms port 443 is open). Thingworx’s Industrial Thing’s Base Thing Template is set to “IndustrialGateway” and the appkey is correct. I have also tried both Host name and IP of the server.

 

This issue is effecting 2x clients both running kepserver v6.1, the reason for the low version number is that both clients were setup 5 years ago to run an Etch line and Penetrant line and we are only now wanting to connect them to Thingworx. Unfortunatly the OEM who did the initial install has gone bust so I'm unable to raise suport ticket via them

1 reply

24-Ruby III
August 17, 2024

Similar discussions:

13-Aquamarine
August 21, 2024

@ChrisR_456 

 

Kepware has the following knowledge base article on the topic:

 

Article - CS395328 - Connection to ThingWorx failed.| Platform = <domain:port>/Thingworx/WS, error = could not initialize a secure socket connection when trying to connect to ThingWorx using PTC Kepware Products

 

If there waw 404 error code in the event log, then the following article would apply:

 

Article - CS334669 - Kepware can't connect to ThingWorx Platform with error: twWs_Connect: Error initializing web socket. Response code: 404 in KEPServerEX / ThingWorx Industrial Connectivity / Kepware (ptc.com)

 

There have been many changes to the product since the v6.1 release to help mitigate the socket connection issue. If you are unable to perform the recommended upgrade, I recommend opening a support ticket with the Kepware team to troubleshoot further. Here is a link to the login page where ticket can be opened:

 

Log In | My Kepware

 

Thanks,

*Chris 

3-Newcomer
August 28, 2024

Hi Chris

Unfortunately while the first article does produce a websocket error it is not a 404 error;

 

"error: could not establish websocket connection."

 

I've not had any luck finding a solution with articals related to this^ error either. I'll look to raising a ticket with a different licence key.

 

Thanks both for your help,

Chris