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.

NoBigCat

Members
  • Joined

  • Last visited

  1. Downgrading and Upgrading unraid fixed the 'plugin: run failed returned 127' error it for me. I upgraded straight to unraid 7.0.1 and skipped 7.0. I downgraded, then upgraded to 7.0, then to 7.0.1. I thought It was because I skipped over 7.0. But if you say you are on 7.0. That means the act of downgrading then having unraid run the update and upgrading fixed the issue for me .
  2. Posting this here aswell, I had the same issue, I upgraded straight to 7.0.1 without upgrading to 7.0 first. This is why the issue was happening for me. I downgraded, upgraded to 7.0 ,got a popup to apply a patch (Unraid Patch),applied it, then upgraded to 7.0.1. The issue was fixed then. edit: It could have just been the act of having it re-update unraid that fixed it, but either way this is what fixed it for me.I don't think the patch was necessary for this fix for me, but I am just saying exactly what I did.
  3. I had the same issue, I upgraded straight to 7.0.1 without upgrading to 7.0 first. This is why the issue was happening for me. I downgraded, upgraded to 7.0 ,got a popup to apply a patch (Unraid Patch),applied it, then upgraded to 7.0.1. The issue was fixed then. edit: It could have just been the act of having it re-update unraid that fixed it, but either way this is what fixed it for me.
  4. Mine broke, after the update. I ran binhex's db repair script /home/nobody/dbrepair.sh in the container and that fixed it. Others rolled back their DB from a backup and that fixed it for them. note: I don't remember what my error was, the logs have overwritten it now. Also in the script type y instead of yes. I was typing in yes and it wasn't working lol.
  5. Nothing changed seems to work just fine with 6.11.1 like it did in 6.11 For me all I did was install Intel GPU Top from community apps Install Jellyfin ( I'm using Jellyfin-AMD-Intel-Nvidia )( it grabs from jellyfin/jellyfin ,i was using nvidia before) Set the Intel GPU value to /dev/dri ,or just add a device name it Intel GPU and value /dev/dri In Jellyfin under admin>playback I changed the transcode to intel quicksync, made sure to checkmark enable hardware encoding. I have all the formats check marked ,I semi remember looking at what the 12th gen igpu supported.(could be wrong on this, so double check for yourself). Also have tone mapping enabled ( not the vpp) I dont have any files that need it so haven't really messed with tone mapping. or looked to understand what the difference is between the two. I must have enabled for nvidia and left it at that. Maybe the vpp is the right choice? Saved and that's it for me it worked after that. To check if its using intel I play a video, lower the quality so it has to transcode, then open up a ssh to unraid and use the command intel_gpu_top and see if it's using it.

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.