cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

EMS and Tunneling - Tunnel Subsytem is not running.

Highlighted

EMS and Tunneling - Tunnel Subsytem is not running.

Hello all!

I am struggling with the EMS configuration on the Customer side, especially Tunneling.

  • ThingWorx 8.0.7-b74 HTTPS
  • EMS 5.4.0 OPENSSL Windows x86-x64

Configuration file:

{

    "ws_servers":   [{

            "host": "###",

            "port": 443

        }],

    "ws_connection": {

        "encryption": "ssl"

    },

    "logger": { 

        "level": "DEBUG"  

    }, 

    "appKey":   "###",

    "certificates": {

        "validate": false,

        "allow_self_signed": true

    },

    "http_server" : {

        "use_default_certificate" : true,

        "ssl" : false,

        "authenticate" : false

    },

    "auto_bind": [{

        "name": "DemoThing123"

    }]

}

It seems to be standard dev configuration. No issue with my local instance (HTTP).

The problem is if I want to connect and establish tunneling on the Customer instance.

First of all Tunneling seems to be not working correctly at all:

002.PNG

RemoteThing (with tunneling ofc) is connected. Tunneling is enabled and created. (tcp, 5900, vnc)

In the mashup I am receiving:

001.PNG

TunnelingSubsytem is Enabled, Running. Nothing weird.

NOTE: One thing is that in Configuration of Tunnel Subsystem there is a host defined, which I cannot ping. (IP is different than IP of this instance). I am not an Administrator user, so cannot change it.

Any ideas?

Best Regards,

Adam