wes.crockett

Members
  • Posts

    74
  • Joined

  • Last visited

Everything posted by wes.crockett

  1. I'm moving to wherever you live... lol. I still can't even get fiber and I live in a really nice area of town where, pretty much, everyone would pay for it.
  2. Wait, your ISP was like "Oh, yeah, sorry, here's a dedicated IP to solve the issue"? What glorious ISP do you use?!?!
  3. They re-autofill every time I remove them. It's been running like that since launch somehow That said... THAT SAID... I stopped the container, blanked them out, started it and: but if i go back in to settings now, again, root shows up with some dummy pw... lol How do you even deal with us plebs? Thanks @ich777
  4. yes, put in your actual. be sure to stop the container, change the setting, then bring it back up. In the container config, did you tell it to auto-update public IP? If not, do so.
  5. OK, my turn... I have updated (and force updated) my Palworld server, enabled VALIDATE (and re-disabled it after saving) and yet my server is still showing 0.1.2.0. Is there a way, from within the docker console, to see the Palworld version?: Here is the log information on startup. Server has been stable since day 1.
  6. Odd, this config looks like it should work. Maybe try setting the router to only accept UDP instead of both UDP and TCP. I couldn't imagine that would matter... but maybe??
  7. Let's all take a moment to stand up at our desks, and applaud @ich777. Doing gamer god's work for all us plebs Seriously dude, thank you for what you do.
  8. You weren't kidding... that's a LOT of servers. I put in the ADMIN password I created and it said it didn't match. Trying the non-admin one next.
  9. I do now. I didn't do a ton of reading up prior to release (on those specifics at least). Not a big deal, I bought it on Steam now instead.
  10. I'm big dumb dumb. I missed it on my first look at the config file. As a side note, it looks like players who are using xbox live to play the game aren't able to join dedicated servers (like, there is no place to even see the dedicated servers.) Also, no cross play between xbox/xbox live and Steam. Really unfortunate limitation.
  11. Hey, where do you set the password? Also, from this and your edit, that's completely broken right now right?
  12. I had issues like this, downgraded, and the issues went away. I've been stable for 5 days now.
  13. When configuring, what do we put in for DOCKER_HOST and DOCKER_PORT when hosted on Unraid? Sorry if this is a super noob question
  14. Ever since downgrading to 6.12.3, I have had no issues with my system.
  15. It would help if I had auto-start enabled in disk settings.
  16. I just ran /sbin/reboot as a user script. Server rebooted fine but array didn't come back online on its own. Is that normal behavior when running /sbin/reboot? My thinking is trying nightly reboots to see if the issue persists every now and then. EDIT: I'm dumb... that just flat out reboots Linux. Is there a prebuilt script for safely rebooting Unraid in the proper order?
  17. I'm seeing several people mention downgrading and the issue going away... would this be worth pursuing to ensure it isn't the newest release resulting in the issue?
  18. Unknown. Sometime between 11pm and 630ish. I came in this morning and it was unusable. It became unusable overnight. I'm seeing several very similar threads. Going through them, looks like pretty identical symptoms. Hoping that, between all the threads, some light can come as to what may be causing it.
  19. The log from the boot drive and the log on my cache drive aren't perfectly aligned, so I uploaded both... either way: I came into my office this morning to find the server totally unresponsive again. Had to perform a hard reboot. Logs attached. syslogs.zip
  20. I'm all about the common mistakes... like this one... that I made. Thanks. So this will write them to my boot drive too then (being the flash drive)? Sounds good.
  21. Any updates with c6 update? I'm running an old Xeon machine and having similar issues.
  22. Hey @JorgeB, I should be seeing logs to the directory I specified, correct? I'm not seeing any generated at this point even though logging is enabled.
  23. I turned it on last night. I THINK I have it set up correctly. Thank you.
  24. As the title says, on Saturday, the server started acting up. I could access the unraid UI but not really od anything. Rebooting resulted in nothing. I could access the terminal but I couldn't get the reboot command to work there either. CPU was pegged at 100%. I had to hard boot it. Parity check passed fine after brining the array online. Tonight, I came home after a few hours away and I couldn't even access the unraid UI through web browser and I couldn't ping the box (so obviously I couldn't ssh in either.) iDrac showed no issues of note (but I could reach the idrac on the box) and I couldn't wake up the box to get direct video out. Naturally, I'm leaning to a dreaded hardware issue. I've attached Unraid logs... Hopefully someone more well versed than I can see a glaring issue in here? Syslogs attached kuiper-diagnostics-20230926-2310.zip
  25. I have just started encountering this issue as well. On Saturday, and tonight, I have had to hard-reboot the server... On Saturday, i was able to access the web UI but nothing would work (taking down the array, rebooting, etc) Tonight, I couldn't even ping the box (which is very scary of course) but iDrac (dedicated LAN port) still worked. Plugging in a mouse and keyboard w/ monitor and I couldn't get it to wake up at all. Logs attached, will enable persistent logging. FYI, Running on a Dell Poweredge T420. kuiper-diagnostics-20230926-2310.zip