dilar

create an alternate user that is not root and enable it for management. see if that helps.

read further... This does require UPnP or Manual port forwarding. I will remove Connect and use an alternate method of remote access.

I am remote at the moment and can't access logs. I looked at the troubleshooting page and it seems since I have made the SSL/TLS port nonstandard it includes that in my url. Hmmmmmmm.....

ERR_CONNECTION_TIMED_OUT It times out. I have other websites running off the server that work fine. But this backend link to the server through Connect isn't working though. Does it rely on UPnP? I am behind double NAT, and generally don't port forward at all. Using a specific port inside my network works fine, not sure why this (Which seems to capture and be able to display "details" just fine) would be attempting to use the same port for outside access.

Hey y'all. Doing this natively as just UNRraid is possible since Slack can cluster. You'd have to dig hard into the console and install things like slurm to manage the workload. You're not going to get the nodes to present in the UNRaid GUI properly though. However, if you want it to be much easier on yourself, set up a ProxMox cluster and make a UnRaid VM on it. You can assign UNRaid all the CPU cores and memory you want, and even pass through storage for UNRaid to manage. I love UNRaid. Keep thinking differently y'all.

I'm having this trouble as well... I have even deleted the docker .img and completely rebuilt and am still getting this error. Nextcloud Logs are NO help. I wonder if UnRaid logs would be better... Things I've tried: change container port, change container IP, delete Docker vdisk.img and rebuild. (huge pain in the ass because now I have to rebuild the DB too) Anybody got ideas?