Can't connect to "https://academic-thingworxconnectivity.portal.ptc.io" with EMS


#1

I’m try to connect EMS on my Thingworx Instance (academic-thingworxconnectivity.portal.ptc.io). I’ve got this error:


C:\EMS\microserver>wsems
[FORCE] 2018-05-23 08:10:13,527 wsems: Initializing EMS …
[FORCE] 2018-05-23 08:10:13,527 main: Using config file C:\EMS\microserver\etc\config.json
[ERROR] 2018-05-23 08:10:13,527 Main: Failed to get HTTP Server ssl configuration.
[FORCE] 2018-05-23 08:10:13,527 Main: Exiting…


Here is the config.json file used for this topics:


{
“ws_servers”: [{
“host”: “academic-thingworxconnectivity.portal.ptc.io”,
“port”: 443
}],
“appKey”: “8e84bee2-e4e1-4757-9452-964c6dd5909a”,
“certificates”: {
“validate”: false,
“cert_chain”: [“certificate.cer”]
}
}


This config.json file are located in: C:\EMS\microserver\etc


#2

Here is the log file with TRACE info:

[FORCE] 2018-05-23 08:44:07,5 wsems: Initializing EMS …
[FORCE] 2018-05-23 08:44:07,5 main: Using config file C:\EMS\microserver\etc\config.json
[INFO ] 2018-05-23 08:44:07,5 wsems: Creating the WsEms proxy.
[INFO ] 2018-05-23 08:44:07,5 wsems: Starting HTTP Server.
[INFO ] 2018-05-23 08:44:07,5 Main: Using custom certificate and private key for HTTP Server
[ERROR] 2018-05-23 08:44:07,5 Main: Failed to get HTTP Server ssl configuration.
[FORCE] 2018-05-23 08:44:07,5 Main: Exiting…
[FORCE] 2018-05-23 08:46:48,109 wsems: Initializing EMS …
[FORCE] 2018-05-23 08:46:48,109 main: Using config file C:\EMS\microserver\etc\config.json
[ERROR] 2018-05-23 08:46:48,109 Main: Failed to get HTTP Server ssl configuration.
[FORCE] 2018-05-23 08:46:48,109 Main: Exiting…
[FORCE] 2018-05-23 08:47:20,881 wsems: Initializing EMS …
[FORCE] 2018-05-23 08:47:20,881 main: Using config file C:\EMS\microserver\etc\config.json
[INFO ] 2018-05-23 08:47:20,881 wsems: Creating the WsEms proxy.
[INFO ] 2018-05-23 08:47:20,881 wsems: Starting HTTP Server.
[INFO ] 2018-05-23 08:47:20,881 Main: Using custom certificate and private key for HTTP Server
[ERROR] 2018-05-23 08:47:20,881 Main: Failed to get HTTP Server ssl configuration.
[FORCE] 2018-05-23 08:47:20,881 Main: Exiting…
[FORCE] 2018-05-23 08:55:36,901 wsems: Initializing EMS …
[FORCE] 2018-05-23 08:55:36,901 main: Using config file C:\EMS\microserver\etc\config.json
[INFO ] 2018-05-23 08:55:36,901 wsems: Creating the WsEms proxy.
[INFO ] 2018-05-23 08:55:36,901 wsems: Starting HTTP Server.
[INFO ] 2018-05-23 08:55:36,901 Main: Using custom certificate and private key for HTTP Server
[ERROR] 2018-05-23 08:55:36,901 Main: Failed to get HTTP Server ssl configuration.
[FORCE] 2018-05-23 08:55:36,901 Main: Exiting…
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getString: Key = audit_target, Parent = logger
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getValueByType: Key audit_target not found
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getString: Key = publish_directory, Parent = logger
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getUnsignedInteger: Key = max_file_storage, Parent = logger
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getString: Key = publish_level, Parent = logger
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getBoolean: Key = auto_flush, Parent = logger
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getUnsignedInteger: Key = buffer_size, Parent = logger
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getUnsignedInteger: Key = flush_chunk_size, Parent = logger
[FORCE] 2018-05-23 08:58:58,477 wsems: Initializing EMS …
[FORCE] 2018-05-23 08:58:58,477 main: Using config file C:\EMS\microserver\etc\config.json
[INFO ] 2018-05-23 08:58:58,477 wsems: Creating the WsEms proxy.
[TRACE] 2018-05-23 08:58:58,477 wsEmsProxy::wsEmsProxy: Constructor called
[INFO ] 2018-05-23 08:58:58,477 wsems: Starting HTTP Server.
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getInteger: Key = port, Parent = http_server
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getValueByType: Parent http_server not found
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getString: Key = host, Parent = http_server
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getValueByType: Parent http_server not found
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getInteger: Key = ports_to_try, Parent = http_server
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getValueByType: Parent http_server not found
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getInteger: Key = max_clients, Parent = http_server
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getValueByType: Parent http_server not found
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getBoolean: Key = use_default_certificate, Parent = http_server
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getValueByType: Parent http_server not found
[INFO ] 2018-05-23 08:58:58,477 Main: Using custom certificate and private key for HTTP Server
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getBoolean: Key = ssl, Parent = http_server
[TRACE] 2018-05-23 08:58:58,477 jsonConfigurator::getValueByType: Parent http_server not found
[ERROR] 2018-05-23 08:58:58,477 Main: Failed to get HTTP Server ssl configuration.
[FORCE] 2018-05-23 08:58:58,477 Main: Exiting…
[DEBUG] 2018-05-23 08:58:58,477 jsonConfigurator::~jsonConfigurator: Deleting JSON object
[TRACE] 2018-05-23 08:58:58,477 wsEmsProxy::~wsEmsProxy: Destructor called
[TRACE] 2018-05-23 08:58:58,477 WsProxy::~WsProxy: Deleting Thing binding list


#3

Hello @h014,

We are currently having issues with the ThingWorx server:

The IoT University platform is currently experiencing an internal issue with our ThingWorx instance. This is affecting the following courses:

• Fundamentals of IoT Development with ThingWorx
• IoT UI Development with ThingWorx
• IoT Connectivity with ThingWorx
• Capstone: ThingWorx IoT Developer Specialization

We are working on getting this resolved as soon as possible. We apologize and appreciate your patience. We anticipate this issue will be resolved on Tuesday, 5/29.

Sorry for the inconvenience!


#4

Hi Admin,

I almost have as similar problem. Here is the error that I am getting
C:\EMS\microserver>wsems
[INFO ] 2018-12-30 21:35:09,39 wsems: Using config file: C:\EMS\microserver\etc\config.json
[FORCE] 2018-12-30 21:35:09,39 wsems: Starting up …
[ERROR] 2018-12-30 21:35:09,55 wsems: Unable to find any configuration file in C:\EMS\microserver\etc


#5

Hi Admin,

I can not connect to the thingworx platform either, I am using the Win version of ems.
Here is the error info:

[FORCE] 2019-07-12 11:07:20,177 httpServer: starting http server port=8000
[ERROR] 2019-07-12 11:07:20,192 SDK: twWs_Create: Error creating BSD socket to be used for the websocket
[ERROR] 2019-07-12 11:07:20,192 SDK: twApi_Initialize: Error creating websocket structure, retrying

And the config file:
{
“ws_servers”: [
{
“host”: “ptcu-thingworx72p-connectivity.portal.ptc.io”,
“port”: 443
}
],
“appKey”: “3c575305-eb10-404c-801a-5f3c95ab3202”,
“certificates”: {
“validate”: false,
“cert_chain”: [
“certificate.cer”
]
}
}


#6

I have the same problem.

SDK: twWs_Create: Error creating BSD socket to be used for the websocket
SDK: twApi_Initialize: Error creating websocket structure, retrying

Any new idea?


#7

Same here, BSD/websocket error. Not sure how to resolve. If I find something I’ll let you guys know.


#8

Just figured it out - there appear to be 2 options, change either one of these lines and it will work:

“validate”: false, -> “validate”: true,

or

“allow_self_signed”: false, -> “allow_self_signed”: true,

Seems to work for me.


#9

Just figured it out - there appear to be 2 options, change either one of these lines and it will work:

“validate”: false, -> “validate”: true,

or

“allow_self_signed”: false, -> “allow_self_signed”: true,

Seems to work for me.


#10

Worked for me…

\\

“validate”: false, -> “validate”: true,

\\

Did the ticket