Aidan13 Posted February 5 Share Posted February 5 These are my docker containers Every one of my containers will not run the WebGui. I can start and stop each container but I am unable to get to webgui. I have shut down the array and restarted it, shut down my system and restarted. Stopped docker completed a restart of my system then started docker. Console will run for all containers. The last docker container I was working on was luckyBackup, where I was getting nginx errors - not enough memory. This was over my head so I stopped. I configured an SMB share to my windows 11 computer and I then downloaded the container backuppc and could not get into webgui. I generally have not messed with the CA form when initially setting up a container the only exceptions are jellyfin which has been working with no problem and HalfLife which I have not been able to get working. Thanks for any help Tim N Quote Link to comment
Kilrah Posted February 5 Share Posted February 5 (edited) Any popup/ad blockers or other browser plugins that could mess with the content or prevent things from loading? Edited February 5 by Kilrah Quote Link to comment
Aidan13 Posted February 7 Author Share Posted February 7 That may be the problem, tried another browser and this is showing at the prompt "about:blank#blocked". With Brave & Edge I get the blank#blocked error with Firefox i get no error and no added web page. I shut down Sponsor Block, ghostery, Kaspersky VPN & Kaspersky safe browsing, none of these work. I can try & add the IP address as trusted address, but is the address going to be static? I am also getting this now when opening Unraid WebGui "NET::ERR_CERT_COMMON_NAME_INVALID". When I 1st started using unraid gui it opened no problem, then I started getting trust certificate errors I downloaded the certificate worked a couple of days now I am getting NAME_INVALID error. . Thanks for the help Kirah Tim N Quote Link to comment
Kilrah Posted February 7 Share Posted February 7 Screenshot the Docker page, I had an "about:blank#blocked" yesterday, happens that the network for that container somehow got removed/set to "None". For the cert I don't know, I don't use https for unraid itself since it's only internal. Quote Link to comment
Aidan13 Posted February 7 Author Share Posted February 7 Here is my docker page image. 14 hours ago, Kilrah said: For the cert I don't know, I don't use https for unraid itself since it's only internal. I have tried changing the "Use SSL/TLS:" from Yes to No back to Yes, unable to select Strict. Does not matter where I set this setting I still get the "about:blank#blocked" error. I did shut down the web browser after each change, to no affect. Here is my management access settings, just for fun. My last try to make this work is to delete them all and reinstall 1 at a time and try opening webgui as I install the dockers. Thanks Tim N Quote Link to comment
Kilrah Posted February 8 Share Posted February 8 (edited) 11 hours ago, Aidan13 said: Here is my docker page image. Something's broken with networking Anything that's running should have IPs there... Don't know what it could be due to though. Edited February 8 by Kilrah Quote Link to comment
Aidan13 Posted February 9 Author Share Posted February 9 I noticed that, just didnt think much of it. This is the one container I didnt want to delete, I have deleted all other docker except jellyfin. I will do this now including image and rebuild this container. Ill let you know it this works. Thanks for help Tim N Quote Link to comment
Aidan13 Posted February 9 Author Share Posted February 9 Reinstalled jellyfin container... still getting "about:blank#blocked". I have done everything I can think of turned off every security feature I can think of, added unraid server to trusted site, added the jellyfin port mapping ip address to trusted sites. I am back to NO on Use SSL/TSL, in managment access. I am at a loss, I really liked unraid for a lot of reasons but not being able to use docker is kindof a deal breaker. The most common reason given for getting the about:blank#blocked error is an address too long, or bad certificate. Now I am unable to open jellyfin from a web browser or my clients on the TV. Going from bad to worse... Thanks for all the help Tim N Quote Link to comment
Aidan13 Posted February 9 Author Share Posted February 9 (edited) Is there a way to see what address the webgui is using to open a page? I tried the 3 IP address shown in Docker Containers - port mapping and I get "The connection was reset" error. Tim N Edited February 9 by Aidan13 Quote Link to comment
Aidan13 Posted February 9 Author Share Posted February 9 (edited) Never mind found it: https://github.com/orgs/linuxserver/packages/container/package/Jellyfin That url takes me to here: https://github.com/linuxserver/docker-jellyfin/pkgs/container/Jellyfin Tim N Edited February 9 by Aidan13 Quote Link to comment
Aidan13 Posted February 9 Author Share Posted February 9 does anyone know the actual IP address jellyfin uses for webgui. My port forwarding address is 172.17.0.2. My JELLYFIN_PublishedServerUrl: is 192.168.0.5 I have entered both of these directly in browser and get the error "The connection has timed out". I have also entered these into the Container Form for WebGui and this also gave me a timeout error. Makes me think these address are incorrect. At the very least I am not getting the about:blank#blocked error. At this point I will take any change as positive progress. Tim N Quote Link to comment
Solution Aidan13 Posted February 10 Author Solution 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. All is right in the world, at least for today. Thanks to all who helped Tim N 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.