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

EMS Tunneling is disconnected

???-31
1-Newbie

EMS Tunneling is disconnected

Hello,

I installed EMS, and it successfully connected to the Platform.

However, when I create an SSH tunnel to the EMS with Remote Access Widget,

connection fails with following messages.

1. When I click on the Remote Access Widget, WSEMS log shows

*****************

TUNNEL NOTIFICATION:

ID: ************

ThingName: TestThing

State: STARTED

Target: 127.0.0.1:22

StartTime: 2016-11-22 09:15:31,976

EndTime: Still in Progress

Duration: 0 msec

User: Unknown

Bytes Sent: 0

Bytes Rcvd: 0

Message:

*****************

2. But after some seconds or minutes,

*****************

TUNNEL NOTIFICATION:

ID: ************

ThingName: TestThing

State: ENDED

Target: 127.0.0.1:22

StartTime: 2016-11-22 09:14:36,793

EndTime: 2016-11-22 09:16:07,464

Duration: 90671 msec

User: Administrator

Bytes Sent: 41

Bytes Rcvd: 0

Message: An unrecoverable IOException occurred so the connection was closed

*****************

When I attempt to connect via localhost:16345 with TeraTerm, username/password prompt appears.

But I can never complete login because End of Tunnel occurs before/at the same time as pressing OK button on the TeraTerm's login prompt.

Does anyone have idea?

-----------

Edge

  Raspberry Pi 3

  WSEMS Version5.3.1 (Linux-ARM-HWFPU)

Platform

  ThingWorx 7.0.1

Network

  Wifi Router (no proxy, can establish SSH connection via 22 port directly)

Regards,

Shunsuke Yamabe

1 ACCEPTED SOLUTION

Accepted Solutions
???-31
1-Newbie
(To:???-31)

Now we have just solved this problem by ourselves.

We should check "AcceptSelfSignedCert" as we use self signed certification.

As I checked this configuration, I could successfully establish the SSH session.

View solution in original post

1 REPLY 1
???-31
1-Newbie
(To:???-31)

Now we have just solved this problem by ourselves.

We should check "AcceptSelfSignedCert" as we use self signed certification.

As I checked this configuration, I could successfully establish the SSH session.

View solution in original post

Announcements