-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Frequently Asked Questions
Follow the instructions on https://syncommunity.com
I'm seeing a 400 Bad Request, The browser (or proxy) sent a request that this server could not understand
http://packages.synocommunity.com is the repository URL, and is meant for your NAS only.
Visit https://synocommunity.com for details about the repository and the available packages.
- Look up the architecture for your model with Architecture per Synology model;
- Look up the package on the package overview, and check if your architecture is mentioned in the package details.
If an architecture is not listed, that is probably on purpose. Some packages cannot be compiled for certain architectures. PPC-based architectures (ppc* and qoriq) are known for this.
Search open and closed issues on the bugtracker to verify the question has not been asked before. If not, open an issue. Follow the instructions in CONTRIBUTING.
- We publish packages for the latest major DSM version (currently DSM 5) by default;
- Upon request, and based on best effort, we publish packages for the previous DSM major version (currently DSM 4.3).
- For DSM4.2 and older, we might not be able to provide packages. You can try to build the packages yourself.
A package should be available for my model and DSM version, but I can't find it in Package Center. What do I do?
- If the package is listed as a
beta
package on https://synocommunity.com/packages, make sure you have turned onYes, I want to see beta versions
in the Package Center settings; - If you're using the search bar in Package Center, then select the drop-down arrow next to the magnifying glass, and set the value to
Community
.
Set the trust level in the Package Center settings to Synology Inc. and trusted publishers
. See How do I add the SynoCommunity repository to my NAS.
Follow the instructions here: CONTRIBUTING.
The icon is shown to the user admin
by default. To show it for other users, log in as a user with administrator privileges. Then choose one of the following methods:
- Open Control Panel > Privileges. Select the application and activate the checkbox for the users who should see the icon;
- Open Control Panel > User. Select the correct user, click
Edit
and open the tab Applications. Activate the checkbox for the application for which the icon should be shown.
Notes:
- The icon does not affect access permissions;
- Packages that are command-line only will not show an icon.
Make sure you have set the path correctly, or use the full path to the binary. For some packages, we add a symlink to the most-used binary in /usr/local/bin
, which is on $PATH by default.
Examples:
PATH=/usr/local/git/bin:$PATH git
/usr/local/git/bin/git
- Home
-
Packages
- Adminer
- Aria2
- Beets
- BicBucStriim
- Borgmatic
- cloudflared
- Comskip
- Debian Chroot
- Deluge
- Duplicity
- dnscrypt-proxy
- FFmpeg
- FFsync
- Flexget
- Gstreamer
- Google Authenticator
- Home Assistant Core
- Jellyfin
- Kiwix
- [matrix] Synapse homeserver
- MinIO
- Mono
- Mosh
- Mosquitto
- Node-Exporter
- Radarr/Sonarr/Lidarr/Jackett
- SaltStack
- SickBeard Custom
- SynoCLI-Disk
- SynoCLI-Devel
- SynoCLI-File
- SynoCLI-Kernel
- SynoCLI-Misc.
- SynoCLI-Monitor
- SynoCLI-NET
- Synogear
- Concepts
- Development
- Resources