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.

Squirreljester

Members
  • Joined

  • Last visited

  1. I've already uninstalled and reinstalled the nvidia driver, but in the plugin it says: Nvidia Driver Version: 595.71.05 Open Source Kernel Module: No Installed GPU(s): NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. My syslog says my p2000 needs a 580.xx driver, which I had installed originally (580.142), but my Plex wouldn't start after the update because of a GPU passthrough error: Apr 29 20:35:25 <Redacted> rpc.mountd[23432]: Version 2.8.4 starting Apr 29 20:35:26 <Redacted> rc.nfsd: NFS server daemon... Started. Apr 29 20:35:30 <Redacted> webgui: Successful login user root from 192.168.15.178 Apr 29 20:35:39 <Redacted> kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 239 Apr 29 20:35:39 <Redacted> kernel: NVRM: The NVIDIA Quadro P2000 GPU installed in this system is Apr 29 20:35:39 <Redacted> kernel: NVRM: supported through the NVIDIA 580.xx Legacy drivers. Please Apr 29 20:35:39 <Redacted> kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more Apr 29 20:35:39 <Redacted> kernel: NVRM: information. The 595.71.05 NVIDIA driver will ignore Apr 29 20:35:39 <Redacted> kernel: NVRM: this GPU. Continuing probe... Apr 29 20:35:39 <Redacted> kernel: NVRM: No NVIDIA GPU found. Apr 29 20:35:39 <Redacted> kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 239 Apr 29 20:35:39 <Redacted> kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 239 Apr 29 20:35:39 <Redacted> kernel: NVRM: The NVIDIA Quadro P2000 GPU installed in this system is Apr 29 20:35:39 <Redacted> kernel: NVRM: supported through the NVIDIA 580.xx Legacy drivers. Please Apr 29 20:35:39 <Redacted> kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more Apr 29 20:35:39 <Redacted> kernel: NVRM: information. The 595.71.05 NVIDIA driver will ignore Apr 29 20:35:39 <Redacted> kernel: NVRM: this GPU. Continuing probe... Apr 29 20:35:39 <Redacted> kernel: NVRM: No NVIDIA GPU found. Apr 29 20:35:39 <Redacted> kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 239 Apr 29 20:35:40 <Redacted> kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 239 Apr 29 20:35:40 <Redacted> kernel: NVRM: The NVIDIA Quadro P2000 GPU installed in this system is Apr 29 20:35:40 <Redacted> kernel: NVRM: supported through the NVIDIA 580.xx Legacy drivers. Please Apr 29 20:35:40 <Redacted> kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more Apr 29 20:35:40 <Redacted> kernel: NVRM: information. The 595.71.05 NVIDIA driver will ignore Apr 29 20:35:40 <Redacted> kernel: NVRM: this GPU. Continuing probe... Apr 29 20:35:40 <Redacted> kernel: NVRM: No NVIDIA GPU found. Apr 29 20:35:40 <Redacted> kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 239 UPDATE: I just reinstalled the 580.142 driver and rebooted for the 4th or 5th time tonight, here's my Plex log: 026-04-29 20:50:44.232132 [info] Host is running unRAID 2026-04-29 20:50:44.249597 [info] System information: Linux f734ff530687 6.12.54-Unraid #1 SMP PREEMPT_DYNAMIC Tue Oct 21 15:58:46 PDT 2025 x86_64 GNU/Linux 2026-04-29 20:50:44.268255 [info] Image architecture: 'amd64' 2026-04-29 20:50:44.286609 [info] Application name: 'plexpass' 2026-04-29 20:50:44.306715 [info] Base image release tag: '2026032801' 2026-04-29 20:50:44.323069 [info] Application image release tag: '1.43.1.10611-1-01' 2026-04-29 20:50:44.345254 [info] PUID defined as '99' 2026-04-29 20:50:44.364620 [info] User 'nobody' already has UID '99', skipping usermod 2026-04-29 20:50:44.387828 [info] PGID defined as '100' 2026-04-29 20:50:44.408034 [info] Group 'users' already has GID '100', skipping groupmod 2026-04-29 20:50:44.424773 [info] UMASK defined as '000' 2026-04-29 20:50:44.445045 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data' 2026-04-29 20:50:44.467570 [info] Deleting files in /tmp (non recursive)... 2026-04-29 20:50:44.490980 [warn] TRANS_DIR not defined,(via -e TRANS_DIR), defaulting to '/config/tmp' 2026-04-29 20:50:44.515990 [info] Starting Supervisor... 2026-04-29 20:50:44,641 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2026-04-29 20:50:44,641 INFO Set uid to user 0 succeeded 2026-04-29 20:50:44,644 INFO RPC interface 'supervisor' initialized 2026-04-29 20:50:44,644 INFO supervisord started with pid 49 2026-04-29 20:50:45,647 INFO spawned: 'claim-script' with pid 111 2026-04-29 20:50:45,648 INFO spawned: 'start-script' with pid 112 2026-04-29 20:50:45,649 INFO reaped unknown pid 50 (exit status 0) 2026-04-29 20:50:45,653 DEBG 'claim-script' stdout output: [info] Env var 'PLEX_CLAIM' value not set and/or 'CLAIM_SERVER' not set to 'yes', skipping claim process. 2026-04-29 20:50:45,653 INFO success: claim-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2026-04-29 20:50:45,653 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 22862189155328 for <Subprocess at 22862190410256 with name claim-script in state RUNNING> (stdout)> 2026-04-29 20:50:45,653 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22862189091152 for <Subprocess at 22862190410256 with name claim-script in state RUNNING> (stderr)> 2026-04-29 20:50:45,653 INFO exited: claim-script (exit status 0; expected) 2026-04-29 20:50:45,653 DEBG received SIGCHLD indicating a child quit 2026-04-29 20:50:45,658 DEBG 'start-script' stdout output: [info] Env var 'PLEX_CLAIM' value not set and/or 'CLAIM_SERVER' not set to 'yes', skipping edit of Preferences.xml for claim process. 2026-04-29 20:50:46,658 INFO success: start-script entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2026-04-29 20:50:59,561 DEBG 'start-script' stdout output: Critical: libusb_init failed
  2. Just to follow up with this, using this driver made the Steam Headless work perfectly, including adding the options to the docker for it to use the GPU. Also my Plex server is transcoding super super fast, faster than I can even GPU-Status can even catch the status of most of the time.
  3. I ran the chown -R 1000:1000 /mnt/user/FoundryVTT command already, and it didn't help, the docker still starts and then stops with the same error. I also don't know what "change the docker user container to match the data." means. I've updated the docker settings with "--user 99:100" in the extra parameters and changes the repository to "felddy/foundryvtt:release" per your suggestions. I'm not sure how to proceed to resolve this issue.
  4. I'm getting this at the end of the log and the container won't stay running: Warning: Failed to open the file downloading.zip: Permission denied * Failure writing output to destination 0 220M 0 1360 0 0 10249 0 6:16:41 --:--:-- 6:16:41 10225 * Connection #0 to host r2.foundryvtt.com left intact curl: (23) Failure writing output to destination Entrypoint | 2025-08-28 17:26:18 | [warn] Download from presigned URL failed with exit code 23. Entrypoint | 2025-08-28 17:26:18 | [error] No valid cached release file found. Unable to proceed with installation.
  5. ok I downgraded my nvidia driver to 570.172.08 (I was on 575.64.03) and it appears to be working now with the GPU runtime added. I'm not sure what effect this will have on my Plex server transcoding. I will monitor.
  6. I'm having an issue adding my nvidia gpu. I'm adding it just as it shows in the documentations, and it is identical to how I have Plex set up to use my GPU, which works fine. When I add --runtime=nvidia it loads the drivers per the log, but I get these errors: 2025-08-05 02:23:53,225 INFO spawned: 'xorg' with pid 426 2025-08-05 02:23:53,272 WARN exited: xorg (exit status 1; not expected) 2025-08-05 02:23:55,234 INFO spawned: 'xorg' with pid 457 2025-08-05 02:23:55,280 WARN exited: xorg (exit status 1; not expected) 2025-08-05 02:23:58,221 INFO spawned: 'xorg' with pid 496 2025-08-05 02:23:58,267 WARN exited: xorg (exit status 1; not expected) 2025-08-05 02:24:01,272 INFO spawned: 'xorg' with pid 538 2025-08-05 02:24:01,320 WARN exited: xorg (exit status 1; not expected) 2025-08-05 02:24:02,321 INFO gave up: xorg entered FATAL state, too many start retries too quickly When I take out the runtime entry, Steam-headless webUI connects and gives me a login. It has to be that entry, but for whatever reason it is just not working like it's supposed to, and I don't know why.
  7. I removed the container, removed the folder, re-installed, and didn't touch anything, left everything defaults, and now it appears to be working. This means some setting I changed broke it, but I'm not sure what did it. Does the password variable in the config need to be default or should I change that to something specific to the container?
  8. I'm trying to get this to work. I can connect to the WebUI but when I click the connect button I get "Failed to Connect to server" message. I've looked through the thread but a lot of the solutions are years old, even the extra step of installing uinput on the project page is outdated. I've installed the app through Unraid, gave it a game library which it has installed it's files to so there's not a permission issue there. I have GPU passthough set up with the variable populated with my GPUID, --runtime=nvidia at the beginning in extra parameters. Is there additional steps I need to take to make this work outside of the instructions on the project page? I'm wondering about the password piece and possibly the timezone. I've tried to change the timezone to my own and I've tried leaving it default. I've also tried to put my own password in there, and I've kept the default, but I always get the same result.
  9. Any ideas what's going on? I had this docker up and running for over 6 months without an issue, then I noticed it was off and wouldn't start. I've even tried doing the extra parameters "--user 99:100" that I found earlier in the thread, but no luck. What can I do?
  10. dockerMan/templates-user.xml <?xml version="1.0"?> <Container version="2"> <Name>FoundryVTT</Name> <Repository>felddy/foundryvtt:release</Repository> <Registry>https://hub.docker.com/r/felddy/foundryvtt</Registry> <Network>bridge</Network> <MyIP/> <Shell>sh</Shell> <Privileged>false</Privileged> <Support>https://forums.unraid.net/topic/121065-support-silman-foundryvtt-felddy-docker-image/</Support> <Project>https://github.com/felddy/foundryvtt-docker</Project> <Overview>A secure, reliable, compact, and simple-to-use container for the Foundry Virtual Tabletop using felddy's Dockerhub images.&#xD; Felddy has the most robust docker image for FoundryVTT their image has over 10M downloads.&#xD; &#xD; You can get a Foundry Virtual Tabletop instance up and running in minutes using this container. This Docker container is designed to be secure, re liable, compact, and simple to use. It only requires that you provide the credentials or URL needed to download a Foundry Virtual Tabletop distrib ution.</Overview> <Category>GameServers:</Category> <WebUI>http://[IP]:[PORT:30000]</WebUI> <TemplateURL>https://raw.githubusercontent.com/silman/unraid_templates/master/foundry/foundry.xml</TemplateURL> <Icon>https://www.foundryvtt.wiki/fvtt-solid-512.png</Icon> <ExtraParams/> <PostArgs/> <CPUset/> <DateInstalled>1752594040</DateInstalled> <DonateText/> <DonateLink/> <Requires/> <Config Name="Game Data Path" Target="/data" Default="" Mode="rw" Description="Maps to container path /data. Path to persistent directory for st oring Config, Data, and Logs directories for Foundry to use." Type="Path" Display="always" Required="true" Mask="false">/mnt/user/FoundryVTT/</Con fig>
  11. I've done all the updates that have come up when it says there's one available. How do I check if it's v12 or v13 when it won't stay running anymore?
  12. I just started having a strange problem where the app isn't searching on it's own, and I can't click on the "automatic search" icon in the GUI. I also can't click the "Refresh and Scan" or "Search for Missing". What does work is clicking "Interactive Search", which brings up results, and it will let me select something to download. I just noticed that I also can't add any new shows. I hit the button to add the show, the button flashes, but then nothing happens. I can click on the button multiple times and nothing happens, and the show doesn't add. Any ideas what's going on? It worked up until a couple days ago.
  13. I just started getting this error out of the blue: FoundryVTT | 2025-07-15 15:40:50 | [error] A fatal error occurred while trying to start the Foundry Virtual Tabletop server: EACCES: permission denied, open '/data/Data/systems/README.txt' Error: A fatal error occurred while trying to start the Foundry Virtual Tabletop server: EACCES: permission denied, open '/data/Data/systems/README.txt'
  14. Support was able to re-issue my a new key and it worked. Strangely I had to go into the key management and re-link the key too. I didn't see that step in any of the instructions I read online.

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.