Article - CS331632
"500 Internal Server Error" is seen when trying to access ThingWorx Flow
Modified: 23-Jan-2025
Applies To
- ThingWorx Platform 8.4 to 9.5
Description
- ThingWorx and ThingWorx Flow servers are not responsive returning 500 error from nginx server
- NGINX server is proxy server for ThingWorx
- No connections received by the ThingWorx or ThingWorx Flow
- New installation of ThingWorx Flow fails to work correctly due to an NGINX 500 error
- What port should the ThingWorx Platform proxy_pass lines point to in <NGINX>\conf\conf.d\vhost-flow.conf point to
- ThingWorx Flow error 500 Internal Server Error nginx
- The following error is seen in the <NGINX>\logs\error.log file:
- [alert] worker_connections are not enough while connecting to upstream, client: <Client IP>, server: <Server Hostname>, request: "GET /Thingworx/Apps/Flows/ HTTP/1.1", upstream: "https://127.0.0.1:<NGINX Port>/Thingworx/Apps/Flows/", host: "<Server Hostname>"
- After deploying ThingWorx Flow to a large user base some users are reporting that the following error in their browsers:
This is a printer-friendly version of Article 331632 and may be out of date. For the latest version click CS331632