Closed kitavidavis closed 9 months ago
@kitavidavis Same for me. It is deployed in a AWS EC2 Cluster but I am getting this issue. Localhost works fine.
@pml-eduardochaves the issue was due to proxy configurations. Check your header's Content-Security-Policy configuration as well. If you are running another instance of socket connection, you might also consider looking at how it is affecting your express-status-monitor WebSocket connection.
The default configuration seems to work fine in localhost. However, running it in a production environment results to error 400. Any means on how to solve this?