winterx

Hi. I spent a whole month trying to do the same without significant progress so i am most grateful you have done it. I must say I can not launch it yet, do you use docker or podman? My docker setup returns

NVM I totally get it. just had a hope it would be something obviuos. My topic was badly formulated. Let me explain. 1. I have a router that routes selected IPs from lan to vpn tunnel 2. To make some of unraid containers work with this setup i gave them fixed ips with bridge network. 3. I do not monitor those dockers 24\7 but once in a week i do and sometimes they are not available 4. Rest of a system work perfectly fine. 5. Remote access to this server was configured through another container so I had to reboot because there is no "restart" option in docker settings menu and "stop" would kill my remote access as well Now I have a wireguard confiured so when it happens again I can restart docker service without reboot. My setup is not a best one ofc but it had months of uptime.

Hi. It looks like you never had a chance to check it out but it still happens every few days. I am going to make a cron script to ping docker in question and make /etc/rc.d/rc.docker restart but it does not look like a permanent solution update: bad https://pastebin.com/82BgJ7kS fixed https://pastebin.com/nxBA8zYZ

bad https://pastebin.com/rdnRu0rV good https://pastebin.com/5v7fbiBK i have a feeling that today it happened when i pointed a new docker to br0 stack

reboot issue was on my side. i had an access through another docker so reboot was my way to restart all of them at once. wg vpn solved it.

unraid-diagnostics-20221105-0022.zip unraid-diagnostics-20221105-0026.zip

Hello. I have a few dockers with static IPs set via br0 They work great for unspecified amount of time, 10 until the last occurence, then become unreachable. my setup 192.168.0.1 - gateway 192.168.0.2 - server 192.168.0.10 - dock1 192.168.0.11 - dock2 i have console access to dock1 from unraid web interface i CAN NOT ping dock1 from server . dest host unreachable i CAN NOT ping server from dock1. dest host unreachable i CAN ping gateway or dock2 from dock1 looks like by bridge gets broken but i can not find a way to prevent it or restore without reboot. Any advice appreciated. How to catch a bug? What log can contain useful data? How to repair bridge wo reboot?

6.10.3 Yesterday I configured few dockers to use fixed IPs via custom network br0. Next day br0 was gone and I had to disable\enable bridging to restore it. However custom networks created in "Network settings" do not appear in docker template options anymore. I can see custom networks for wireguard and docker compose but no br0 or vlans that i created in attempt to fix it. Partly solved Looks like it failed to create 'br0' under Docker. A quick workaround is: rm /var/lib/docker/network/files/local-kv.db /etc/rc.d/rc.docker restart br0 is back What went wrong and how can I fix it? Network settings Docker settings Container settings Also docker.cfg has a weird string DOCKER_CUSTOM_NETWORKS= " "

Hello. I hope someone can give me a piece of routing wisdom. What i have now Router with static IP and wireguard port forwarded to unraid server. Docker containers can access commercial VPN service via dedicated privoxy container. Usecase I connect with my laptop from afar and have an access to my docker containers, LAN and internet via router connection What I want to achieve I connect with my laptop from afar and have an access to docker containers, LAN and internet via commercial VPN service It would be great to route dockers via the same VPN As far as I understand, I am trying to build a chained VPN but I can not find any manuals on this issue. I'd be extremely happy if someone could explain me how to achieve it or offer a better setup

Hi. I've tried to search first but found no suitable answer. My use case looks like this - I have a docker container (gluetun) with commercial vpn that I use for other dockers with --network=container:gluetun option. I'd like to connect to my server remotely (wg?) and use this container for remote devices. Is it even possible?

I do not imply that i asked for one, but i searched all over the forum and documentation extensively. Since I am not an English speaker i might have used wrong choice of words but my intention stays the same: my case was not covered by docs or existing forum replies and i chose to ease the way for the next guy trapped in this loop

I've seen it and It did not work for me. HDD did appear at step 3 but got lost again if added to parity field. fdisk returned input\output error at any stage

Most definitely sata cable or power failure. There might be something else ofc but what i needed most was a solution to bring my HDD back into system. I did replace cable and ordered a very good one as well. UPS must arrive next week too. I built my system from leftover parts and there is always a space for improvement.

No advice on this forum helped me so i decided to write down solution that worked for me. Unraid 6.9..1 Parity disk got disabled after some failure. New config, start stop etc. Nothing helps. It is invisible or just disappears from designated field. unraid fdisk says input output error So i did the following 1. Stop array 2. New config (all) to remove trace of parity disk 3. Remove failed HDD and fdisk delete partition on another machine 4. Put it back and add as new parity disk 5. Thats it If this post helps someone please mention it below.

(SOLVED) I could not find exact problem source and decided to roll back to original mobo. Everything went back to normal immediately. IMO that is somehow related to USB controller model or power management issue. I do understand that many of us build setups from leftover parts and compatibility issues are unavoidable so that might worth a try to make compatibility thread to pinpoint problematic hardware pieces. My 50cent would be: GA - H81ND2H works fine GA - Z87N-WIFI has compatibility issues ---------------------------------------------------------------------- Hello. I've been using Unraid for a short time and ir was fine until i decided to upgrade hardware. Swaped MB and cpu and foun out that onw of my cpu cores is 100% loaded without any dockers or VMs started. I tried to pinpoint the cause with forum advices but with no success. As far as i can see kworker/3:4 burns the cpu but i have no clue what to do next. I hope someone can help me to get back to stable state. Version: 6.9.1 PS top command shows usage by kworker process when i reboot, 100% load migrates to another core but it is kworker again icebox-diagnostics-20210325-1437.zip