August 20, 20223 yr Version: 6.11.0-rc3 I've successfully set up a custom network to route traffic on some of my containers through a VPN. When I try to use Unraid to navigate to the docker's web interface by clicking the docker's icon and drop list, it doesn't work. It opens a new tab that Chrome tells me is called about:blank#blocked. I have to instead enter unraid's url:port in the address bar manually to get to the web UI and am hoping there's a simpler way. Any ideas on how to make the WebUI work from the Unraid page? Edited August 20, 20223 yr by DBJordan Specified version number.
August 20, 20223 yr What version of the OS? Try updating to 6.11 as there were some changes regarding how WebUI's are handled.
August 20, 20223 yr Author Hi Squid, Just updated to 6.11-rc3 and seeing the same. Can get to the web ui by specifying my ip:port in the browser address bar but not by clicking from the docker page. Edited August 21, 20223 yr by DBJordan Attached docker settings for vpn and client containers.
August 25, 20223 yr WebUI entry is never [HOST] should always be [IP] Running the container through another is a complication though and I'm unable to assist with that as I've never seen the real point in doing so for how I use my system
August 25, 20223 yr Author Thanks for the reply. I tried changing HOST to IP without success. I'll check out the container support thread to see if anyone has any ideas.
August 30, 20223 yr Author Solution Well, I have it working, although I'm not sure it's the most elegant solution. Everything is now working. I just updated webui to hard code the url of the webui instead of relying on things like [HOST], [IP], and [PORT]. See screen capture.
August 30, 20223 yr I ran into the same problem. 6.11-rc4 binhex-plex about:blank#blocked in chrome and edge. Firefox does nothing, doesn't even bring up a new tab.
August 31, 20223 yr Author 16 hours ago, aim60 said: I ran into the same problem. 6.11-rc4 binhex-plex about:blank#blocked in chrome and edge. Firefox does nothing, doesn't even bring up a new tab. Try explicitly specifying (hard coding) the WebUI. Maybe my screen shot wasn't clear enough-- what got it working for me was changing: http://[HOST]:[PORT:9117] to http://172.16.100.100:9117
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.