Alexstrasza Posted July 2, 2022 Share Posted July 2, 2022 Hi all, Recently I've started noticing that all of my Docker WebUI links open a new window to about:blank#blocked rather than their destination. I've checked and the links themselves seem fine (e.g. http://[IP]:[PORT:14002]/) and I've also tested with no extensions and no AV other than Windows Defender. I'm wondering if this is perhaps an upcoming security change in Chrome Dev? (I'm running Chrome Dev Version 105.0.5148.2 (Official Build) dev (64-bit)) Has anyone else observed this behavior? Quote Link to comment
jmztaylor Posted July 2, 2022 Share Posted July 2, 2022 I just installed the same Chrome Dev version and I am not seeing this behavior. Everything is working as intended. See if the problem persists in incognito mode. Quote Link to comment
Squid Posted July 2, 2022 Share Posted July 2, 2022 Does Chrome tell you that "popup blocked"? Quote Link to comment
Alexstrasza Posted July 2, 2022 Author Share Posted July 2, 2022 1 hour ago, jmztaylor said: I just installed the same Chrome Dev version and I am not seeing this behavior. Everything is working as intended. See if the problem persists in incognito mode. Hmm, that's so strange. I tried earlier in Incognito and I just tried as well in --disable-extensions mode (which completely disables extensions) and it still does the about:blank#blocked thing. 45 minutes ago, Squid said: Does Chrome tell you that "popup blocked"? It doesn't seem to, and I manually enabled popups as well because I heard that might be an issue. Quote Link to comment
Alexstrasza Posted July 2, 2022 Author Share Posted July 2, 2022 Hmm, if I inspect the actual link itself is it supposed to be literally the [IP]:[PORT] syntax? Quote Link to comment
Squid Posted July 2, 2022 Share Posted July 2, 2022 That's wrong. Can you post the relevant xml from /config/plugins/dockerMan/templates-user on the flash drive Quote Link to comment
Alexstrasza Posted July 2, 2022 Author Share Posted July 2, 2022 (edited) 1 hour ago, Squid said: That's wrong. Can you post the relevant xml from /config/plugins/dockerMan/templates-user on the flash drive <?xml version="1.0"?> <Container version="2"> <Name>Storj</Name> <Repository>storjlabs/storagenode:beta</Repository> <Registry/> <Network>bridge</Network> <MyIP/> <Shell>sh</Shell> <Privileged>false</Privileged> <Support/> <Project>https://documentation.storj.io/</Project> <Overview>This is official Storj V3 node client. To participate you must first have to have an authorization token, to get the Authentication Token go to: https://storj.io/sign-up-farmer
 
 This template is for running the Docker application only, please follow Storj Lab directions to generate your Node Identity files - this is in https://documentation.storj.io/dependencies/identity
 
 
 
 !!! IMPORTANT !!!
 
 Two path need to be passed to the docker. Currently Storj requires that the path are mounted using --mount rather than -v. Please add the path for the storage and identity folders to the extra parameters in the following format (extra parameters can be accessed through the advanced view toggle):
 
 --mount type=bind,source="/mnt/user/appdata//storj/identity/storagenode/",destination=/app/identity --mount type=bind,source="/mnt/user//",destination=/app/config
 
 During the first run the -e SETUP=true argument needs to be added to this string to create the required folders. After the first run when container is created restart it and delete the -e SETUP=true argument.
 
 For additional information please visit the support thread: https://forums.unraid.net/topic/88430-support-storj-v3-docker/
 </Overview> <Category>Cloud: Crypto: Other: Status:Stable</Category> <WebUI>http://[IP]:[PORT:14002]/</WebUI> <TemplateURL>https://raw.githubusercontent.com/dalekseevs/Unraid-Docker-Templates/master/stroragenode-v3.xml</TemplateURL> <Icon>https://raw.githubusercontent.com/dalekseevs/Unraid-Docker-Templates/master/logos/storj-logo-png-transparent.png</Icon> <ExtraParams/> <PostArgs/> <CPUset/> <DateInstalled>1654110094</DateInstalled> <DonateText/> <DonateLink/> <Requires/> <Config Name="TCP Port" Target="28967" Default="28967" Mode="tcp" Description="Default Storj V3 node port." Type="Port" Display="always" Required="true" Mask="false">57658</Config> <Config Name="Dashboard Port" Target="14002" Default="14002" Mode="tcp" Description="The port to access web dashboard" Type="Port" Display="always" Required="true" Mask="false">14002</Config> <Config Name="Email address" Target="EMAIL" Default="" Mode="" Description="Email address used to sign Storj V3 node. (recommended)" Type="Variable" Display="always" Required="true" Mask="false"></Config> <Config Name="Wallet Address" Target="WALLET" Default="" Mode="" Description="Your Payout address here." Type="Variable" Display="always" Required="true" Mask="false"></Config> <Config Name="Allocated Storage" Target="STORAGE" Default="2TB" Mode="" Description="A minimum of 500GB with no maximum of available space per node. Preferred minimum of 8TB and maximum of 24TB of available space per node." Type="Variable" Display="always" Required="true" Mask="false">32TB</Config> <Config Name="Identity directory" Target="/app/identity" Default="" Mode="rw" Description="" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/appdata/Storj/identity/storagenode/</Config> <Config Name="Storage location" Target="/app/config" Default="" Mode="rw" Description="Storj database location" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/Storj/</Config> <Config Name="Internet Address" Target="ADDRESS" Default="domain.ddns.net:28967" Mode="" Description="Your ISP IP address:28967 (static IP) or dynamic DNS address here." Type="Variable" Display="always" Required="true" Mask="false"></Config> <Config Name="TCP Port" Target="28967" Default="28967" Mode="udp" Description="QUIC Port" Type="Port" Display="always" Required="true" Mask="false">57658</Config> <Config Name="Bandwidth" Target="BANDWIDTH" Default="" Mode="" Description="(OPTIONAL) Amount of bandwidth used, per month, to Storj network. According to Storj documentation, minimum is 2TB, recommended is 16+ TB, preferred is unlimited (e.g. 100000TB)." Type="Variable" Display="advanced" Required="false" Mask="false">45TB</Config> </Container> I removed two personal values Edited July 2, 2022 by Alexstrasza Quote Link to comment
Alexstrasza Posted July 14, 2022 Author Share Posted July 14, 2022 I'm also observing this issue in Microsoft Edge. Does anyone see anything off with my XML? Quote Link to comment
valiente Posted August 4, 2022 Share Posted August 4, 2022 (edited) Also have this exact same issue - Doesn't happen with ALL containers, only some... XML: <?xml version="1.0"?> <Container version="2"> <Name>quizmaster</Name> <Repository>nymanjens/quizmaster</Repository> <Registry/> <Network>br0.10</Network> <MyIP>10.10.10.100</MyIP> <Shell>sh</Shell> <Privileged>true</Privileged> <Support/> <Project/> <Overview/> <Category/> <WebUI>http://[IP]:[PORT:9000]</WebUI> <TemplateURL/> <Icon>https://mensa.org.za/wp-content/uploads/2021/03/Quiz1.jpg</Icon> <ExtraParams/> <PostArgs>"bin/server"</PostArgs> <CPUset/> <DateInstalled>1659606132</DateInstalled> <DonateText/> <DonateLink/> <Requires/> <Config Name="Config" Target="/app/conf/quiz" Default="" Mode="rw" Description="" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/appdata/quizmaster/quiz/</Config> <Config Name="application" Target="/app/conf/application.conf" Default="" Mode="rw" Description="" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/appdata/quizmaster/application.conf</Config> </Container> Edited August 4, 2022 by valiente Quote Link to comment
TopherHax Posted August 30, 2022 Share Posted August 30, 2022 I'm also having this exact same issue for Plex docker. Quote Link to comment
itimpi Posted August 31, 2022 Share Posted August 31, 2022 Do you have an ad-blocker installed in the browser? If so you should make sure your Unraid server is white-listed in the ad-blocker. Quote Link to comment
aim60 Posted August 31, 2022 Share Posted August 31, 2022 In the image below, both the successful pihole docker, and the about:blank#blocked binhex-plex docker are running on the same custom network, and have fixed ip addresses. 1 Quote Link to comment
DBJordan Posted August 31, 2022 Share Posted August 31, 2022 Try explicitly specifying the WebUI. Change <WebUI>http://[IP]:[PORT:9000]</WebUI> to <WebUI>http://192.168.198.12:9000</WebUI> 1 Quote Link to comment
TopherHax Posted August 31, 2022 Share Posted August 31, 2022 4 hours ago, DBJordan said: Try explicitly specifying the WebUI. Change <WebUI>http://[IP]:[PORT:9000]</WebUI> to <WebUI>http://192.168.198.12:9000</WebUI> I just tried explicitly specifying in docker edit settings and it works fine now. Not sure what caused it to start this behavior though. 1 Quote Link to comment
cNeCh Posted September 1, 2022 Share Posted September 1, 2022 I have the same problem with my Plex container and only my plex container. How did you fix the problem? Quote Link to comment
TopherHax Posted September 1, 2022 Share Posted September 1, 2022 (edited) 7 hours ago, cNeCh said: I have the same problem with my Plex container and only my plex container. How did you fix the problem? Go to the Plex container, edit settings, switch to advanced view by cliking "basic view" on the top right. Now find the "WebUI" entry and change it to the actual ip and port you use for Plex. Mine is below as an example: Edited September 1, 2022 by TopherHax 1 Quote Link to comment
TopherHax Posted September 2, 2022 Share Posted September 2, 2022 So now I am noticing this is happening to any docker that I update or restart. Just happened to tautulli and sabnzbd after docker update..... Quote Link to comment
Dizzienoo Posted September 5, 2022 Share Posted September 5, 2022 (edited) I had the issue that the links were returning aboutblank#blocked after I had moved containers onto a VPN network and removed all port references. It looks like it might be because the system is unable to populate one of the dynamic fields in the webui template, either IP or PORT and so just spits out a URL that doesn't work. Look to see you have the ports allocated to the containers and there may be something about it being unable to find the IP address of the system? As other people have mentioned, the workaround seems to be to hardcode the web UI links, e.g http://192.168.1.100:8080, this setting can be accessed from teh conainter edit page under the "advanced" settings (activated by the advanced button in the top right of the page). As an extra note, I had issues simply adding 192.168.1.100 or just a port number in the web UI field, it would always add a / between the IP address and whatever was put after. It seems to resolve this you either need to use the default [IP]:[PORT] template or use a full http:// url Edited September 5, 2022 by Dizzienoo Quote Link to comment
Snowman Posted September 18, 2022 Share Posted September 18, 2022 Is there any fix for this besides the manual fix in advance settings mentioned here, like is this a bug or what? My dockers on other VLAN worked before with no issue until today... 2 Quote Link to comment
brianonymous Posted December 20, 2022 Share Posted December 20, 2022 Any more info on this? I have this same prob for any container I route through a VPN bridge Quote Link to comment
sasbro97 Posted June 22, 2023 Share Posted June 22, 2023 I had the same problem after resetting my Docker Engine. Had to delete the docker directory or maybe for others the docker.img vdisk. After that every container with an WebUI link was broken and only opened about:blank#blocked. I have used a custom docker network and that was the problem. It could not be restored even though it was selected in the Docker Template for each application. I had to run all of my 50 containers manually one time with the bridge network and back again to my custom network. Everything works again. I figured out by seeing that the container do not have an IP address: Quote Link to comment
randypfau Posted January 23 Share Posted January 23 as of 1/23/24 I am having this same issue. I had recently deleted my docker.img and my custom docker network was deleted. I read they are not persistant and documentation said you sould create the network prior to reinstalling containers. On the main topic here, my vlans are also screwy about showing the ip address of the container. I have tried everything including changing the network to a different network for the container and it still has the error and doesnt display. Quote Link to comment
Aidan13 Posted February 9 Share Posted February 9 2/9/24 I have the same issue with all my dockers. I ended up deleting all my dockers and I reinstalled only 1 container so this problem was smaller for me. I also had the same issue as sasbro97 where my container did not show a web address in the port mapping area. When I reinstalled 1 container this solved the port mapping missing an ip address. Dizzienoo's post gave me some relief: On 9/5/2022 at 5:38 AM, Dizzienoo said: As other people have mentioned, the workaround seems to be to hardcode the web UI links, e.g http://192.168.1.100:8080, this setting can be accessed from teh conainter edit page under the "advanced" settings (activated by the advanced button in the top right of the page). As an extra note, I had issues simply adding 192.168.1.100 or just a port number in the web UI field, it would always add a / between the IP address and whatever was put after. It seems to resolve this you either need to use the default [IP]:[PORT] template or use a full http:// url With adding the ip address to WebUI at the containers CA form did change the aboutblank#blocked error to a "The connection has timed out" error, which gives me some hope. I'm thinking the ip address I have added to WebUI is incorrect. I have tried the JELLYFIN_PublishedServerUrl: ip address and the ip address shown for port forwarding both of these address gave me the timeout error. If anyone knows the correct ip address to use for the jellyfin WebUI, it would be brilliant if passed this on. Thanks Tim N Quote Link to comment
Aidan13 Posted February 10 Share Posted February 10 Finally got it figured out, going over Network Access again, I saw a little note saying network must be on "eth0"; lght bulb went off. I had taken apart my build again to add some fans and put it all back together & I hooked up my lan cable to the wrong port, its always the small things. Tim N Quote Link to comment
Charlie24 Posted February 17 Share Posted February 17 Hi, I'm also now getting this error I've only just started using gluetun but I've tried it set up using both Nord VPN and PIA (because I'd read there are issues with ports on PIA) and get the about#blocked I can see that Gluetun is working by running the wget -qO- Https://ipinfo.io command in the console and checking the IP address. I then added a port variable to gluetun for the container (Firefox) and run the same command and can see that it's using the correct IP address I've changed the port to use my Lan IP not the dynamic address but still can't access the webgui, I have had about#blocked and refused to connect I've got the gluten container set to custom:bro and Firefox to none Any help would be greatly appreciated Quote Link to comment
Recommended Posts
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.