#2836 closed bug (Invalid)
webui returns blank page when used with --base
Reported by: | Matt | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | needs verified |
Component: | Web UI | Version: | develop |
Keywords: | --base proxy | Cc: | Calum |
Description
This is in reference to closed ticket http://dev.deluge-torrent.org/ticket/2677
I am running latest develop branch which includes the commits to fix this issue.
When configured as such (using --base or setting base in web.conf) I get nothing but a blank page when browsing to the web site.
I've tested the site in IE, FF, Chrome, and Edge, all have the same issue.
I can privately provide a URL which is publicly accessible for verification.
Change History (5)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Are you sure this is not the same as #2807
If you see a blank page then you need to report any errors from browser developer console.
comment:3 by , 9 years ago
EDIT: I just realized I get nothing even without a base being set. This may be the same as 2807, trying now.
Command I've been testing with is
deluge-web --config=/tmp --base="/deluge" -L debug
Developer console shows an error in Delugr.debug, but only in Chrome, I don't see if in safari.
I've tried the following URL
http://10.0.2.15:8112/deluge http://10.0.2.15:8112/deluge/ https://tld.com/deluge https://tld.com/deluge/
The TLD is behind a Netscaler VPX using Content Switching/Reverse Proxy. I use the same device for NZBGet/Sonarr/Couch with no issues.
The Netscaler also provides SSL Offloading, so the back end connection is http. Aside from Netscaler issues, I would expect the IP address to work.
I've also tried sending the X-Deluge-Base header to no avail.
comment:4 by , 9 years ago
Resolution: | → Invalid |
---|---|
Status: | new → closed |
sorry, this was #2807 getting me. It was late and I had never tested without the base to realize I had no WebUI no matter what.
comment:5 by , 9 years ago
Either using develop install or run minify script should work: http://dev.deluge-torrent.org/ticket/2807#comment:22
To be able to reproduce the issue we need as much detailed information as possible. That includes the exact command you run as well as the URL you try to access.