ErikH

Of course, thanks! Here is my diagnostics zip-file. tower-diagnostics-20221113-1519.zip

I've been back and forth but haven't found a solution yet. When Unraid boots up, the array will not autostart. In settings under 'Disk settings', 'Enable auto start:' is set to Yes. Yet when the server boots up it says in the lower grey area that the array is stopped. When I look at the 'Array operation section' it shows: Stopped. However when I hover over it, it shows: I can manually start it and everything looks fine (and works). I have set 'Enable auto start' to no, rebooted and then set it to yes and rebooted again but no luck so far. The disks in the array seem to be fine... I seem to be missing something but I have no idea what... Any ideas?

Oh! Didn't see that. Network type to e1000 did the job! Thanks :)

I used to be able to install a Windows 11 VM without network. During the installation process at some point I was able to choose to install with 'limited' support and create a local Windows account. After finishing installation I could load the network drivers in the VM and go from there. The new Windows installation does not seem to allow that anymore. It just tells you you need internet to finish installation. There is no way to load the network driver. Or none that I see... Anyone got around this?

Gentlemen, it took me some time before I actually had the time to work on this. I first removed router 2 and made sure the ip-range was correct. The network now works with only one (the first) router. Then I tried again, but had no luck. So after that I tried a clean install of the server and then it worked! Thanks!

What I've read so far, to be (completely) safe, Hyper-threading should be disabled. I'm wondering if / how this will affect (my) unraid builds...

Well it's a good excuse to clean up the network and take the 2nd router out of the loop. Been meaning to do that for some time, and this is a good reason. Port forwarding worked till now so I didn't expect that to be the problem. Anyway, I'll be back

NP, I added an extra image to show how the routing is done. The reason for 2 routers is that router 1 used to be a simple cable modem. It broke when I was not at home and a technician replaced it with a fancy all in one modem / router. When I got back, I left it like that (due to the fact that the two are two floors apart) and just routed the ports on router 1 to just pass them on 1 on 1. routing.zip

here's my routing. I have directed the a-records directly to my ip for now (my ip adress hasn't changed over a year), which I will set up further when I have this working. routing.zip

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='letsencrypt' --net='bridge' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'EMAIL'='[email protected]' -e 'URL'='xxxxxx.xxx' -e 'SUBDOMAINS'='nextcloud,deluge' -e 'ONLY_SUBDOMAINS'='true' -e 'DHLEVEL'='2048' -e 'VALIDATION'='http' -e 'DNSPLUGIN'='' -e 'PUID'='99' -e 'PGID'='100' -p '180:80/tcp' -p '1443:443/tcp' -v '/mnt/user/appdata/letsencrypt':'/config':'rw' -v '/mnt/user/appdata/letsencrypt/logs':'/var/log/letsencrypt':'rw' 'linuxserver/letsencrypt'

My bad... I thought "Nginx is never starting up......" was the problem. So then... if the creation of the cert is failing, where do I look then?

Alright, then I know the problem is Nginx. In the mean while I tried a clean unraid install + letsencrypt on yet another system and there the exact same thing happend. Any idea on how to fix this error?

ah.. file.zip

et voila... letsencrypt.zip

Thanks for your reply! Hoewever it seems that this doens't work either... all the other docker containers work fine except the letsencrypt one... I tried it on two machines now and both give the same result.