Open Dialgatrainer02 opened 6 months ago
@Dialgatrainer02
I have it set up the same way and no errors.
bridge
mode, port 8080/tcp
configured (different port for me)*
and Port is 8080
(get another port on the proxy for me, but leave 8080)http
/ Forward IP: 192.168.0.203
/ Forward Port: 8080
(for me this is changed) / Cache Assets: off
allow 192.168.0.0/16
Perhaps you could also take a screenshot of the dev console to find out more.
I'll be home ina few days I'll send ss of the console as well as double check asset caching is off
@Dialgatrainer02 :point_up_2:
qBittorrent & operating system versions
qbittorrent: 4.6.4 os: docker image hosted on alpine vm
What is the problem?
when behind a reverse proxy most functionality of the web gui seems to break i can exit and log out but most interactivity is broken and torrents don't appear
Steps to reproduce
Additional context
Log(s) & preferences file(s)
192.168.0.200 is my reverse proxi have enabled trusted proxies and added 192.168.0.200 to it and still get the broken barely functional web ui
this is in npm's custom config