Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

GamingADHD

Members
  • Joined

  • Last visited

  1. I made a new container, copied the v1.04 Palworld server files to /mnt/user/appdata, and deleted the appmanifest file. That all seems to have worked perfectly. I'm patched to v1.05 and off to the races. At this point, I'm thinking I'm just a doofus for not noticing /mnt/cache/ was a bad idea at install time. If so, I will acknowledge the failure. I will live in the failure. And I will let the failure make me stronger. Otherwise, I am definitely open to suggestions.
  2. Hey all, Been having this issue with the Palworld version for the last two big updates. When I restart the container to grab the latest version, I get a failure with this error message. Creating a new one sometimes fixes it, but today it didn't. Obviously making a new container and porting things over isn't the best, so I'd be curious on what the issue might be and if anyone else has dealt with this. Thanks! Connecting anonymously to Steam Public...OK Waiting for client config...OK Waiting for user info...OK Update state (0x0) unknown, progress: 0.00 (0 / 0) Error! App '2394010' state is 0x26 after update job. Unloading Steam API...OK Sometimes the error is 0x226. Previously my whole app got wiped out, but the backups and saves were safe, but this time it looks like it's still installed and just defaulting to the old version (v1.0.4.102642). I've got steamcmd in /mnt/user/appdata/ and palworld in /mnt/cache/appdata/, per the defaults from the container. Plenty of space in the array, so I don't think that's it.
  3. I've been getting this issue when trying to run Core Keeper the past few days. Haven't gotten it to work yet. Issue persists through upgrade to UnRaid 6.12.13 as well as reboots, spinning Docker down then back up, and numerous fresh installs. The image for V Rising, though, works perfectly fine and has no issues. I've used a ton of @ich777 's containers and they're the best. Any ideas? Error Code: /opt/scripts/start-server.sh: line 84: 153 Segmentation fault ${SERVER_DIR}/CoreKeeperServer -batchmode -logfile ${SERVER_DIR}/CoreKeeperServerLog.txt -world ${WORLD_INDEX} -worldname "${WORLD_NAME}" -datapath "${SERVER_DIR}/Save" ${GAME_PARAMS} 2 > /dev/null

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.