Skip to main content
R
RK_103563041-Visitor
1-Visitor
September 1, 2022
Question

Getting "502 Bad Gateway nginx" error while accessing https://servername/Thingworx/WS

  • September 1, 2022
  • 2 replies
  • 3774 views

Hi Team,

 

Please help on this issue.

 

Thanks in advance.

2 replies

N
nmilleson17-Peridot
17-Peridot
September 1, 2022

@RK_10356304 ,

 

Can you give us a little context on how and where you're trying to access this?  Is it for a TWx SDK? EMS? Other?

 

Nick

R
RK_103563041-VisitorAuthor
1-Visitor
September 1, 2022

@nmilleson 

The data is flowing from AWS kinesis stream to ThingWorx 9.3.3 via WebSocket Protocol.

N
nmilleson17-Peridot
17-Peridot
September 1, 2022

@RK_10356304 ,

 

I'm not very familiar with Kinesis streams.  Are you subscribing to that stream somewhere and then sending to ThingWorx?  Typically when I have to connect to the ThingWorx websocket, the address is formatted as wss://servername/Thingworx/WS

 

-Nick

D
Deepak_kankhare12-Amethyst
12-Amethyst
January 31, 2023

This issue might occur due to Thingowrx SSL .jks file is misplaced. Please restore the .jks file on original location or configure the .jks file path in server configuration side.

Thanks!

Terms & ConditionsCookie settingsAccessibility statement