tetrapod

Hia! My YouTube-DL doesn't have an icon I'm getting this to the log-file: YouTube-DL: Could not download icon https://raw.githubusercontent.com/SmartPhoneLover/unraid-docker-templates/main/templates/icons/youtube-dl.png ...and getting a 404 when looking for the file. No biggie, but could you have a look or tell me what I'm doing wrong?

While executing the commands from the same answer you were looking at I have time over I see that @blaine07 already answered your question, but I think he is missing what you are asking about. A command line window can be opened from the top right corner of the Unraid GUI >_

Thanks for caring. I never found out what the problem was and started to set the clock manually. I know, it's not good enough, but there are only so much risks you are willing to take with remote (like four country borders away remote) systems. Anyways, checking now and it seems that somewhere between 6.9.2 and 6.10.5 this fixed itself. It's working now. Could have been a corrupt config file that @John_M mentioned that is now overwritten... Thanks for adding you five cents

Did restart normally, but didn't do any difference for unraid GUI access Yes, that did start the reboot command, but I lost the prompt and all services seemed to be still open. I could see the disk-activity lamp plinking through the PiKVM interface I waited an hour and no difference: ...so used ssh in and did another reboot which did reboot the server, but triggered the parity-check 😐 After this I did manage to get the GUI, but not through the https://www.xxxxxxxxxxxxxxxxxxxxxxxxxx.unraid.net:<port> I had to go through http://<WAN IP>:<port>/ Now I upgraded to 6.11.5 which went well, but still the behavior from above. I changed to the new myunraid certificate and that helped. Now I could get the GUI from my servers page. Still couldn't get VPN access through my WireGuard tunnels, but after a while I realized I had to update the the tunnels after the URL changed. Yes, I do. I'm reading up on this and will m a y b e change it. Need to breathe first a couple of days. My old man heart is not built for remote updates It was the latest. Got uppdated automagically somewhere along the way. Thank you for the quick help and have a nice weekend.

Thank you so much for being thorow in your reply. I'll will have a look tomorow and tell you here how it goes.

Thank you treebeard-diagnostics-20221201-1029.zip

I can no longer reach my servers Unraid GUI. It worked just fine a couple of days ago. If I click [Remote access] I'm directed to the URL https://www.xxxxxxxxxxxxxxxxxxxxxxxxxx.unraid.net:<port>/Dashboard where I get a 500 Internal server error from nginx I have a wireguard tunnel active from where I can remotly reach the GUI of active containers via this URL format http://<server LAN IP>:<port>/ I can also reach services like SMB via the wireguard tunnel, but not the Unraid GUI like I could before via https://<server LAN IP>/Dashboard I get the same 500 Internal server error from nginx What can be wrong? I do at the moment have access to a shell via a connected PiKVM, but do not want to do an unessasary restart and what to find the root of the problem. The server is geografically located in another country and I'm terrified to do something stupid.

That's really good to know - thank you.

Back up again thanks to reboot via PiKVM (prais be it's name). Waiting for 6.11.2 before I touch anything more with network involved. VPN was now able to start without any changes to the config file. Marking the issue as solved

Thank you for providing a solution. However, I applied this without thinking :-$ Not your fault, but I think I cut of the branch I'm sitting on. Got to the [Apply] and then lost communication with the server that is four country boarders north of me. I have a remote access to monitor and power button through a PiKVM, but I'm afraid to order a reboot. Do not know what I could have changed to make this happen?!? I shouldn't have changed anything when hitting [Apply]. But maybe I did? I (think) I chnged one of the top Yes/No switches - something "* binding" - from Yes to No and then back again befor hitting [Apply]. Could that have changes something else? Can I check a settings file somewhere?

Have a workaround for this here, but still needs correction

Well, when WG is running it is very stable. Extremely so imho. To me it seems the error lies with UnRAID's WG config implementation in 6.11.1. I think it's an easy fix but we prabably need to wait for 6.11.2 for that. The workaround is stable

I have the same problem after updating 6.10.3 -> 6.11.1 Figured out a workaround

This is driving me nuts and I think I have figured it out. At least I can get it work, but maybe I do not understand all the implications. In the file /etc/wireguard/wg0.conf there is this line PostUp=ip -4 route add 192.168.100.0/24 via 192.168.100.1 dev table 200 The same line that throws the error in wg-quick.log [#] ip -4 route add 192.168.100.0/24 via 192.168.100.1 dev table 200 Error: either "to" is duplicate, or "200" is a garbage. I refreched some knowledge about routing in Linux and I don't think the "dev " (notice the extra space) should be there. If I edit /etc/wireguard/wg0.conf and remove "dev " the tunnel can stay started and there is no error in wg-quick.log PostUp=ip -4 route add 192.168.100.0/24 via 192.168.100.1 table 200 This solution works and are stable for starting/stopping the tunnel. If I however add a peer or update a peer, the config is overwritten with the "dev " in the line and it needs to be edited again. I have only tested this for "remote access to server" and have not changed anything from default values. Why do I have this problem? I saw the upgrade note that you should refresh Wireguard tunnels to get it to work. So there is an issue with Wireguard, but somehow my system/setup is different. I'll guess this is a workarond for now and maybe someone else can give a +1 if they had the same?

Still have this problem and made some more tests. Tried deleting peers and set up new, but have the same problems so I deleted all tunnels and started anew. I can start this tunnel which add these lines to wg-quick.log wg-quick down wg0 wg-quick: `/etc/wireguard/wg0.conf' does not exist But it does exist. Looks like this: [Interface] #test05 PrivateKey=ANoWVzWStD+5FBt3OoeOv4UDhDEayUDwd6n43ZmLr0M= Address=10.253.0.1 ListenPort=51820 PostUp=logger -t wireguard 'Tunnel WireGuard-wg0 started' PostUp=iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o eth0 -j MASQUERADE PostDown=logger -t wireguard 'Tunnel WireGuard-wg0 stopped' PostDown=iptables -t nat -D POSTROUTING -s 10.253.0.0/24 -o eth0 -j MASQUERADE And I can start it, which add these lines to wg-quick.log wg-quick up wg0 [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.253.0.1 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 started' [#] iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o eth0 -j MASQUERADE Ok, so a tunnel seems to be up, but when I add a peer it goes wrong and the tunnel goes from ACTIVE to INACTIVE I see this added in the wg-quick.log wg-quick down wg0 [#] ip link delete dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 stopped' [#] iptables -t nat -D POSTROUTING -s 10.253.0.0/24 -o eth0 -j MASQUERADE wg-quick up wg0 [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.253.0.1 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] ip -4 route add 10.253.0.2/32 dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 started' [#] iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o eth0 -j MASQUERADE [#] ip -4 route flush table 200 [#] ip -4 route add default via 10.253.0.1 dev wg0 table 200 [#] ip -4 route add 192.168.100.0/24 via 192.168.100.1 dev table 200 Error: either "to" is duplicate, or "200" is a garbage. [#] ip link delete dev wg0 What is the table 200 problem here? Is there a wg0 missing in the second route add? Seems to be double space there? Any pointers would be apriciated - hanging on by a thread here with the server in questions far away in a different country. Also posting my diagnostics diagnostics-20221013-1053.zip

Yes, it is relevant, but I did perform the "Users are advised to regenerate the WG configs" as instructed. I included that information in my description, but mayby I wasn't clear enough. Thank you anyways for responding

No biggie, but coding heros should have their name spelled right His name is "Jason A. Donenfeld"

Just updated to 6.11.1 from 6.10.3 and my wireguard tunnels doesn't seem to start? And yes, I did refresh the tunnel configs as instructed in the release notes 🙂 My remote clients will start, but only show send activity. Nothing for recieved. There is a slider in the settings for the tunnel showing "INACTIV". When clicking it it slides to "ACTIVE" and then directly back again. In the syslog I can see Oct 11 11:55:49 XXX wireguard: Tunnel WireGuard-wg1 started and nothing else. I also see there is a wg.quick.log file that updates when I updated a tunnel and there I see some errors, but I do not understand what they mean. wg-quick up wg0 (autostart) [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.253.0.1 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] ip -4 route add 10.253.0.5/32 dev wg0 [#] ip -4 route add 10.253.0.4/32 dev wg0 [#] ip -4 route add 10.253.0.3/32 dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 started' [#] iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o bond0 -j MASQUERADE wg-quick up wg1 (autostart) [#] ip link add wg1 type wireguard [#] wg setconf wg1 /dev/fd/63 [#] ip -4 address add 10.253.1.1 dev wg1 [#] ip link set mtu 1420 up dev wg1 [#] ip -4 route add 10.253.1.4/32 dev wg1 [#] ip -4 route add 10.253.1.3/32 dev wg1 [#] ip -4 route add 10.253.1.2/32 dev wg1 [#] logger -t wireguard 'Tunnel WireGuard-wg1 started' [#] iptables -t nat -A POSTROUTING -s 10.253.1.0/24 -o bond0 -j MASQUERADE wg-quick down wg0 [#] ip link delete dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 stopped' [#] iptables -t nat -D POSTROUTING -s 10.253.0.0/24 -o bond0 -j MASQUERADE wg-quick up wg0 [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.253.0.1 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] ip -4 route add 10.253.0.5/32 dev wg0 [#] ip -4 route add 10.253.0.4/32 dev wg0 [#] ip -4 route add 10.253.0.3/32 dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 started' [#] iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o eth0 -j MASQUERADE [#] ip -4 route flush table 200 [#] ip -4 route add default via 10.253.0.1 dev wg0 table 200 [#] ip -4 route add 192.168.xxx.xxx/24 via 192.168.xxx.xxx dev table 200 Error: either "to" is duplicate, or "200" is a garbage. [#] ip link delete dev wg0 wg-quick down wg1 [#] ip link delete dev wg1 [#] logger -t wireguard 'Tunnel WireGuard-wg1 stopped' [#] iptables -t nat -D POSTROUTING -s 10.253.1.0/24 -o bond0 -j MASQUERADE wg-quick up wg1 [#] ip link add wg1 type wireguard [#] wg setconf wg1 /dev/fd/63 [#] ip -4 address add 10.253.1.1 dev wg1 [#] ip link set mtu 1420 up dev wg1 [#] ip -4 route add 10.253.1.4/32 dev wg1 [#] ip -4 route add 10.253.1.3/32 dev wg1 [#] ip -4 route add 10.253.1.2/32 dev wg1 [#] logger -t wireguard 'Tunnel WireGuard-wg1 started' [#] iptables -t nat -A POSTROUTING -s 10.253.1.0/24 -o eth0 -j MASQUERADE [#] ip -4 route flush table 201 [#] ip -4 route add default via 10.253.1.1 dev wg1 table 201 [#] ip -4 route add 192.168.xxx.xxx/24 via 192.168.xxx.xxx dev table 201 Error: either "to" is duplicate, or "201" is a garbage. [#] ip link delete dev wg1 wg-quick down wg1 wg-quick: `wg1' is not a WireGuard interface wg-quick up wg0 [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.253.0.1 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] ip -4 route add 10.253.0.5/32 dev wg0 [#] ip -4 route add 10.253.0.4/32 dev wg0 [#] ip -4 route add 10.253.0.3/32 dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 started' [#] iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o eth0 -j MASQUERADE [#] ip -4 route flush table 200 [#] ip -4 route add default via 10.253.0.1 dev wg0 table 200 [#] ip -4 route add 192.168.xxx.xxx/24 via 192.168.xxx.xxx dev table 200 Error: either "to" is duplicate, or "200" is a garbage. [#] ip link delete dev wg0 wg-quick down wg0 wg-quick: `wg0' is not a WireGuard interface wg-quick up wg0 [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.253.0.1 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] ip -4 route add 10.253.0.5/32 dev wg0 [#] ip -4 route add 10.253.0.4/32 dev wg0 [#] ip -4 route add 10.253.0.3/32 dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 started' [#] iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o eth0 -j MASQUERADE [#] ip -4 route flush table 200 [#] ip -4 route add default via 10.253.0.1 dev wg0 table 200 [#] ip -4 route add 192.168.xxx.xxx/24 via 192.168.xxx.xxx dev table 200 Error: either "to" is duplicate, or "200" is a garbage. [#] ip link delete dev wg0 wg-quick down wg0 wg-quick: `wg0' is not a WireGuard interface wg-quick up wg1 [#] ip link add wg1 type wireguard [#] wg setconf wg1 /dev/fd/63 [#] ip -4 address add 10.253.1.1 dev wg1 [#] ip link set mtu 1420 up dev wg1 [#] ip -4 route add 10.253.1.4/32 dev wg1 [#] ip -4 route add 10.253.1.3/32 dev wg1 [#] ip -4 route add 10.253.1.2/32 dev wg1 [#] logger -t wireguard 'Tunnel WireGuard-wg1 started' [#] iptables -t nat -A POSTROUTING -s 10.253.1.0/24 -o eth0 -j MASQUERADE [#] ip -4 route flush table 201 [#] ip -4 route add default via 10.253.1.1 dev wg1 table 201 [#] ip -4 route add 192.168.xxx.xxx/24 via 192.168.xxx.xxx dev table 201 Error: either "to" is duplicate, or "201" is a garbage. [#] ip link delete dev wg1 wg-quick down wg1 wg-quick: `wg1' is not a WireGuard interface wg-quick up wg0 [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.253.0.1 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] ip -4 route add 10.253.0.5/32 dev wg0 [#] ip -4 route add 10.253.0.4/32 dev wg0 [#] ip -4 route add 10.253.0.3/32 dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 started' [#] iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o eth0 -j MASQUERADE [#] ip -4 route flush table 200 [#] ip -4 route add default via 10.253.0.1 dev wg0 table 200 [#] ip -4 route add 192.168.xxx.xxx/24 via 192.168.xxx.xxx dev table 200 Error: either "to" is duplicate, or "200" is a garbage. [#] ip link delete dev wg0 wg-quick down wg0 wg-quick: `wg0' is not a WireGuard interface wg-quick down wg0 wg-quick: `wg0' is not a WireGuard interface wg-quick up wg0 [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.253.0.1 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] ip -4 route add 10.253.0.5/32 dev wg0 [#] ip -4 route add 10.253.0.4/32 dev wg0 [#] ip -4 route add 10.253.0.3/32 dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 started' [#] iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o eth0 -j MASQUERADE [#] ip -4 route flush table 200 [#] ip -4 route add default via 10.253.0.1 dev wg0 table 200 [#] ip -4 route add 192.168.xxx.xxx/24 via 192.168.xxx.xxx dev table 200 Error: either "to" is duplicate, or "200" is a garbage. [#] ip link delete dev wg0 wg-quick down wg0 wg-quick: `wg0' is not a WireGuard interface wg-quick down wg0 wg-quick: `wg0' is not a WireGuard interface wg-quick down wg1 wg-quick: `wg1' is not a WireGuard interface wg-quick up wg0 [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.253.0.1 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] ip -4 route add 10.253.0.5/32 dev wg0 [#] ip -4 route add 10.253.0.4/32 dev wg0 [#] ip -4 route add 10.253.0.3/32 dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 started' [#] iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o eth0 -j MASQUERADE [#] ip -4 route flush table 200 [#] ip -4 route add default via 10.253.0.1 dev wg0 table 200 [#] ip -4 route add 192.168.xxx.xxx/24 via 192.168.xxx.xxx dev table 200 Error: either "to" is duplicate, or "200" is a garbage. [#] ip link delete dev wg0 wg-quick down wg0 wg-quick: `wg0' is not a WireGuard interface wg-quick up wg1 [#] ip link add wg1 type wireguard [#] wg setconf wg1 /dev/fd/63 [#] ip -4 address add 10.253.1.1 dev wg1 [#] ip link set mtu 1420 up dev wg1 [#] ip -4 route add 10.253.1.4/32 dev wg1 [#] ip -4 route add 10.253.1.3/32 dev wg1 [#] ip -4 route add 10.253.1.2/32 dev wg1 [#] logger -t wireguard 'Tunnel WireGuard-wg1 started' [#] iptables -t nat -A POSTROUTING -s 10.253.1.0/24 -o eth0 -j MASQUERADE [#] ip -4 route flush table 201 [#] ip -4 route add default via 10.253.1.1 dev wg1 table 201 [#] ip -4 route add 192.168.xxx.xxx/24 via 192.168.xxx.xxx dev table 201 Error: either "to" is duplicate, or "201" is a garbage. [#] ip link delete dev wg1 wg-quick down wg1 wg-quick: `wg1' is not a WireGuard interface

If you are hanging around here I asume you are running Calibre in a container on an Unraid server? I find Calibre very useful, but also equally confusing. For upload, download, mailing etc. I use the Calibre-Web container from the Unraid Apps page as a wrapper for Calibre. Easier to handle and a better overview of what it does. Especially when I try explaining it to my family. I do not have the problem you are describing when emailing books to my Kindle from the Calibre-Web server. Hope that can be of help to you. I still dont have a good work flow when it comes to how my media server works for eboks and audio books. I'm using Readarr, Calibre and Calibre-Web at the moment and if anyone know a good forum for discussing this I'm all ears

Confirming having same problem and the --security-opt seccomp=unconfined fixed it for me also. Thank you

Much water have flown under the bridges and I'm finaly serverside again. I tried the USB-RS232 adapter so kindly suggested by @DigitalMaestro and @Gnomuz. Unraid rightly identifies the device root@:/mnt/user/appdata# lsusb Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 0781:5571 SanDisk Corp. Cruzer Fit Bus 003 Device 002: ID 8087:0029 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cd:0121 Keyspan USA-19hs serial adapter Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I'm having problems finding the right settings for the UPS deamond, BUT my bigger problem is that I'll get the original problem where the device path keeps on changing. I started at 002, but keeps changing one up: root:/mnt/user/appdata# ls /dev/bus/usb/ 001/ 002/ 003/ 004/ 005/ 006/ I think adding a PCI serial port card is my next move. Just hope it'll arrive before I have to leave again. I'm also waiting for the last part of a PiKWM-switch. I have high hopes for that to be a lifesaving device for my situation where I seldom are server side and have to cross four country boarders to be near my baby 😐 To Be Continued...

I have this problem also. The but none of the commands render any output: :~# fuser -s "/mnt/user/system/libvirt/libvirt.img" :~# losetup -j "/mnt/user/system/libvirt/libvirt.img" :~# I still have the problem where I see: ~# fuser -c /mnt/user/system/libvirt/libvirt.img /mnt/user/system/libvirt/libvirt.img: 12659c 14997 14999 15000 15051m 15619 15621 15623 15625 15627 17069c 17136 17525 18758 19036 19298 19856m 19980m 20180m 20538 20705 20824m 21309 21751 21986 21988 21989 22042 22043 22044 22045 22046 22047 22048 22049 22052 22053 22055 22056 22057 22059 22060 22061 22062 22063 22064 22066 22067 22068 22070 22071 22072 22073 22074 22075 22076 22077 22078 22079 23509m 23942 24433 24434 24456 24457 24458 24459 25140c 25219c Which correspond to these processes: php-fpm: master process (/etc/php7/php-fpm.conf) nginx: master process /usr/sbin/nginx -c /config/nginx/nginx.conf /usr/bin/python3 /usr/bin/fail2ban-client -x -f start influxd nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: cache manager process /usr/bin/mariadbd --basedir=/usr --datadir=/config/databases --plugin-dir=/u /usr/bin/python /usr/bin/supervisord -c /etc/supervisor.conf -n /usr/bin/python /usr/bin/supervisord -c /etc/supervisor.conf -n /usr/bin/python /usr/bin/supervisord -c /etc/supervisor.conf -n /usr/bin/python /usr/bin/supervisord -c /etc/supervisor.conf -n /usr/bin/python /usr/bin/supervisord -c /etc/supervisor.conf -n /usr/bin/mono --debug /usr/lib/sonarr/bin/Sonarr.exe -nobrowser -data=/confi /app/bin/Readarr --nobrowser --data=/config /usr/lib/radarr/bin/Radarr -nobrowser -data=/config /usr/bin/python /usr/bin/supervisord -c /etc/supervisor.conf -n /opt/ombi/Ombi --storage /config --host http://*:3579 /usr/lib/lidarr/bin/Lidarr -nobrowser -data=/config python3 /app/bin/nzbhydra2wrapperPy3.py --nobrowser --datafolder /config java -Xmx256M -DfromWrapper -XX:TieredStopAtLevel=1 -noverify -XX:+HeapDumpO nginx: master process /usr/sbin/nginx -c /config/nginx/nginx.conf php-fpm: master process (/etc/php7/php-fpm.conf) python3 /app/tautulli/Tautulli.py --datadir /config nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process nginx: worker process /usr/bin/python3 -u /app/bazarr/bin/bazarr/main.py --no-update --config /con /usr/sbin/python3 /usr/lib/sabnzbd/SABnzbd.py --daemon --config-file /config php-fpm: master process (/etc/php7/php-fpm.conf) nginx: master process /usr/sbin/nginx -c /config/nginx/nginx.conf nginx: worker process nginx: worker process nginx: worker process nginx: worker process /usr/bin/python /usr/bin/deluged -c /config -L info -l /config/deluged.log deluge-web Attaching my diagnostics from after I tried reboot which didn't help. I then tried stopping the Docker service and the start the VM service and then it did come up. But... ...starting my daily driver Win10 VM did not work. I get "Cannot get interface MTU on 'virbr0': No such device." Searched some more and found this: :~# virsh net-start default Network default started This made it possible to start the VM without the error. I can use TeamViewer to use the VM, but I get "Failed to connect to server" in the VNC Remote window diagnostics-20220124-1513.zip

Not a thing that is solved but marking it such now.

Is this statement true and what is the Writable column?

64GB CPU: AMD Ryzen 9 3950X 3.5 GHz 16-Core Processor CPU Cooler: Noctua NH-D15 82.5 CFM CPU Cooler Motherboard: ASRock X570 Phantom Gaming X ATX AM4 Motherboard Memory: Corsair Vengeance LPX 64 GBDDR4-3600 CL18 Memory Storage: 2* Samsung 980 Pro 1 TB M.2-2280 NVME Solid State Drive Storage: 1* Samsung 980 Pro 2 TB M.2-2280 NVME Solid State Drive Storage: 7* Seagate EXOS Enterprise X18 18 TB 3.5" 7200RPM Internal Hard Drive Storage: Seagate IronWolf Pro 14 TB 3.5" 7200RPM Internal Hard Drive Video Card: PNY Quadro P2000 5 GB Video Card Case: Fractal Design Define 7 XL ATX Full Tower Case Power Supply: Corsair HX Platinum 1000 W 80+ Platinum Certified Fully Modular ATX Power Supply Case Fan: 7* Noctua A15 PWM 140 mm Fan UPS: APC SMC1500I UPS DELL H310 SAS 8Port 12Gb/s PCIE3.0 Extended family and friends media server. 30+ containers and some VMs. CCTV server and home automation server