The config server, right now, uses CFG_HOSTNAME as a local host to connect to. It also exposes this same setting to the client as a public-facing hostname, along with the port.
This breaks deployments behind reverse proxies, and deployments over the internet, as these variables are not the same. The config server should have a separate config variable for local interface name, and should expose an ORIGIN or BASE_URL setting to the client instead of a hostname/path combo.
The config server, right now, uses CFG_HOSTNAME as a local host to connect to. It also exposes this same setting to the client as a public-facing hostname, along with the port.
This breaks deployments behind reverse proxies, and deployments over the internet, as these variables are not the same. The config server should have a separate config variable for local interface name, and should expose an ORIGIN or BASE_URL setting to the client instead of a hostname/path combo.