Make it more obious you can host Wings behind reverse proxy

[Sietex]

Right now there is (from what I can see) no obvious way to host Wings behind a reverse proxy that manages SSL itself (especially when the panel is hosted using https).

It is however easily doable by disabling ssl in the config.yml for Wings:
api:
host: 0.0.0.0
port: 8080
ssl:
enabled: false
cert: ""
key: ""
disable_remote_download: false
upload_limit: 256
trusted_proxies: []

And setting the allowed_origins in the config.yml for Wings as well:
allowed_origins:
- 172.16.10.50 # IP of reverse proxy

With the following proxy config (for caddy):
https://lxc-wing01.hosting.DOMAIN {
reverse_proxy 172.16.10.40:8080
import certificate # Just my own custom code snippet for certificate management
}

I'm not sure if this is intended but it is very much appreciated, since I do believe it's always safer to host behind a reverse proxy instead of exposing a service directly.

I would suggest adding a checkmark into the Basic or Advanced Settings that reads something like "Behind reverse proxy".

[beingsuz]

Personally its behind Cloudflare with SSL enable just need to to get the origin server Certificate from them instead but Cloudflare does limit the upload to 100MiB

[Pr0mises]

I don't even understand why I need to expose my nodes at all?
E.g.
I've one Proxmox Server, one LXC hosts the panel (which is exposed through a reverse Proxy using a Domain with SSL).
One LXC hosts a wing node, which isn't exposed to the webs and should only be accessible through the internal IP because why should anyone connect to it directly?
Not sure if I missed something in the docs which explains that

[rmartinoscar]

You need it to be reachable because your browser directly reaches for Wings to get the websocket (For the Console).

[Boy132]

See #1263 & #1423