Skip to main content
H
hujingrui1-Visitor
1-Visitor
October 22, 2019
Solved

EMS on rpi not connecting to thingworx server

  • October 22, 2019
  • 11 replies
  • 4545 views

Hi,

I followed the instructions on https://developer.thingworx.com/en/resources/guides/thingworx-raspberry-pi-quickstart/configure-ems 

 

I got a error after ./wsem: Starting the connection  which is:

Main: Unable to connect to server. Trying .booted config file

followed by other errors eg 110 as shown.

 

 

 
 
 
Best answer by slangley

Hi @hujingrui.

 

The config.json you provided appears to be incomplete.  For example, since you're running SSL, there needs to be a valid certificate.  That is not indicated in your config.  Note that the example in the documentation you are following is not complete.

 

If you have a support account, you might consider opening a case to review your configuration for correcting the issue.  You may also want to check the Help Center for more information.

 

Regards.

 

--Sharon

11 replies

V
vangne16-Pearl
16-Pearl
October 22, 2019

@hujingrui I found these posts which might be helpful to refer:

Community Post 1

Community Post 2

Community Post 3

Community Post 4

Community Post 5

 

 

Thanks,

Vibhuti

R
Rick-Stanley5-Regular Member
5-Regular Member
October 22, 2019

Can you upload more of the log file along with your config.json file 

H
hujingrui1-VisitorAuthor
1-Visitor
October 23, 2019

I am starting to think it might be a subsystem issue. I cannot access or http://123.123.123.31:443/Thingworx/WS even http://123.123.123.31:443/Thingworx/WS on browser.

Is there a place in thingworx composer where i can find this information?

 

Previously i have similiar issue for anomaly detection: http://123.123.123.31:8091/training but that issue is solved but seems to be down again now. Are the microservices running together backend? ie all services either run or stops together. if so, it might be the issue.

S
slangleyCommunity Manager
Support
October 24, 2019

Hi @hujingru.

 

Are you sure there isn't a port issue?  In the url you provided:   http://123.123.123.31:443/Thingworx/WS, the protocol (http) is unsecured but the port of 443 is the default port for SSL.  So I would expect your url to be this:   https://123.123.123.31/Thingworx/WS (443 is the default, therefore it's not necessary to include it).  However, in your config, you indicated SSL was "false" so perhaps the correct url would be something like this:

 

 http://123.123.123.31/Thingworx/WS

 http://123.123.123.31:8080/Thingworx/WS

 

Regards.

 

--Sharon

H
hujingrui1-VisitorAuthor
1-Visitor
October 23, 2019

log file is as follows. 

error is as attached

 

 

{
"ws_servers": [{
"host": "123.123.123.31",
"port": 443
}],
"appKey": "xxxxxxxxxx......",
"http_server" : {
"host": "127.0.0.1",
"port": 8080,
"use_default_certificate" : true,
"ssl" : false,
"authenticate" : false
},
"logger":{
"level":"INFO"
},

"certificates":{
"validate": false
}
}

 

Terms & ConditionsAccessibility statement