Currently, working with the Winflector HTML5 Server behind a proxy has some gotchas. A (functioning) workaround is described in this thread: https://www.winflector.com/store/forum/topic-view/id/575
The main issue is that the application list brought by the javascript API brings the original (internal) port and address, and not the public facing ones (that are handled by the proxy).
Some options to solve this:
* Provide a way to specify the public IP and port for the server (similar to what's available in farm configuration - but that doesn't seem to apply here);
* Add a flag (or turn as default) to use the public facing address/ports (that is, the same used in the browser, and not the inner request).
One workaround by now would be to customize the web portal to make these replacements, but it is somewhat cumbersome because their source code (HTML / CSS / JS) is apparently not available, so we could easily tweak on what is already done.
Context:
Why use a proxy?
* Easier to integrate with SSL certificate renewal tools (e.g.: IIS + LetsEncrypt)
* Make available two (or more) sites in one endpoint: we have a web app and the desktop app (that runs on winflector). Each client has their own address. Centralizing everything in the proxy we can enable each one as sub-resources:
https://client.address.com/web-app
https://client.address.com/desktop-app
* Implement a WAF (Web Application Firewall) on top of it all