Scorchmuffins

I'm back up and running. I'm still not sure what was wrong though. I compared my network.cfg for the backup and the working clean USB and they matched exactly. As a last resort I made the backup again but used DHCP instead of static settings and it worked. It even booted to the ip was trying to assign. If I hadn't made the USB and checked the settings a dozen times I'd think that I screwed up a setting. I noted my array drives this time so I will have that if a future crisis arises. Thank you for your help.

So, I can just compare my backup to a "clean" USB and delete everything that isn't there except the specific things you mentioned. I'll give that a try and see how it goes.

I'm having some issues with my server that have me stumped. A couple of days ago my dashboard was unreachable remotely. I could still access shares from the PC and containers were still functioning so I kind of put off looking into it. The next day I lost access to the shares from my PC, containers were still functioning. Today I finally lost access to the containers. I decided to reboot the server to see if that would resolve the issue. Upon rebooting I was thrown into the bios with "no boot device". Dead USB drive. The server has been up and running for about a year and my understanding is that everything is in ram once booted up so the USB could have died any time in the past year and may be completely unrelated. I had a rather old backup of my USB but figure it was better than nothing so I used the Unraid tool to create a new USB from the backup. Server boots up and is at the login prompt so I got back to my pc. Still can't connect remotely, pings time out. I log into my network and the sever isn't showing up. Tried the second network port and still not there. I then decided to make a new/clean boot USB just to rule things out. The new USB boots and the server shows up when pinged. I didn't do anything beyond that because I didn't want to risk my data if possible. Anyone have any thoughts as to what is going on? I've made zero additions or changes in several months so I'm not sure what has gone wrong all of the sudden. I used the same network settings on the original, the backup and the clean USB. I'm not using any proxies or anything. I'd be ok with starting fresh with the clean USB but being the idiot I am I didn't note which of my drives were which so importing my existing array might be a bit of a roll of the dice? I'm a Linux/Unraid noob and did all my containers and stuff from tutorials so I have no idea what the best way to proceed is. Thanks for any help, it is greatly appreciated.

I wasn't able to connect using either my LAN or WAN ips, I tried adding the server through Steam as well as manually in game. The only settings I changed were the steamcmd and game file locations. I was confused because everything seemed to be working. I ended up removing the container and reinstalling, steam still doesn't see it when I try to add it via game servers, but I can manually connect from within the game now. I'll call that a win, I guess maybe something weird happened on the first install. Thank you for working on these containers and supporting them.

I've got an error with my V-Rising server, hopefully someone can help me out. The server appears to be running and is generating autosaves according to the logs but I'm unable to connect to it or even ping it. The error I'm seeing is "Curl error 7: getsockname() failed with errno 10022: Invalid arguments". I've got a couple of other game servers running but this one is the only one giving me trouble. Any ideas would be greatly appreciated.