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.

darknavi

Members
  • Joined

  • Last visited

Everything posted by darknavi

  1. Me too! I'd love to jump into fediverse this way.
  2. You are correct, fixed. Thanks for finding that!
  3. FYI anyone that comes across this, I got an updated version of this app up in CA now. Still called "ArchiveTeam-Warrior" but by me, darknavi. It has a few extra params built in. New support thread:
  4. Template Repo: https://github.com/JakeShirley/unraid-templates/blob/main/archiveteam-warrior.xml Official Repos: https://hub.docker.com/r/archiveteam/warrior-dockerfile/ https://github.com/ArchiveTeam/warrior-dockerfile NOTE: This thread will be moved once my CA dev application is accepted.
  5. +1 to fixing this in the app template. It's trivial to add these variables to the config so it'd be nice if it was built in so the jobs automatically start.
  6. I updated the `VERSION` variable from "latest" to "1.23.3.4707-ebb5fe9f3" (I just looked through their tags which have Plex server versions, this is from ~2 weeks ago) and every thing seems better. Error spew in the docker/Unraid logs went away. Not sure what's up with latest PMS, but at least this works for now.
  7. Hey all! I am jumping on the bandwagon to report my Plex server seems to start up, but then crashes over and over again very often. In the docker logs I see this over and over again: libc++abi: terminating with uncaught exception of type soci::soci_error: Cannot begin transaction. database is locked ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.23.6.4810-15ce0e21a/PLEX MEDIA SERVER/8575f75a-9267-434f-35d880a7-f0e79b44.dmp Sqlite3: Sleeping for 200ms to retry Starting Plex Media Server. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. libc++abi: terminating with uncaught exception of type soci::soci_error: Cannot begin transaction. database is locked ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.23.6.4810-15ce0e21a/PLEX MEDIA SERVER/1bacac55-0edc-4204-144f91a3-3aecb0db.dmp Sqlite3: Sleeping for 200ms to retry Starting Plex Media Server. Any ideas?
  8. This worked for me to transfer over my torrents (along with adding the correct/same volume mapping(s)). Now to port over my RSS feeds!
  9. Ok, so I just tested it. Stopping and starting the server: - Corrupts the level.db file (server is no longer joinable, level file is a few MB) - Creates a level.db.backup file that DOES work if manually renamed Any ideas? Basically every time I restart the server I have to restore a backup.
  10. Last night my Valheim world got "corrupted" again after running CA Auto Update. Symptoms: - World file is small (under 1MB) - Cannot join server (server is still broadcasted to steam, joining in-game results in a black screen) - level.db file in backup is also corrupt - level.db.backup file in backup actually works (not sure who/where this file is being created) Any help would be appreciated. I am afraid to run this container much longer because it seems increasingly likely that I'll loose my progress. Is this a problem with the game sever software its self? Or has anyone found a way to fix this corruption/reset issue?
  11. Same here. Here are my findings for what happened in my situation: - Get online this morning (after shutdown, backup, update, restart) and I can't connect to the server - Server says online in Steam but Valheim pretty quickly gives a "disconnect" message with no prompt for password - Look for .old file on disk and it seems similarly sized and does the same thing (~16MB) - Download AppData backup from last night and apply database file (~16MB) and the server does the same thing - Apply AppData backup .db.old file (~48MB) and the server works! The only thing I can think is that the main world file got corrupted somehow and made the server refuse to start/let people join. Is there any way to get Valheim server logs in this container? I'd like to look around to see if I can see anything getting wonky. To clarify my findings, these are the sizes of my worlds in my AppData backups that lead me to believe my main save got currupted (perhaps as part of server shutdown): world.db - 17.4MB world.db.old - 46.6MB
  12. I awoke this morning to my cache being 100% full (which can lead to Plex DB corruption for me) with this error: I guess Mover wasn't working at all! Your fix got me back running. I guess I need to turn auto updates off for this plugin.

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.