PsyVision

Thank you very much, that seems to have done the trick!

Yo, thanks for this - I gave it a try this evening and I get the following in my logs: 2022-02-02 21:43:15,256 INFO supervisord started with pid 1 2022-02-02 21:43:16,258 INFO spawned: 'x11' with pid 15 2022-02-02 21:43:16,260 INFO spawned: 'easy-novnc' with pid 16 2022-02-02 21:43:16,261 INFO spawned: 'prusaslicer' with pid 17 2022-02-02 21:43:16,263 INFO spawned: 'openbox' with pid 18 2022-02-02 21:43:17,796 INFO success: x11 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-02-02 21:43:17,796 INFO success: easy-novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-02-02 21:43:17,796 INFO success: prusaslicer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-02-02 21:43:17,796 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-02-02 21:43:18,990 INFO exited: prusaslicer (terminated by SIGSEGV; not expected) 2022-02-02 21:43:19,992 INFO spawned: 'prusaslicer' with pid 29 2022-02-02 21:43:20,025 INFO exited: prusaslicer (terminated by SIGSEGV; not expected) 2022-02-02 21:43:21,401 INFO spawned: 'prusaslicer' with pid 41 2022-02-02 21:43:21,432 INFO exited: prusaslicer (terminated by SIGFPE; not expected) 2022-02-02 21:43:23,436 INFO spawned: 'prusaslicer' with pid 46 2022-02-02 21:43:23,466 INFO exited: prusaslicer (terminated by SIGSEGV; not expected) 2022-02-02 21:43:26,471 INFO spawned: 'prusaslicer' with pid 51 2022-02-02 21:43:26,518 INFO exited: prusaslicer (terminated by SIGFPE; not expected) 2022-02-02 21:43:26,471 INFO spawned: 'prusaslicer' with pid 51 2022-02-02 21:43:26,518 INFO exited: prusaslicer (terminated by SIGFPE; not expected) 2022-02-02 21:43:27,519 INFO gave up: prusaslicer entered FATAL state, too many start retries too quickly When navigating to the IP:8080 I get the connect dialog then a blank/black VNC screen. Any ideas?

Thanks @bonienl!

Thanks for this guide, it's working well for me. I can access my containers on my separate VLAN (192.168.5.0/24) when connected via WireGuard. My unRAID server is 192.168.1.50. In my client configuration I get: AllowedIPs=10.253.0.1/32, 192.168.1.0/24 For everything to work on the client I need to explicitly add 192.168.5.0/24 to the list (e.g when setting up my phone, I had to do this on the phone itself). What is a valid config entry in unRAID to have other subnets populate? I tried adding 192.168.5.0 and 192.168.5.0/24 to the 'Peer allowed IPs' setting but that seems to make no difference.

I see they have just released UniFi Video 3.2 ;) nblain1 - I had to run it from my cache drive or else mongodb wouldn't work, some sort of file read/write speed check it does at startup fails otherwise.

I can't post logs at the moment as I'm in bed now but I did some more digging albeit in the NZBGet container... So I can ping Google.com and I can ping nzbget.org (i think it was) from inside the container (ssh in) my etc resolv file has Google nameservers listed (from my host). If I try and execute the curl command that fetches the nzb JSON file it just sits there doing nothing. It seems that apt-get update is basically doing the same in this and all other containers too. Googling for info shows some people having issues with iptables and routing, I don't have any weird config setup though. I've got VMs turned off but do have bridging enabled - this is no change from recent, though I have recently upgraded hardware, but this shouldn't cause this problem. A reboot hasn't fixed the issue either.

Any ideas on this... my CouchPotato (and NZB from you guys) have both become inaccessible over the last few days. I've deleted both containers and images, and re-created and they still wont open up (connection refused error). I've tried deleting all couch files apart from config.ini and it still wont load.

Looking forward to GrumpyRAID!