imit8r

Oh nice, well, this definitely explains the issues I have been having.

I don't recall exactly when this started, but it seemed to coincide with the 6.9 RCs or Betas, though it likely was just coincidence. I have been getting frequent drive faults, warnings and just outright failures. Every time, as far as I can tell the drives have shown as passed on the subsequent SMART diagnostics. The first few were limited to one of the cache drives dropping out, and causing the cache to be inaccessible, which is where I had all my appdata folder etc. Since then I moved my appdata and VM stuff to an unassigned NVME drive. Based on the errors at the time I suspected that I had a bad SATA cable. The cables I had were mostly from many previous PC builds and I really didn't know how old they were so I replaced most of them with new. I have my drives spread across 2 controllers. Most the array drives are on my LSI controller. The cache and Parity drives are on the motherboard's built in SATA controller. Since changing the cables I continue to have drive faults. The faults are not limited to the onboard controller only, in fact, I think I have now had a fault on just about all the drives. This setup is mostly new (aside from some of the drives). I built the whole thing about a year ago now, but have been slowly adding more storage etc as needed. Attached is the zip file from diagnostics. Any/all help would be greatly appreciate as I am kind of at a loss as to where to proceed next. ted-diagnostics-20210321-0832.zip

I am trying to get the built in voice chat to work with foundry. After some tinkering I was able to follow some of the guides associated with this on foundry's site. I still can't make it work, and I am pretty sure it has something to do with the certs. I tried mounting the cert directory from swag in the foundry docker. When I try pointing the foundry setup for where the certs are it can never find them. Not sure what I am doing wrong, but I would love some help.

I had this same problem. My buddy who also runs a similar setup managed to get it working by commenting out the lines in the nginx proxy-conf file for Foundry that looks like this: # These are important to support WebSockets proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; After I did that and restarted swag/letsencrypt every thing worked like normal. I think it has something to do with cloudflare. I recently switched configs to use cloudflare's dns authentication.

I grabbed a direct copy of a friend's server files. I first ran it on your other minecraft server docker. The actual minecraft server seems to run just great. The MineOS web interface only stops responding once the minecraft server is fully up (or at least roughly then, hard to tell for sure). I checked to make sure that the world and server names have no spaces in them. I did some testing earlier to see how some of the stuff works before I imported my friend's server, and it seems to run just fine (the MineOS part) with a fresh server. I am at a loss for what I can test, or how to begin figuring out what the cause is.

Firstly, I am still quite new at this whole UNRaid thing, but I love all the work you have done. I know this is likely a stretch. I installed the mine-os docker, and the server I imported runs just fine. BUT, as soon as the server comes online the web page for monitoring the mine-os thing stops working. The container is still running, I can open the console and see the logfile chugging along for the minecraft server, but the web interface just doesn't respond. It is probably one of the mods or some setting of the actual server, since it is heavily modded. I just don't really have any idea where to start to figure this out. Any help would be appreciated.