In order to overcome an issue we were experiencing regarding webSockets, we are going to move our Lightstreamer deployment up a physical level between our internal application servers and the internet. Note that the webSocket issue is internal and not related to Lightstreamer itself.

We had previously deployed Lightstreamer behind a reverse proxy running IIS, which worked great, minus the webSocket issue. We are now attempting to install Lightstreamer straight on to the reverse proxy machine directly. The issue we are currently running into is that we had to remove IIS (due to both IIS and Lightstreamer listening to port 443) which is removing our ability to serve HTML pages (such as pages/monitor/index.html).

Anyone with information regarding this type of deployment would be greatly appreciated!!