running behind proxy (nginx)

Nobody has claimed this yet.

I tried switching from AUTOMATIC1111 but running with the same command line arg (--listen --api) Forge gets stuck on loading the WebUI (only showing "Loading..."). I suspect that is because I am running this behind a reverse proxy (nginx) - which works fine with automatic - but Forge has some requests that still refer to localhost:7860 instead of the public URL for example:

GET https://localhost:7860/theme.css?v=08a9a3d9d3e40c203ea3699bd76e749856b31c2653d540a483c23edbc452f7af
OPTIONS https://localhost:7860/heartbeat/11yjo1p1h7g
GET https://localhost:7860/custom_component/87f95f6d14efc00a95595f701b29389c/component/style.css
GET https://localhost:7860/custom_component/87f95f6d14efc00a95595f701b29389c/component/index.js

running "--share" with a public gradio link works (with interface from gradio.com).
setting "--server-name" to the real name gives me a connection error (and of course, I can't put it to port 80 directly for obvious reasons)

any hints or suggestions?

Reproduce the WebUI behind an nginx reverse proxy with --listen --api and compare it with the working --share setup. Inspect the requests for theme.css, heartbeat, and custom_component assets; done means the public URL is used instead of localhost:7860 and the WebUI finishes loading.

Written by the indexing model from the issue text.