rawfuls

Just updated from 6.12.6 to 6.12.8 and can no longer load WebGUI locally nor externally. Logs indicate that webGUI has started and privoxy is listening. Where to start on this guy? Running on proxynet. EDIT: Solved! LAN_NETWORK under Edit was incorrect.

The rebuild was successful and the data seems to be intact, however Docker is unable to start. Service seems to be enabled on the settings side. EDIT: Maybe I jumped the gun here. Disabling Docker then re-enabling seems to have gotten the service to start.

Understood, so bring down the array, rip open and replace cables (as needed) and rebuild parity after I tell UnRAID that the drive is in fine shape. I did use the cheap(er) Amazon splitters from molex -> SATA (not the cheapest ones that cause fires). Any recommendations here for those LSI SAS and power cables? Maybe it's time I fix these bugs once and for all with quality components. Is the absolute latest version firmware for the LSI cards fine, or should I backdate?

Should I still move data, or just shut the server down, check connections, upgrade firmware and let parity emulate data still? If I still rebuild (by taking the drive out, moving contents to disk5), would I run the new permissions on all disks and all shares, or thinking not needed here?

Had a drive fail and get disabled. While I personally think it's probably a cable problem, I've learned to not shut down UnRAID right away and fuddle, as I want to get the data off before the drive and another drive fails with it (happened once.. that sucked..) So now, I'm running here with my diagnostic logs hoping somebody can jump in and see if they can find something I'm not seeing. I'm okay tossing out disk4 in my array, disk5 has lots of open space and I have a 4TB drive that just passed pre clear that I plan on throwing back into the array when this fiasco is resolved. I've also shut down all dockers, and stopped mover and any other auto-run plugins for the time-being as I was getting ready to use unBalance to move all disk4 onto disk5, until the attached message cropped up. "There are some permission issues with the folders/files you want to transfer 331 file(s)/folder(s) with an owner other than 'nobody' 329 file(s)/folder(s) with a group other than 'users' 0 folder(s) with a permission other than 'drwxrwxrwx' 540 files(s) with a permission other than '-rw-rw-rw-' or '-r--r--r--' You can find more details about which files have issues in the log file (/boot/logs/unbalance.log) At this point, you can transfer the folders/files if you want, but be advised that it can cause errors in the operation You are STRONGLY suggested to install the Fix Common Problems plugin, then run the Docker Safe New Permissions command" This is a new one for me so looking for some insight here. Should I go ahead and run the Tools > New Permissions command on all disks and shares, or just disk5? (disk4 doesn't show) Diagnostics attached, drive failed on March 6th at 4:59pm PST hoangserver-diagnostics-20220309-0100.zip

Getting a new error message that the server is outdated. Two of the players on the newer updated Minecraft version are having the issue whereas two players on the older (matching) version are fine. Is there a way to check the docker for updates? I'm on UnRAID 6.9.2 and docker shows the docker was last created 2 days ago (assuming, updated 2 days ago). EDIT: Sigh, should have checked. Docker > Advanced View (top right) > Force Update for docker container. This fixed it; thanks

I've gotta be completely missing something... Where is the openvpn config file? Am I modifying for each location.ovpn? Attaching an image of my dir for /config. This was setup per SpaceInvader's video.

This was it, thanks a ton @alturismo!

Seeing a variety of different issues, the latest being a 400 Bad Request The plain HTTP request was sent to HTTPS port. This happens when trying to access via https://192.168.1.180:444, too. Just prior I had a 502 Bad Gateway. Pulling my hair out trying to figure this out, I've got Sonarr/Radarr/Bazarr services working through LetsEncrypt with no issues. If anybody sees where I'm missing a variable, it'd be appreciated LetsEncrypt console can ping 'nextcloud' with no issues Docker Config: https://imgur.com/a/xzLs6x5 nginx default config: https://pastebin.com/hdd3YeZp subdomain config: https://pastebin.com/Vq1LGHbS nextcloud config: https://pastebin.com/xvvJCeCj Error: 400 Bad Request The plain HTTP request was sent to HTTPS port nginx/1.16.1