Skip to main content
B
bmdeshmukh18_4929251-Visitor
1-Visitor
November 16, 2021
Question

nginx

  • November 16, 2021
  • 1 reply
  • 1176 views

Hello,

 

We are using Nginx as a proxy server and a SSO authentication for the ThingWorx setup.

Also we have a ThingWorx Connection Server After Proxy server to be able to connect more number of Edge Devices.

We are able to connect only around 3800-4000 edge devices maximum.
And we are seeing below Errors in Nginx error logs.

2021/10/26 18:02:32 [error] 2384#2384: *1 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 123.21.21.122, server: server.com, request: "POST /Thingworx/Things/ApplicationAThing/Services/ButtonVisible?Accept=application%2Fjson-compressed&_twsr=1&Content-Type=application%2Fjson HTTP/1.1", upstream:

 

2021/10/26 17:33:45 [error] 2387#2387: *39 connect() failed (111: Connection refused) while connecting to upstream, client: 123.12.12.121, server: server.com, request: "POST /Thingworx/Runtime/index.html HTTP/1.1", upstream:

 

2021/11/05 19:30:23 [error] 2362#2362: *160316 upstream timed out (110: Connection timed out) while connecting to upstream, client: 72.3.6.26, server: server.com, request: "GET /Thingworx/WS HTTP/1.1", upstream: "http://72.3.18.22:80/Thingworx/WS", host: "server.com"


Any guides as to why these errors are appearing and what they are indicating.

 

Any inputs would be very helpful.

 

Thanks and Regards,
Bhushan

1 reply

S
slangleyCommunity Manager
Support
December 2, 2021

Hi @BD_01_10085301.

 

Are you able to collect data from any devices or is everything failing even though the devices are connected?  If you're able to collect some data, you should probably check into tuning nginx (timeout setting, message size, config setting, etc.).  It may be getting overwhelmed.

 

Regards.

 

--Sharon

Terms & ConditionsAccessibility statement