ThingWorx WebSocket-based Edge MicroServer (WS EMS) and Lua Script Resource (LSR) > Troubleshooting the WS EMS
Troubleshooting the WS EMS
This section discusses issues that can arise when using the WS EMS, along with recommended solutions.
Possible Solution
The WS 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 Requirements and Compatibility Matrix, which is available from the Reference Documentation page on the PTC Support site,
The WS EMs is failing to connect to my local server.
If your server is not configured to use HTTPS, set the encryption option of the WS EMS to none. Before deployment, set the option back to ssl.
I’ve started the WS EMS, made changes to config.json, but these changes are not reflected when I restart the WS EMS.
There is likely a syntax error (such as an extra comma, or similar) in your config.json. If the WS 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 WS EMS. If it fails to start, check the config.json for errors.
The WS 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