joecool169

Okay, I'll try that. I rebooted and everything appears to have returned to normal. But when I tried to reboot the system would not shut down. It couldn't unmount /mnt/user, so I had to push the reset. It is currently running parity so I think I'll let that finish.

I think I have cache drive issues. I was trouble shooting a docker container that I could not get to run. After trying many things I went to tools and ran docker safe perms. After that nothing worked right in docker. I stopped the docker service and have not been able to get it to start again. edit** Extended test has been running for 4 hours- joeserver-diagnostics-20220615-1940.zip

I figured this out on my own, I went to unraid settings, stopped docker, and then checked the box for custom data network br0

It seems like I have all my issues sorted out. Changing these network settings you suggested fixed the network issues. Deleting and reinstalling the nextcloud container fixed my issues there - still not sure what was wrong with it And my usb flash was failing for the 3rd time. Not sure why these do not last, first one was a cheap micro center one, the last 2 were Samsung's But now I can not choose br0 as a network in my docker container configs and therefore can't select a custom ip address for pihole.

I am going to link to the thread I created yesterday because I think most of the information about this problem is available there. Network Problems I really feel like this is still an issue with Unraid's networking. I have always had trouble with unraid's networking and I am not sure why.

Firefox can access nextcloud @HTTPS://172.18.0.4:443 but nothing can access it from HTTPS://192.168.7.10:444. Why is this? I wish I understood better. I'm still trying to learn.

I do not know Linux that well, but I can tell you changing the network settings in unraid is almost guaranteed to cause the system not to boot. Also seems to sometimes cause other various issues, like the webui going from dark to light without me changing the setting. In any case, I'm using eth0 now with bonding disabled. Should I start a thread in docker containers about why I still can't access nextcloud docker? It sure feels like a network issue.

YES

So step by step here is what I did. Stop docker Remove bond wait 20 minutes - server never came back on network plug keyboard and monitor into server - won't wake up hit reset button - choose unraid gui from boot menu local host unable to access - wait 15 minutes - started working switch eth 2 and eth 0 in unraid gui reboot into gui wait 10 minutes for it to work again - check network access on unraid ip - working reboot to no gui - unraid never got an ip address - had a 169.xxx something address type reboot got usb error reboot again - everything works - still no access to nextcloud webgui

Also EVERYTIME I change any network setting this happens! Sent from my iPhone using Tapatalk

Bonding is off and I now have no access to my server even in the unraid gui itself. Local host unable to connect. If I even look at the network setting in unraid it falls apart. Always been this way. Sent from my iPhone using Tapatalk

So I have been struggling with some very strange issues. Things like docker containers becoming inaccessible through the webui. I recently spent 2 1/2 days trying to get wordpress docker to work. At 1 point my internal usb adaptor seemed to fail. I had some strange issues like unraid seemed to lose some of it's settings. For example I refreshed the unraid gui and I was no longer in dark mode. Many many other things acted strange. When I attempted to reboot the server could not find the usb flash. So I moved the flash to a port on the back of the motherboard and most things have seemed fine since. But tonight I decided to try and troubleshoot my nextcloud docker container. With the help of smdion in the discord we figured out that Unraid has some very strange network things going on. So I'll attach a diagnostic. If I can answer any more questions please lmk. The wordpress docker is hosting the website for my small business which I prefer to keep active as much as possible. joeserver-diagnostics-20220606-2051.zip

I'm wondering what all this means? It pops up in logging every 30 seconds.

I'm having this untrusted certificate issue with nextcloud. Just started today for me as well.