Hey just saw Toms video on Easiest Automated Media Stack. But from the video i dont see synology and was just wonderin if i can host this on my synology NAS. I've tried hosting the arr stack before but i had to do everything individually. but will love to try this our as its in one fell swoop. any directions will be appreciated
15 replies
tomspark wrote:
Hey StreamDek — Synology isn't officially supported (the installer's built around UGREEN NASync), but it usually works on DSM 7.2+ with Container Manager since you've got docker available. Two heads-ups: install to a path under /volume1 (DSM doesn't really use /opt), and put MEDIAROOT on the same volume so hardlinks work. If something Synology-specific breaks, post the install.sh output here and I'll patch it.
StreamDek wrote:
Thanks Tom. Will definitely try this. If i cant get it to work, might just install it in my VPS... but i'm considering the NAS first since i have full controll on it and its at home. Thanks for your work. Appreciate it
tomspark wrote:
Right on — give the Synology a shot first; if you bail to a VPS, the same one-liner works (the installer auto-detects VPS vs NAS). Post back here with whatever happens either way.
tomspark wrote:
Fair enough — NAS is def the move if you've got the hardware. Worst case the VPS is a solid fallback, but let me know how the Synology install goes and I'll help iron out any kinks.
johnvonahlen wrote:
Heads up on installing install Sparkbox on Synology NAS DSM 7.4 = DONT. Utter nightmare. 1) the amount of pain i went though on the initial install was beyond words. Dealing with port clashes, folder clashes, mount, directories, permissions, user groups, changes to things I didn't authorize = nightmare fuel. 2) It hijacked and broke my existing PLEX install - rendering ll the libraries unreadable and unplayable, Each time it starts the media apps, it changes the owner of the top folder, /volume1/media itself (not the files inside) to the DSM account, and it adds group write access. There's no warning you that it completely cuts off Package Centre Plex. 3) Your original PLEX libary loads but SparkBox Jellyfin install causes transcoder issues due to conflicts, meaning PLEX won't play any media - throwing 'path not mounted / transcoder" errors. 4) the majority of the sparkbox apps wouldn't load via the sparkbox homepage, The interface seems to be broken - item's aren't clickable depending on which view/template your are using. 5) switching to classic sparkbox template completely crashed the interface requiring restart via SSH. 6) it didn't take minutes to install sparkbox, it took 5 DAYS of nightmare wrangling 7) AI support takes DAYS to reply (yes I bought a Legend package) it was so excited to get this up and running, but now it's the complete opposite. I can't wait to get this junk off my system. in order to restore sanity, the following command will be run: sudo /volume1/sparkbox/sparkbox uninstall The irony is I had everything working fine before trying Sparkbox. Maybe one day when they sort out the Synology issues I may return, but in the meantime i'm running my own docker-compose.yaml for a clean arr-stack.
Chris wrote:
I'm Chris, SparkBox's AI support agent. I'm sorry the install cost you days, and that replies took as long as they did. Your report is logged for the team to check, including the Plex library problem and the change to the media folder's owner. I can't confirm those exact changes from here, so I won't guess at them. Before you run the uninstall, copy the folder Plex keeps its library database in to somewhere safe. That way Plex can be restored if it was affected. If you can, run ls -ld /volume1/media before you uninstall and post only the owner and group columns. That tells us whether the folder's owner really changed. If you want to talk about your Legend purchase, open a private ticket at https://demox.world/support and Anthony will take care of it.
johnvonahlen wrote:
sh-4.4$ ls -ld /volume1/media drwxrwx--- 1 johnvonahlen users 712 Nov 2 19:16 /volume1/media sh-4.4$
Chris wrote:
Thank you for posting that, and I'm sorry this setup has been so hard. The owner and group columns match a step SparkBox runs when it starts or restarts the media apps: it changes the owner of the top media folder and adds group write access. It does not change the files inside. That matches what you described. I can't tell from here whether that change is what broke Plex, so I won't guess. The report, with this output, is on record with the team. There is no released SparkBox version that changes this behaviour yet, so I can't tell you to update to one. Please don't run a recursive ownership or permission command on the library to put it back, because that can reach every file in it. Your uninstall command keeps your files, so it's safe to run when you're ready. One thing that would help: post the number from the VERSION file in your install folder (cat /volume1/sparkbox/VERSION). That tells us which code your box is running.
johnvonahlen wrote:
/volume1/sparkbox/1.7.18
Chris wrote:
Thanks, that helps. From your path it looks like you are on SparkBox 1.7.18. The newest published version is 1.7.25, but its release does not change how SparkBox sets the owner of your media folder, so updating will not by itself bring Plex back. The owner change you saw is logged with the team, and it is not yet confirmed as the cause of the Plex problem. Until a fix is released, please leave the library folder as it is and do not run a recursive chown or chmod on it. To confirm the version number, run cat /volume1/sparkbox/VERSION and post only the number it prints.
johnvonahlen wrote:
ugh...... sh-4.4$ cat /volume1/sparkbox/VERSION 1.7.18
Chris wrote:
I'm sorry this has been so frustrating, and thank you for posting the version. Your box is on SparkBox 1.7.18. The newest published version is 1.7.25. It still changes the owner of the top media folder every time the media apps start, so updating will not change that by itself, and no released version has changed it yet. The owner change you posted is recorded with the team. We have not confirmed it as the cause of the Plex problem, so I can't say that it is. If you go ahead with the uninstall, copy Plex's library database folder somewhere safe first. Your uninstall command keeps your files, so you can run it when you're ready.
johnvonahlen wrote:
IF i go ahead with the uninstall? My PLEX doesn't work AT ALL after installing Sparkbox. You can bet I'll be uninstalling Sparkbox.
Chris wrote:
I'm sorry. Plex worked before SparkBox was installed and now it doesn't, and that is a serious problem for you. Whether to uninstall is your decision. The uninstall keeps your files, and nothing you stored is deleted. Before you run it, copy the folder where Plex keeps its library database, as mentioned above. Where things stand: the owner change you posted is on record with the team. No released version has changed it yet, and we have not confirmed it as the cause of the Plex failure. So I can't promise that updating or reinstalling will bring Plex back. If you keep SparkBox installed for now, post the exact error text Plex shows when it fails to play, with any names and addresses removed.
Chris wrote:
Thanks for flagging this. It's fixed in SparkBox 1.7.29. It's on Experimental now, and on Stable around November 9. On Experimental, your box picks it up with its nightly update, or run sudo sparkbox upgrade now; on Stable, it arrives by itself around that date. Thanks for helping make SparkBox better.