klippertyk

I have this motherboard and although it's stable I'm constantly having issues with USB drives and devices with it. I can reboot unraid 3-5 times, all will be fine, on the next reboot, the unraid boot menu comes up then a message like "looking for sda" appears, the drive times out, and i'm forced to restart, at this point, the USB drive is not detected until I pull the power cable and fully restart the server. NONE of the USB2 ports seem to work, I've tried my Unraid USB and a Samsung T5 SSD and some tiny sandisk thing. other than that I quite like the board

Thank you - just folllowed this and it worked beautifully. You're awesome for spending the time writing that up for us. Thank you very much indeed - personally I'd have been completely stuck. Again, THANK YOU!

woo woo woo!! It's back. Thank you again @JorgeB!!

Thank you very much @JorgeB i’ll try it and report back. Could you let me know how you discovered that? I’m keen to learn - I have an IT background just not in Linux much.

ok so something strange happened just now. I've had no vms for a while, but just turned the service back on, I created a new vm and selected the windows 11 iso to start the install. Turned on the vm and an old Windows 11 vm immediately popped up in the vnc window - that wasn't even listed. I checked the domains folder and found only the windows 11 folder, I'm wondering if something has happened to the opnsense image not being deleted properly in Unraid or something, but saying that, it wouldn't cause Eth1 doesn't exist on Unraid boot up would it? I'm really confused, I feel like doing a factory reset would probably solve this, but setting all this up took more time than I currently have.

Hi All, I have an issue with the 2nd 2.5GB NIC on my server. The story goes... I've been using Unraid for about 2 years. When I first set it up I flirted with the idea of running opnsense in a vm as my router and abandoned the idea shortly after reading up on the forbidden router. I did however assign a physical NIC to the vm when I was playing about with it. Fast forward 18 months and a couple of Unraid updates later, I deleted the VM. I then had issues upgrading from 6.12.13 to 6.12.14 when upgrading the server I was getting eth0 interface is down showing -1Mbps, half duplex, mtg 1500 - likely unrelated to this issue. I downgraded back to 6.12.13 and everything went back to normal. I recently upgraded to 7.0.1 (love it btw) but I can't seem to get the 2nd NIC to show up anywhere. When I watch the OS loading log I briefly see an entry "Eth1 doesn't exist" Really don't know how to attack this one, I've attached diagnostics. Would appreciate someone more knowledgeable giving me a hand, I would like to get this working again for a future project. I suspect it might have been caused by assigning the nic to the VM and deleting the vm before unassigning it? A wild guess.. thank you.

I just collected diagnostic logs and reverted back to 6.12.13 and eth0 is back up and running. Phew. happy to share my diagnostic log if it'll help or are people already aware of this issue?

HI All, Server working fine until I decided to update to 6.12.14 today - now my eth0 interface is down showing -1Mbps, half duplex, mtg 1500. I have an Asus W680 IPMI motherboard with 2x 2.5g intel nics, and fortunately I got eth1 up and running (can anyone tell me how to quickly change my docker network config to use eth1 while I troubleshoot this please?) but can't get eth0 to come back at all. Everything was 100% ok prior to the update (I'm not using macvlan) Help! anyway to reset the Nic?

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.