exces6
-
Posts
3 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by exces6
-
-
6 hours ago, binhex said:
doesnt this work?, left click container icon select edit, then toggle to 'advanced view' (top right) and then change the value for 'WebUI' to 'http://[IP]:[PORT:<port number you want>]/' click on apply at the bottom.
It seems to accept this input and the XML file under dockerMan/templates-user saves the desired input correctly (unlike some posters above), but the generated link in the Unraid GUI still sticks to 8080.
<WebUI>http://[IP]:[PORT:8089]/</WebUI> <Variable> <Value>8089</Value> <Name>WEBUI_PORT</Name> <Mode/> </Variable> <Config Name="8089" Target="8089" Default="8089" Mode="tcp" Description="Container Port: 8089" Type="Port" Display="always" Required="true" Mask="false">8089</Config>
This persists even with a complete Unraid reboot as suggested by wgstarks.
-
On 9/27/2021 at 9:36 PM, guyyst said:
Alright I figured it out, kind of. I did a grep through all the config files in the 'dockerMan' folder to find where '8080' might still be listed. It was still set as the default value for the WEBUI_PORT variable, so I changed that to 9090 as well. After that I could set the 'WebUI' to whatever I want. (Even a hard coded link like 'https://google.com', which... why was that previously prevented by an old default port in WEBUI_PORT ?)
Also, changing the default value of WEBUI_PORT back to 8080 doesn't get me back into the broken state I was in before.
So I really don't know what was going on there, but for anyone else having trouble with this, try changing the default value of WEBUI_PORT ¯\_(ツ)_/¯
This problem has been vexing me all day as well; I'm glad I'm not the only one.
I can't get this to work even if I change the default value of WEBUI_PORT. I'm beginning to suspect there is something odd in this particular Docker image that is forcing all Unraid WebUI GUI links to the default IP:8080 regardless of the link specified in the Advanced view of the Docker configuration page.
My goal: Multiple instances of binhex-qbittorrentvpn, each using a different port for their respective WEBUIs.
I can get the WebUI to be active on a non-default port by doing the following:
1. Delete Host Port 3 (default 8080:8080)
2. Add new TCP mapping [newport]:[newport]
3. Change WEBUI_PORT to [newport]
But regardless of what I change in the WebUI field (Unraid advanced view), the Unraid GUI link redirects me to IP:8080. The only exception is if I manually map container port 8080 to [new port], in which case I get linked to IP:[new port]. But since the container requires a [newport]:[newport] mapping for the WebUI to function, I can't add a second mapping of 8080:[new port] to force the link in the Unraid GUI to work properly.
The field just doesn't seem to change even if I hard code the WebUI link to http://[IP]:[newport] or change it to http://google.com. Other containers let me change the WebUI link to literally anything I want, which leads me to believe this has something to do with this specific container. I can't find anything in the dockerMan XML file referencing port 8080 so it's got to be somewhere deeper.
Yes I could just bookmark the individual links and never access them via the Unraid Docker page, but it would really be nice to have so that in the future I don't have to reinvent the wheel if I ever lose track of which ports I used.
I'd love to help troubleshoot this because I'm at my wit's end trying to get this to work and am pretty close to giving up and just using binhex-rtorrentvpn.
- 1
[Support] binhex - qBittorrentVPN
in Docker Containers
Posted
I've tried this too (that's what I was doing at first), but no luck.
I even just tried manually editing the XML to something random for testing purposes (http://www.google.com) but Unraid still forces IP:8080 in the context menu.