Hi, Currently just testing Plex install got this in the log: Container sb-plex Creating Container sb-plex Created Container sb-plex Starting Error response from daemon: error gathering device information while adding custom device "/dev/dri": no such file or directory
23 replies
tomspark wrote:
No problem — the claim token gets you there without needing the same-network bit. Quick job, but the token expires after 4 minutes, so do these back-to-back: 1. In a browser signed into your Plex account, go to https://plex.tv/claim and copy the code (it starts with claim-). 2. Right away, open /opt/sparkbox/.env and add this line, pasting your code: PLEXCLAIM=claim-xxxxxxxxxxxx 3. Save it, then run: sudo sparkbox up Plex restarts, sees the token, and claims the server to your account — refresh Plex and it should show up. If you were a bit slow and it doesn't take, the token just expired: grab a fresh one from plex.tv/claim and redo steps 2-3. Once it's claimed you can delete that PLEXCLAIM line if you like.
tomspark wrote:
Hey Seez — you didn't do anything wrong, this one's on us. Plex is trying to grab a graphics chip to speed up video, but this box doesn't have one Docker can see, so it refuses to even start. You don't need that chip to run Plex, so we can just tell it to skip it. Paste this one line and Plex should come up: sudo sed -i '\- /dev/dri:/dev/drid' /opt/sparkbox/modules/plex/docker-compose.yml && sudo sparkbox up When it finishes, open Plex at port 32400 (http://your-box-ip:32400/web). A proper fix so nobody has to touch that file is on the way.
Seez wrote:
After running that command, the container message line returns this: validating /opt/sparkbox/modules/plex/docker-compose.yml: services.plex.devices must be a array
tomspark wrote:
Ah, that's on me — deleting that line left the section half-finished, which is what it's complaining about now. Nothing's broken, one more quick paste sorts it. This swaps that section for an empty one so Plex stops looking for the graphics chip: sudo sed -i 's|^ devices:.| devices: []|' /opt/sparkbox/modules/plex/docker-compose.yml && sudo sparkbox up When it finishes Plex should come up — open it at port 32400 (http://your-box-ip:32400/web).
Seez wrote:
Hmm weird, I get the same error even after pasting that line 😊 Will take another look at it later tomorrow, thanks for the troubleshooting so far.
Seez wrote:
Your comment(s) got deleted twice by moderation it seems. Can you repost it?
tomspark wrote:
Ah — that comment was an early workaround I pulled because we replaced it with a proper fix, so you don't need any of that file-editing anymore. Good news: the real fix is already shipped. Plex was refusing to start because it looked for a graphics chip your box doesn't have, and the update makes it skip that automatically. Just run these two: sudo sparkbox update sudo sparkbox up The update also tidies up the file my earlier commands touched, so it puts everything back to a clean state. Give it a minute, then open Plex at port 32400 (http://your-box-ip:32400/web) — it should come right up with no manual edits. If anything's still stuck after that, paste the new log and I'll jump back in.
Seez wrote:
So I got Plex installed as Clean Slate. However I got this: No server to claim? And the website only allowed me to login, no server token or anything to claim? How come?
tomspark wrote:
Nice, Plex is up now! This last bit is just the claim step being fiddly. Plex only lets you 'claim' a server when you open it directly from a device on the SAME network as your box. So on a computer or phone on the same home network as the box, open http://YOUR-BOX-IP:32400/web (not plex.tv) and sign in with your Plex account — it should then show your new server and walk you through naming it. If you only get a login screen with no server listed, you're most likely opening it from a different network or through a VPN, which hides the unclaimed server. If it still won't show up on the same network, tell me and I'll walk you through the claim-token method.
Seez wrote:
Yea it’s not showing up on the same network for some reason. I think I need the claim-token method :)
Seez wrote:
Thanks Tom, this did the trick! 😊
tomspark wrote:
Glad it's working! 😊 One quick heads-up so it doesn't surprise you later: that one-liner edits a file that a future SparkBox update can overwrite. So if Plex ever throws that same /dev/dri error again after an update, just run the same line and you're set. We're working on a permanent fix that handles it automatically so you won't have to touch it at all — I'll post when it's out.
Seez wrote:
Alright good to know, thanks 😊 Jellyfin is still my main, but at the moment just testing Plex too, just to see what the "hype" is all about lol.
Seez wrote:
Another big noob question again 😅 On my UGREEN nas nearly all files are hidden. How can I apply the same fix on the UGOS? (Sorry still new to this OS) I have also installed the File Manager in Sparkbox, but that seems to be just for Media (Movies, Series etc.) Any tips?
tomspark wrote:
Happy to help! One thing I can tell you for sure: SparkBox's File Browser is scoped to your data folder (media, photos, etc.) on purpose, so it won't show system or config files — that part's expected, not a bug. For everything else on the NAS you'd use UGREEN's own File Manager in UGOS. To point you at the exact fix though, I need a bit more: when you say nearly all files are hidden and 'the same fix' — what are you actually trying to get to (your media folders? SparkBox's config at /opt/sparkbox? something else?), and where did you see the fix you're referring to? Tell me that and I'll give you precise steps for UGOS.
Seez wrote:
I'm trying to get a Plex server claimed (since it didn't do the setup correctly again (no wizard)) so I guess I have to manually add-in the PLEXCLAIM line 😊 As for "all my files seem hidden": When I go to the native Files app in UGOS, I only see 1 "docker" folder (with nothing inside it) and no other folders at all. I know it's a bit different, but on my WSL SparkBox I could see all files easily etc. Hope that makes sense.
tomspark wrote:
Two things: Plex claim — yep, you've got it. Grab a code from plex.tv/claim, add one line to /opt/sparkbox/.env: PLEXCLAIM=claim-xxxxxxxx …then run sudo sparkbox up. Do it within ~4 minutes (the code expires fast). That claims the server without needing the wizard. On the 'hidden files' — that's expected on UGOS, not broken. UGREEN's Files app only shows your storage shares, not the system area where SparkBox installs (/opt/sparkbox), which is why you just see that empty docker folder and none of SparkBox's files. On WSL there's no such split, so you saw everything. To edit files like .env, use the terminal you installed SparkBox from rather than the Files app — which is exactly how you'll add that PLEXCLAIM line above.
Seez wrote:
Fair enough, so I guess I'll have to go with the Terminal, SSH in and run some commands, right? If yes, what are those commands? And is there no way to edit them in a GUI like in a "Files"-like app? 😂
tomspark wrote:
The normal GUI way to claim Plex is its own web wizard (open http://YOUR-NAS-IP:32400/web from a device on the same network) — but that's the exact thing not showing for you, which is why we're going the token route. There's no dashboard field for the claim token, so it's a quick terminal edit. (You can use the UGOS terminal or SSH — either works.) 1. Grab a code at plex.tv/claim (starts with claim-). 2. Run: sudo nano /opt/sparkbox/.env 3. Find the line PLEXCLAIM= (or add one at the bottom) and make it PLEXCLAIM=claim-yourcode. Save with Ctrl+O then Enter, exit with Ctrl+X. 4. Run: sudo sparkbox up Do steps 1-4 within ~4 minutes so the code doesn't expire. If step 2 says 'nano: command not found', tell me and I'll give you a one-liner that skips the editor.
Seez wrote:
Alright that worked, thanks :) Now I added the libraries in Plex (data/TV etc) but the files I already have downloaded are not showing up, did I do something wrong here? :)
tomspark wrote:
Glad the claim worked! For the missing files, two possibilities: First, the simple one: Plex only shows files that are actually inside the library folders you pointed it at (/data/TV, /data/Movies). If your downloads are still sitting in a downloads folder and haven't moved into TV/Movies, they won't appear — same import step as Sonarr/Radarr. But I also just found a real bug that might be your exact cause: Plex wasn't honoring a custom media-folder location (MEDIAROOT) the way Jellyfin does, so if your media lives somewhere other than /opt/sparkbox/data/media, Plex was pointed at the wrong (empty) folder. I've fixed it — ships next release. To tell which it is: do these same files show up in Jellyfin? And what does this print: grep MEDIAROOT /opt/sparkbox/.env
tomspark wrote:
Good news — that Plex media-folder bug I mentioned is now fixed and live in v1.6.156. Run sudo sparkbox update, then in Plex your library should pick up the files (as long as they're sitting in your /data/Movies, /data/TV etc. folders). If you'd set a custom media location, Plex will now read the same folder Jellyfin does. Give it a go and let me know if anything's still missing.
Seez wrote:
That update fixed it! Thanks again Tom 😊