|
Problem
|
Possible Solution
|
|---|---|
|
The EMS connects, but reports a time-out error when trying to authenticate.
|
Verify that you are running the required version of Tomcat. Refer to the ThingWorx Edge MicroServer Support Matrix in the help center.
|
|
The EMS is failing to connect to my local server.
|
If your server is not configured to use HTTPS, set the encryption option of the EMS to none. Before deployment, set the option back to ssl.
|
|
I’ve started the EMS, made changes to config.json, but these changes are not reflected when I restart the EMS.
|
There is likely a syntax error (such as an extra comma, or similar) in your config.json. If the EMS is unable to start with the current config.json, it will use the last known good configuration file (config.json_booted).
To verify that the problem is in config.json, delete the config.json_booted file and restart the EMS. If it fails to start, check the config.json for errors.
|
|
The EMS connects to a ThingWorx Platform, authenticates successfully, but the Thing I specified in the “auto_bind” group of my configuration file is not being created on the THingWorx platform.
|
The “auto_bind” group is an array of objects. Verify that you’ve enclosed the JSON object that represents your Thing in square brackets as follows:
"auto_bind": [{
"name”: "RemoteThing001", "gateway": true }] Instead of this, which would lead to this Thing not being created on ThingWorx Platform:
"auto_bind": {
"name" : "RemoteThing001", "gateway": true } |