klippertyk

for others... https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications I am new to this, so any advice apprciated - pre-req checks or gotchas would be useful.

I'm having the same issue - my docker.img is 42.9gb. I've had this error for a while actually and only got around to invesitgating the problem recently. Can I please ask - are there updated links for your articles above? They appear to be out of date. My primary concern is losing my config, my containers took hours to setup - i'm curious as to what is writing to the docker.img though - any tips to investigate that?

I don't think this is an Unraid issue, but as I'm using it on this board, I thought it worth posting. I updated the BIOS to 2802 today from 2305 as part of some prep to update from 6.11.5. When I do a shutdown via unraid, on the next power on, all the drives are no longer detected in POST. I have to powerdown again via IPMI then everything behaves itself. Warm restarts are ok. I'm posting just incase anyone uses this board and has the same issue and if anyone has any ideas why this might be happening (ACPI settings?) as the update blew away my BIOS config so I may have forgotten to set something correctly. This is repeatable. Normal.... Not normal...

just signed up to mullvad but the link in 1st post (and their site) I get a 404. Sooo.... I'm a bit stuck? okaaay had to embarass myself in public to work it out. you have to click account on the top right...

still beavering away at this and my previous comment jumped the gun a bit and didn't solve all my issues. I'm having real trouble getting containers to communicate with each other depending if they are setup to use gluetun or not. I thought I found the answer here which sounds ideal, but I'm on a lengthy NordVPN subscription. At this point I'm prepared to sign up with another provider just to get the VPN tunnel setup but not sure who to go with (I'm based in the UK)

in an effort to fix the prowlarr issue myself, I watched this vid and thought it was excellent. i realised I needed to specify the bridge ip and volia! sorted. Im really interested in try macvlan now though, he's right, the networking in dockers is so cool

Hello! TL:DR - 1. Prowlarr on Gluetun won't connect to other containers not using gluetun's container connection. 2. how to get vpn working for containers generally. I've been scratching my head a little. I've setup the gluetunvpn container to securely provide vpn tunnels to containers. I reviewed spaceinvaders guide to sharing that connection with other containers, and all appeared to be working quite well, I linked jackett via gluetun to sonarr (bridge) and things were going well and the idea was proven. Until I decided to switch from jackett to prowlarr, I need to run prowlarr using gluetun's connection as I did with jackett but when I do, I cannot get it to communicate to sonarr or anything else, switching sonarr over to use gluntun's connection works fine, until I change it back to the container bridge again. Basically I cannot connect to any other containers with prowlarr when it's on gluetun and they are not. browsing several forums, I get the impression this is an "issue" with prowlarr, but I don't understand enough to fix it. Anyone been able to get prowlarr to connect with sonarr or qbittorrent without them also being on a gluetun connection? Which leads me into point 2. My router isn't powerful enough to have an openvpn connection setup on it, else I would do that for all connections and not use gluetun at all, so my question here is, how are you guys securing your containers over vpn (if different to the above) I plan to look at nginxproxymanager next to see what that offers.

Thank you binhex. appreciate your time.

never mind. only needed to change the host port and not the container port. Hello @binhex chimp with a keyboard again and you guessed it, new docker, same(ish) problem. i cant use 8080 and thought after our last adventure I was modifying ports like a boss, alas, on this container, despite me changing ports the log says listening on 8080 and i cant hit the webgui... any faq on this topic?

I understand. As I say I'm quite new to unraid and dockers (but having a blast learning it for my new server) so I was sticking to "what works" as I built my understanding - I didn't have a picture of host vs bridge vs custom bridge, which I learned when puzzling out this issue. I was illustrating that I had vanilla qbit webui working on host, but not in bridge and qbitvpn forced bridge and no webui. Difficult to troubleshoot. What's the reason you mention? FYI - I had to root cause this and test your theory and you were correct, I disabled adblock and it popped up. Thanks for your help and thanks for the time and effort you put into this tooling, really very much appreciated and absolutely adds value to unraid imo.

I would say that is a good theory Binhex yes. I have adblock and ublock origin installed as extensions, but I would have never had guessed that (partly because I had NO IDEA that field was supposed to be there!). A little odd adblock or ublock would take issue with a field to me, but then again, i'm not a code writer either. I was so utterly frustrated by this, I had the log open, I got the vpn working no problems at all, then, to be stumped by the webui... It's worth noting I was checking my logic by removing this docker and installing the vanilla qbit, as it happens I couldn't hit the web ui on any network setting other than host (resolved: my mistake). Which, btw... if I try and setup qbitvpn with host as the network setting, it falls over and doesn't create the docker at all... in case you're interested..

6.11.5 on chrome. It's basically a new deployment. I'll try edge... oh my days, there it is.... you know, for someone new, this was really really puzzling. I'll consider myself rather unlucky eh? I'll give it a try.

wait... If I select the drop down as "path" i see name container path host path default value access mode description but when i select port - I get what I stated

OMG! No! No there is not! I now have a setting called Custom Host Port 1111 and in orange underneath it says Container Port: <blank>

Hi Binhex, thanks for replying. I read all the faq, articles and that link (thanks for making all the support docs easy to find) perhaps it was because it was 2am, but I couldn't puzzle it out. I'll step through the setup as a write this... and reference your faq. I'll be deliberately pedantic to illustrate what I'm doing. 1. Open unRAID Web UI/Docker left click qBittorrent and select Edit I assume this means binhex-qbittorrentvpn 2.Go to Container Variable: WEBUI_PORT and click on Edit and set the Value to the port number you want to run the Web UI on and click Save This is NOT "Host Port 3" - which is labelled Container Port: 8080 It IS "Key 9" which is called "Container Variable: WEBUI_PORT" which is also 8080 <- this is the one I changed i.e 1111 3. Find Container Port: 8080 and click on Remove This is "Host Port 3" - Labelled "Container Port 8080" <- this is removed 4. Click on blue link Add another Path, Port, Variable, Label or Device and select config type of port ok... no room for intrepretation here.. now the bit I don't get.. 5. Set the Container Port: and Host Port: to the same value as the Container Variable: WEBUI_PORT then click on Add This will be the value I set in step 2. which will be 1111 Ok, I have.. Config Type - Port Name = What(?) Host Port = 1111 Default Value = what(?) Connection Type = TCP Description = (just a description) and click add. In my head I've added the host port only. So... do I need to do this again and specify a container port now? There is no container port (like there was host port) when clicking add another path, port, variable.... and selecting port. 6. Click on Apply at the bottom and wait for the container to be recreated. yup 7. Attempt access to the qBittorrent Web UI using the new port. am I right?

You know you said you were at your wits end..... I'm 5 days behind you... 🙂 I spent 4 hours trying to get this to work last night. I have EXACTLY the same problem (Unify, not your subnet) can you please, in "a chimp with a keyboard" terms tell me how you changed the webui port... I know from your explaination above you were doing this... "So in order to get around this you need to edit the container and then use the link down the bottom shown as "Add another Path, Port, Variable, Label or Device", select "config type" as "port" then put in the port number you want for both the "container port" and "host port" and then click "add". So now you have added the additional port you can now remove the old port, as this will now clash on the host port if you have already altered it. Remember - Make sure to set the webui_port to the same value and then click on "apply" button to apply the changes." But i'm new to dockers and can't tell if I need to put two settings, one for container port and one for host port or what... please.. just step 1 step 2 etc.. thanks.

+1! I am also using the same board, with a 13500. I am also using slimsas cable with 4x sata cables. I'm using kingston memory with reports single bit ecc Total Width: 80 bits Data Width: 64 bits I use the ipmi card and it's very good. I get a lot of temperature monitoring and power info and use it to control the case fan speeds. I switched as the sensor driver is trying to use nct 6775 (if i remember correctly) which has a well documented bug, but there is a new driver in the 6.2 kernel coming - (whenever limetech move to that) very happy with the board, although it seems the top row of usb ports (looking at it vertically) are a bit picky on what they will detect, I had to plugin my UPS into a lower bank of usb ports to get it detected.

Hi SimonF, Appreciate you sticking with me on this one. Sometimes the low tech way wins out. I just sat with the console open and ran lsusb over and over working though the ports each time and eventually..... Bus 001 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply appeared! Unraid picked it up and all is well, can see everything I need. Seems to me like the uppermost row of USB ports on this board (2x SS 1x "BIOS" and 1x (I think it's usb2) are particularly fussy about what's connected to them. I actually recall when I assembled the hardware on the motherboard box for validation and booted the board for testing I had issues with my USB keyboard and wireless mouse dongle when using that row, but didn't put 2+2 together as I dismissed it as a buggy bios (was much improved after an update) and just general first time setup "bedding in" the ports work, as I've had that usb drive plugged in them ok, but as to why they wont pick up some usb devices, someone more knowledgable will have to say.... again, I appreciate your time working through this with me, if you would still like the diagnostic I'm happy to provide.

I was starting to worry I had some dodgy USB ports on the motherboard (i have not connected case headers) so after failing to get the ups detected again, i've plugged a usb pen drive in the same port as the ups was, and plugged the ups into a different port.. Bus 002 Device 003: ID 0781:5583 SanDisk Corp. Ultra Fit Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 004: ID 046b:ffb0 American Megatrends, Inc. Virtual Ethernet. Bus 001 Device 003: ID 046b:ff01 American Megatrends, Inc. Virtual Hub Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub still nthin. the port is live, that sandisk was the test device.

Asus W680 IMPI https://www.asus.com/motherboards-components/motherboards/workstation/pro-ws-w680-ace-ipmi/

lsusb from terminal shows... Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 003 Device 002: ID 1005:b155 Apacer Technology, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub so the course of action is clear, get that bus 003 device to appear on lsusb first eh. is there a command to get unraid to query usb ports for devices please?

I'm viewing external devices in the qnap gui, USB is selected and both snmp and network share are grey'd out. I realise this doesn't quite answer your question so i'm currently googling how I get more info from a console.

I plugged the UPS back into the Qnap and it is working, I see battery charge, est run time. Connected by USB It's an APC BACK-UPS ES 700G

Alright, so... I think this isn't anything to do with unraid, but as it' that service I can't use... see what you think. I have two devices. 1. "qnap1" this runs a container for pihole. 2. "unraid2" this is my new unraid server. My Router performs DHCP - this is configured to use dns from qnap1. On pi-hole, both hostnames have a records in DNS. My laptop correctly ets its ip address from dhcp on the router, and the router is correctly making my laptop use the pihole dns. Nslookup confirms this when getting successful connections to both qnap1 and unraid2 hostnames. I can ping both as well. Until I turn on the NordVPN Windows client and make a connection. Then it gets a bit strange. On nordvpn, I can still ping qnap1, but not the unraid2. (both time out on their nslookups from pihole incidentally) The confusion is, as far as I can tell all elements are equal - therefore I should either be able to ping both, or neither. What's going on? Anyone got any ideas for trying to identify the issue? It's worth pointing out I did notice on the nslookups my machine was defaulting to NordVPNs DNS IPs and I thought I'd cracked the issue (despite STILL being able to ping qnap1!) and I added the pihole IP as a custom dns in the client, but unraid1 still doesn't work. I can still access shares on unraid via ip address, but I want to use the hostname (more to fix/understand this problem than anything else!) On a side note, I wanted to move my pihole service over to Unraid, but i'm getting the following error - docker: Error response from daemon: driver failed programming external connectivity on endpoint pihole (308e2f603d2e8bc6b9f4bc6c153122eb9fd0306efe5a447a0bd6ca17619bf476): Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use. Port 80 is already in use? I ran sudo netstat -tunlp to check and found this... no idea what it is. tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 3028/nginx: master How do I fix this please? I want to run pihole on unraid. Thanks for reading!