Jump to content
XPEnology Community

Synology Community Package Sources (UPDATE 2024)


Schnapps

Recommended Posts

  • 5 months later...
  • 1 month later...

Hi All,

 

i added all known sources together in this site together with uptime monitoring.

please let me know if i miss any sources or you have some updates and i will update them.

 

just thought we need something a bit more easy & user friendly hope i managed to do so.

 

more info here: http://dottoremoe.com/synology-package- ... e-monitor/

 

cheers

.docmoe.

Link to comment
Share on other sites

I'm posting this here for my own future reference, and to help anyone that needs a fast and reliable method of getting the list of feeds added to their "Package Center"

 

docmoe's site is helpful to determine if the site is reachable, but doesn't help to determine if it is still a working SPK repo,

so I added that list to my own and filtered out all the sites that I had trouble connecting to, and resulted in a feeds file that can easily be added to any syno box, quickly and painlessly.

 

the feeds file is currently stored in /usr/syno/etc/packages in DSM 5

if you're just installing your box for the first time, copy the text below into a file called "feeds" and put it into the /usr/syno/etc/packages directory

 

FILENAME: /usr/syno/etc/packages/feeds

 

CONTENTS:

[{"feed":"http://cbo.netau.net/synopackages/","name":"http://cbo.netau.net/synopackages/"},{"feed":"http://cytec.us/spk/","name":"http://cytec.us/spk/"},{"feed":"http://e-remonty.info/spkrepo/packages","name":"http://e-remonty.info/spkrepo/packages"},{"feed":"http://ggteknikus.tk/sspks/","name":"http://ggteknikus.tk/sspks/"},{"feed":"http://packages.jdel.org/","name":"http://packages.jdel.org/"},{"feed":"http://packages.jdel.org/","name":"http://packages.jdel.org/"},{"feed":"http://packages.mdevries.org","name":"http://packages.mdevries.org"},{"feed":"http://packages.mertymade.com/","name":"http://packages.mertymade.com/"},{"feed":"http://packages.missilehugger.com/","name":"http://packages.missilehugger.com/"},{"feed":"http://packages.page81.net/","name":"http://packages.page81.net/"},{"feed":"http://packages.pcloadletter.co.uk/","name":"http://packages.pcloadletter.co.uk/"},{"feed":"http://packages.quadrat4.de/","name":"http://packages.quadrat4.de/"},{"feed":"http://packages.synocommunity.com","name":"http://packages.synocommunity.com"},{"feed":"http://packages.synocommunity.com/?beta=1","name":"http://packages.synocommunity.com/?beta=1"},{"feed":"http://pcloadletter.comlu.com/","name":"http://pcloadletter.comlu.com/"},{"feed":"http://pvr.unzureichende.info/synology","name":"http://pvr.unzureichende.info/synology"},{"feed":"http://repo.synozwave.com/","name":"http://repo.synozwave.com/"},{"feed":"http://spk.naefmarco.ch/spkrepo/packages","name":"http://spk.naefmarco.ch/spkrepo/packages"},{"feed":"http://spk.naefmarco.ch/spkrepo/packages/","name":"http://spk.naefmarco.ch/spkrepo/packages/"},{"feed":"http://spk.nas-mirror.de/","name":"http://spk.nas-mirror.de/"},{"feed":"http://spk.nas-mirror.de/spkrepo/packages","name":"http://spk.nas-mirror.de/spkrepo/packages"},{"feed":"http://spk.synologyitalia.com","name":"http://spk.synologyitalia.com"},{"feed":"http://spk.unzureichende.info/","name":"http://spk.unzureichende.info/"},{"feed":"http://subtitlessh.no-ip.biz/repo_spk/","name":"http://subtitlessh.no-ip.biz/repo_spk/"},{"feed":"http://synobox.fr.nf/synopackages/","name":"http://synobox.fr.nf/synopackages/"},{"feed":"http://synobox.fr.nf/synopackages/beta.php","name":"http://synobox.fr.nf/synopackages/beta.php"},{"feed":"http://synology.acmenet.ru","name":"http://synology.acmenet.ru"},{"feed":"http://packages.mdevries.org/","name":"http://packages.mdevries.org/"},{"feed":"http://synology.sysco.ch","name":"http://synology.sysco.ch"},{"feed":"http://synology.w01.eu","name":"http://synology.w01.eu"},{"feed":"http://synopkg.superzebulon.org/spkrepo/packages","name":"http://synopkg.superzebulon.org/spkrepo/packages"},{"feed":"http://synopkgs-garble.rhcloud.com/","name":"http://synopkgs-garble.rhcloud.com/"},{"feed":"http://update.10trum.de/packageupdate/getpackages.php","name":"http://update.10trum.de/packageupdate/getpackages.php"},{"feed":"http://www.brigittehelsen.be/plexconnect/ ","name":"http://www.brigittehelsen.be/plexconnect/ "},{"feed":"http://www.christoph-papke.de/spkrepo/spkrepo/packages/","name":"http://www.christoph-papke.de/spkrepo/spkrepo/packages/"},{"feed":"http://www.cphub.net/index.php/getpackages.php/","name":"http://www.cphub.net/index.php/getpackages.php/"},{"feed":"http://www.need-soft.com/packages/index.php/spkrepo/packages","name":"http://www.need-soft.com/packages/index.php/spkrepo/packages"},{"feed":"https://synocommunity.com/packages","name":"https://synocommunity.com/packages"},{"feed":"https://www.christoph-papke.de/spkrepo/spkrepo/packages","name":"https://www.christoph-papke.de/spkrepo/spkrepo/packages"}]

 

If you already have your own list, you may want to compare with this one.

 

A few other things to note about these feeds. The first time you get the feeds your package center may choke and complain about a dropped connection, if you 'tail /var/log/messages' you'll see a few sites that might be experiencing difficulties.

 

I eliminated and corrected many of the sites that are incorrect or down forever, but there are a few that I either left because it looked like a temporary problem, or were left because I couldn't determine the actual site with problems via /var/log/messages.

 

I left a couple that looked like they might just be having temporary problems.

 

What's left is a list of the most up to date spk repositories that I could pull together quickly.

 

Below is information if you need to edit the file. Chances are if you're installing this file, you wont need to read it.

 

Note the formatting is feed url follwed by the feed name. I left the name the same as the feed, but you can change them to whatever is appropriate for each site.

file begins with a [ and ends with a ]

each feed is surrounded by { }

Each feed is separated by a single comma " , "

it is all on one single line.

Example file:

[{"feed":"http://packages.synocommunity.com/?beta=1","name":"http://packages.synocommunity.com/?beta=1"},{"feed":"url to site","name":"nick name or aka or other label for the site"},{and so on...}]

Link to comment
Share on other sites

I'm posting this here for my own future reference, and to help anyone that needs a fast and reliable method of getting the list of feeds added to their "Package Center". Basically adding a feed list of the spk repositories all in one file that can be quickly uploaded.

 

docmoe's site is helpful to determine if the site is reachable, but doesn't help to determine if it is still a working SPK repo,

so I added that list to my own and filtered out all the sites that I had trouble connecting to, and resulted in a feeds file that can easily be added to any syno box, quickly and painlessly.

 

the feeds file is currently stored in /usr/syno/etc/packages in DSM 5

if you're just installing your box for the first time, copy the text below into a file called "feeds" and put it into the /usr/syno/etc/packages directory

 

As Loderunner pointed out (Thank you, btw), this is JSON source. Notepad++ was able to help me to reformat the text to something more easily read by a human. Pasted below

I haven't tested in the human readable format, but if this file is read by anything that understands JSON, the human readable formatting shouldn't be a problem. The default formatting is one long line.

 

DSM 5 location (Same in previous versions?) b]/usr/syno/etc/packages/feeds[/b]

[{
"feed": "http://cbo.netau.net/synopackages/",
"name": "http://cbo.netau.net/synopackages/"
},
{
"feed": "http://cytec.us/spk/",
"name": "http://cytec.us/spk/"
},
{
"feed": "http://e-remonty.info/spkrepo/packages",
"name": "http://e-remonty.info/spkrepo/packages"
},
{
"feed": "http://ggteknikus.tk/sspks/",
"name": "http://ggteknikus.tk/sspks/"
},
{
"feed": "http://packages.jdel.org/",
"name": "http://packages.jdel.org/"
},
{
"feed": "http://packages.jdel.org/",
"name": "http://packages.jdel.org/"
},
{
"feed": "http://packages.mdevries.org",
"name": "http://packages.mdevries.org"
},
{
"feed": "http://packages.mertymade.com/",
"name": "http://packages.mertymade.com/"
},
{
"feed": "http://packages.missilehugger.com/",
"name": "http://packages.missilehugger.com/"
},
{
"feed": "http://packages.page81.net/",
"name": "http://packages.page81.net/"
},
{
"feed": "http://packages.pcloadletter.co.uk/",
"name": "http://packages.pcloadletter.co.uk/"
},
{
"feed": "http://packages.quadrat4.de/",
"name": "http://packages.quadrat4.de/"
},
{
"feed": "http://packages.synocommunity.com",
"name": "http://packages.synocommunity.com"
},
{
"feed": "http://packages.synocommunity.com/?beta=1",
"name": "http://packages.synocommunity.com/?beta=1"
},
{
"feed": "http://pcloadletter.comlu.com/",
"name": "http://pcloadletter.comlu.com/"
},
{
"feed": "http://pvr.unzureichende.info/synology",
"name": "http://pvr.unzureichende.info/synology"
},
{
"feed": "http://repo.synozwave.com/",
"name": "http://repo.synozwave.com/"
},
{
"feed": "http://spk.naefmarco.ch/spkrepo/packages",
"name": "http://spk.naefmarco.ch/spkrepo/packages"
},
{
"feed": "http://spk.naefmarco.ch/spkrepo/packages/",
"name": "http://spk.naefmarco.ch/spkrepo/packages/"
},
{
"feed": "http://spk.nas-mirror.de/",
"name": "http://spk.nas-mirror.de/"
},
{
"feed": "http://spk.nas-mirror.de/spkrepo/packages",
"name": "http://spk.nas-mirror.de/spkrepo/packages"
},
{
"feed": "http://spk.synologyitalia.com",
"name": "http://spk.synologyitalia.com"
},
{
"feed": "http://spk.unzureichende.info/",
"name": "http://spk.unzureichende.info/"
},
{
"feed": "http://subtitlessh.no-ip.biz/repo_spk/",
"name": "http://subtitlessh.no-ip.biz/repo_spk/"
},
{
"feed": "http://synobox.fr.nf/synopackages/",
"name": "http://synobox.fr.nf/synopackages/"
},
{
"feed": "http://synobox.fr.nf/synopackages/beta.php",
"name": "http://synobox.fr.nf/synopackages/beta.php"
},
{
"feed": "http://synology.acmenet.ru",
"name": "http://synology.acmenet.ru"
},
{
"feed": "http://packages.mdevries.org/",
"name": "http://packages.mdevries.org/"
},
{
"feed": "http://synology.sysco.ch",
"name": "http://synology.sysco.ch"
},
{
"feed": "http://synology.w01.eu",
"name": "http://synology.w01.eu"
},
{
"feed": "http://synopkg.superzebulon.org/spkrepo/packages",
"name": "http://synopkg.superzebulon.org/spkrepo/packages"
},
{
"feed": "http://synopkgs-garble.rhcloud.com/",
"name": "http://synopkgs-garble.rhcloud.com/"
},
{
"feed": "http://update.10trum.de/packageupdate/getpackages.php",
"name": "http://update.10trum.de/packageupdate/getpackages.php"
},
{
"feed": "http://www.brigittehelsen.be/plexconnect/ ",
"name": "http://www.brigittehelsen.be/plexconnect/ "
},
{
"feed": "http://www.christoph-papke.de/spkrepo/spkrepo/packages/",
"name": "http://www.christoph-papke.de/spkrepo/spkrepo/packages/"
},
{
"feed": "http://www.cphub.net/index.php/getpackages.php/",
"name": "http://www.cphub.net/index.php/getpackages.php/"
},
{
"feed": "http://www.need-soft.com/packages/index.php/spkrepo/packages",
"name": "http://www.need-soft.com/packages/index.php/spkrepo/packages"
},
{
"feed": "https://synocommunity.com/packages",
"name": "https://synocommunity.com/packages"
},
{
"feed": "https://www.christoph-papke.de/spkrepo/spkrepo/packages",
"name": "https://www.christoph-papke.de/spkrepo/spkrepo/packages"
}]

 

If you already have your own list, you may want to compare with this one and adjust accordingly.

 

A few other things to note about these feeds. The first time you get the feeds your package center may choke and complain about a dropped connection, if you 'tail /var/log/messages' you'll see a few sites that might be experiencing difficulties.

 

I eliminated and corrected many of the sites that are incorrect or down forever, but there are a few that I either left because it looked like a temporary problem, or were left because I couldn't determine the actual site with problems via /var/log/messages.

 

I left a couple that looked like they might just be having temporary problems.

 

What's left is a list of the most up to date spk repositories that I could pull together quickly.

 

Below is information if you need to edit the file. Chances are if you're installing this file, you wont need to read it.

 

Note the formatting is JSON. fairly simple. It is a feed url follwed by the feed name. I left the name the same as the feed, but you can change them to whatever is appropriate for each site.

file begins with a [ and ends with a ]

each feed is surrounded by { }

Each feed is separated by a single comma " , "

it is all on one single line.

Example file: (Don't use this one)

[{"feed":"http://packages.synocommunity.com/?beta=1","name":"http://packages.synocommunity.com/?beta=1"},{"feed":"url to site","name":"nick name or aka or other label for the site"},{and so on...}]

Edited by Guest
Link to comment
Share on other sites

  • 3 weeks later...
ive edited my file in /usr/syno/etc/packages/feeds using the above.....all the websites show in the source settings...but now all I get is "all packages installed" under community apps. It no longer shows any apps.

 

I also get this. I'm not sure exactly what causes it, but if you watch the messages log you'll see it is trying to connect to some and having problems. I haven't had time to investigate which sites cause it and why it seems to affect the loading of that screen, but I do have a work around that works...

 

From a command prompt do a

 tail -n 20 -f /var/log/messages

 

the '-n 20' part is only if you got to the command prompt after you tried to look for updated apps. It gives the last 20 lines and then -f follows anything that gets added after. I see entries where some sites are not responding appropriately or quickly.

 

What I do to get around the problem is just click on the regular syno app package pages (recommended, all, backup,multimedia, etc..) once each and let them load while I work my way down to community. By the time I get there the page is either populated or in the process of refreshing. (Clicking the refresh button sometimes works, but not as reliably as this method)

 

When I tried it just now, I received the same message and it displayed no community apps. I used the above method, and it indicated I might have a network problem. Clicking refresh was a fruitless excercise. I clicked back up on one of the syno app pages (Utilities, in this case) and then back down and it refreshed with the loaded app page.

 

Below is the contents of my /var/log/messages

Most of the problems seem to be related to how the program fails to account for certain curl errors.

Thor/root$> tail -n 25 -f /var/log/messages
Jan 21 16:08:14 Thor PkgSynoMan.cgi: pkgcurltool.cpp:287 Failed to curl perform, code=6, err=Error
Jan 21 16:08:14 Thor entry.cgi_SYNO.Core.Package.Server[1].check[6415]: pkgcurltool.cpp:287 Failed to curl perform, code=6, err=Error
Jan 21 16:08:15 Thor PkgSynoMan.cgi: pkgcurltool.cpp:287 Failed to curl perform, code=6, err=Error
Jan 21 16:08:15 Thor entry.cgi_SYNO.Core.Package.Server[1].check[6415]: pkgcurltool.cpp:287 Failed to curl perform, code=6, err=Error
Jan 21 16:08:16 Thor PkgSynoMan.cgi: pkgcurltool.cpp:397 Failed to curl perform, http://synopkg.superzebulon.org/spkrepo/packages
Jan 21 16:08:16 Thor entry.cgi_SYNO.Core.Package.Server[1].check[6415]: pkgcurltool.cpp:397 Failed to curl perform, http://synopkg.superzebulon.org/spkrepo/packages
Jan 21 16:08:23 Thor entry.cgi_SYNO.Core.Package.Server[1].check[6415]: pkgcurltool.cpp:407 http://www.need-soft.com/packages/index.php/spkrepo/packages, Failed to request packages, httpResponseCode=404
Jan 21 16:08:24 Thor PkgSynoMan.cgi: pkgcurltool.cpp:407 http://www.need-soft.com/packages/index.php/spkrepo/packages, Failed to request packages, httpResponseCode=404
Jan 21 16:08:24 Thor entry.cgi_SYNO.Core.Package.Server[1].check[6415]: pkgcurltool.cpp:287 Failed to curl perform, code=51, err=Error
Jan 21 16:08:24 Thor PkgSynoMan.cgi: pkgcurltool.cpp:287 Failed to curl perform, code=51, err=Error
Jan 21 16:08:28 Thor PkgSynoMan.cgi: pkgimagetool.cpp:219 Wrong content type image/gif in http://www.mshgroup.eu/piwik/piwik.php?idSite=4&rec=1&url=http%3A%2F%2Fspk.synologyitalia.com%2Fpackagecenter&action_name=PackageCenter&_id=[spoiler=]removed[/spoiler]
Jan 21 16:08:55 Thor PkgSynoMan.cgi: pkgcurltool.cpp:287 Failed to curl perform, code=7, err=Error
Jan 21 16:08:58 Thor PkgSynoMan.cgi: pkgcurltool.cpp:287 Failed to curl perform, code=6, err=Error
Jan 21 16:08:59 Thor PkgSynoMan.cgi: pkgcurltool.cpp:287 Failed to curl perform, code=6, err=Error
Jan 21 16:09:00 Thor PkgSynoMan.cgi: pkgcurltool.cpp:287 Failed to curl perform, code=6, err=Error
Jan 21 16:09:01 Thor PkgSynoMan.cgi: pkgcurltool.cpp:397 Failed to curl perform, http://synopkg.superzebulon.org/spkrepo/packages
Jan 21 16:09:06 Thor PkgSynoMan.cgi: pkgcurltool.cpp:407 http://www.need-soft.com/packages/index.php/spkrepo/packages, Failed to request packages, httpResponseCode=404
Jan 21 16:09:07 Thor PkgSynoMan.cgi: pkgcurltool.cpp:287 Failed to curl perform, code=51, err=Error
Jan 21 16:09:09 Thor PkgSynoMan.cgi: pkgimagetool.cpp:219 Wrong content type image/gif in http://www.mshgroup.eu/piwik/piwik.php?idSite=4&rec=1&url=http%3A%2F%2Fspk.synologyitalia.com%2Fpackagecenter&action_name=PackageCenter&_id=[spoiler=]removed[/spoiler]
Jan 21 16:16:34 Thor PkgSynoMan.cgi: pkgimagetool.cpp:219 Wrong content type image/gif in http://www.mshgroup.eu/piwik/piwik.php?idSite=4&rec=1&url=http%3A%2F%2Fspk.synologyitalia.com%2Fpackagecenter&action_name=PackageCenter&_id=[spoiler=]removed[/spoiler]
Jan 21 16:17:31 Thor PkgSynoMan.cgi: pkgcurltool.cpp:287 Failed to curl perform, code=28, err=Error
Jan 21 16:18:33 Thor PkgSynoMan.cgi: pkgcurltool.cpp:287 Failed to curl perform, code=28, err=Error
Jan 21 16:19:35 Thor PkgSynoMan.cgi: pkgcurltool.cpp:287 Failed to curl perform, code=28, err=Error
Jan 21 16:19:36 Thor PkgSynoMan.cgi: pkgcurltool.cpp:397 Failed to curl perform, http://e-remonty.info/spkrepo/packages
Jan 21 16:19:46 Thor PkgSynoMan.cgi: pkgcurltool.cpp:407 http://spk.nas-mirror.de/, Failed to request packages, httpResponseCode=405
Jan 21 16:20:53 Thor PkgSynoMan.cgi: pkgcurltool.cpp:287 Failed to curl perform, code=7, err=Error
Jan 21 16:20:57 Thor PkgSynoMan.cgi: pkgcurltool.cpp:287 Failed to curl perform, code=6, err=Error
Jan 21 16:20:58 Thor PkgSynoMan.cgi: pkgcurltool.cpp:287 Failed to curl perform, code=6, err=Error
Jan 21 16:20:59 Thor PkgSynoMan.cgi: pkgcurltool.cpp:287 Failed to curl perform, code=6, err=Error
Jan 21 16:21:00 Thor PkgSynoMan.cgi: pkgcurltool.cpp:397 Failed to curl perform, http://synopkg.superzebulon.org/spkrepo/packages
Jan 21 16:21:07 Thor PkgSynoMan.cgi: pkgcurltool.cpp:407 http://www.need-soft.com/packages/index.php/spkrepo/packages, Failed to request packages, httpResponseCode=404
Jan 21 16:21:08 Thor PkgSynoMan.cgi: pkgcurltool.cpp:287 Failed to curl perform, code=51, err=Error
Jan 21 16:21:10 Thor PkgSynoMan.cgi: pkgimagetool.cpp:219 Wrong content type image/gif in http://www.mshgroup.eu/piwik/piwik.php?idSite=4&rec=1&url=http%3A%2F%2Fspk.synologyitalia.com%2Fpackagecenter&action_name=PackageCenter&_id=[spoiler=]removed[/spoiler]

Link to comment
Share on other sites

Humm I checked it last night and noticed it was still down. :sad:

 

The way things are looking with the 5.1 build mirroring resources might become a requirement. Just a hunch...that payment.synology.com url with api's seems like a method of validating whether paid or otherwise. It looks like some of the package sources route through something accessed via that domain before the contents render in the DSM. I think I read somewhere that something associated with this was added back in one of the later 4.x DSM releases? I could be remembering that wrong though?

 

We will need a plan if the doors are being closed to packages via the DSM update and installation process.

 

Here's the thread about the github performance issues https://github.com/SynoCommunity/spksrc/issues/1452

 

You maybe able stop twiddling your thumbs and get what you want from here and go manual https://synocommunity.com/packages/

 

EDIT: It's probably not wise to apply any packages manually if you're not sure if you have the dependencies required by the package you want to install. Don't come crying if things go horribly wrong you have been warned.

 

That's not directed at you fusiondust it's just a general note of caution for anyone that wants to try going off piste.

Link to comment
Share on other sites

For those editing the host file(see below) to get volumes to work,

echo 127.0.0.1 payment.synology.com >> /etc/hosts

 

a possible temporary solution for updating packages is:

mv /etc/hosts /etc/nohosts

perform your package installs or updates

and then

mv /etc/nohosts /etc/hosts

afterward.

 

This is untested, but based on some feedback I'm seeing, it looks like it would work on a temporary basis.

Also, Completely disable any automatic update checking in the control panel, just in case, and also adjust the settings in package manager to allow packages other than the official synology spks to be installed.

Link to comment
Share on other sites

GIT is free and open so there should be no form of copy protection.

 

The package centre allowed GIT to install on my machine but it's not intuitive, lacks an interface and basic docs to help get going. There's a thread on the syno forums. I don't use git so I stopped after reading the tread maybe there will be something useful in it for you? GIT forum post is here.

Link to comment
Share on other sites

I've Trimmed down feeds file for package sources. If I received errors from a site or could not add a site manually, it was removed from my list.

 

This list loads much faster than before, with bad and unresponsive repos removed.

Some of these may require you to set "Any publisher" under Settings ... General in the package center

 

backup your feeds file /usr/syno/etc/packages/feeds and replace the contents with the below.

[{"feed":"http://cbo.netau.net/synopackages/","name":"cbo.netau.net"},{"feed":"http://cytec.us/spk/","name":"cytec.us"},{"feed":"http://e-remonty.info/spkrepo/packages","name":"e-remonty.info"},{"feed":"http://ggteknikus.tk/sspks/","name":"ggteknikus.tk"},{"feed":"http://packages.jdel.org/","name":"jdel.org"},{"feed":"http://packages.jdel.org/","name":"jdel.org"},{"feed":"http://packages.mdevries.org","name":"mdevries.org"},{"feed":"http://packages.pcloadletter.co.uk/","name":"packages.pcloadletter.co.uk"},{"feed":"http://packages.synocommunity.com","name":"synocommunity.com"},{"feed":"http://packages.synocommunity.com/?beta=1","name":"synocommunity.com beta"},{"feed":"http://pvr.unzureichende.info/synology","name":"pvr.unzureichende.info"},{"feed":"http://spk.naefmarco.ch/spkrepo/packages","name":"spk.naefmarco.ch"},{"feed":"http://spk.nas-mirror.de/spkrepo/packages","name":"spk.nas-mirror.de"},{"feed":"http://spk.unzureichende.info/","name":"unzureichende.info"},{"feed":"http://synobox.fr.nf/synopackages/","name":"synobox.fr.nf"},{"feed":"http://synobox.fr.nf/synopackages/beta.php","name":"synobox.fr.nf beta"},{"feed":"http://synology.acmenet.ru","name":"synology.acmenet.ru"},{"feed":"http://packages.mdevries.org/","name":"mdevries.org"},{"feed":"http://synology.sysco.ch","name":"synology.sysco.ch"},{"feed":"http://synopkgs-garble.rhcloud.com/","name":"synopkgs-garble.rhcloud.com"},{"feed":"http://www.brigittehelsen.be/plexconnect/","name":"www.brigittehelsen.be/plexconnect/"},{"feed":"http://www.cphub.net/index.php/getpackages.php/","name":"www.cphub.net"},{"feed":"https://www.cphub.net/packages.php","name":"cpbhub.net"}]

 

If you find any missing that you know to work, please post it here.

Link to comment
Share on other sites

GIT is free and open so there should be no form of copy protection.

 

The package centre allowed GIT to install on my machine but it's not intuitive, lacks an interface and basic docs to help get going. There's a thread on the syno forums. I don't use git so I stopped after reading the tread maybe there will be something useful in it for you? GIT forum post is here.

I understand what you are saying, but my initial question is still unclear. Is it true that Synocommunity Package repository stops working if you have XPenology?

 

edit: then again, this second synology on my LAN is being anoying anyway... when i start it, my router goes crazy and no one has internet anymore.

When i remove synocommunity and only add http://synology.acmenet.ru/ I also see the loading screen going on forever.

Link to comment
Share on other sites

I understand what you are saying, but my initial question is still unclear. Is it true that Synocommunity Package repository stops working if you have XPenology?

 

I have not had that problem.

 

edit: then again, this second synology on my LAN is being anoying anyway... when i start it, my router goes crazy and no one has internet anymore.

When i remove synocommunity and only add http://synology.acmenet.ru/ I also see the loading screen going on forever.

 

See my previous post. One or more of your feeds are bad and that is what is causing the hang. Either replace your feeds with the contents I posted above, or you could manually go through your list to check which ones are bad. My list is fairly complete and I've removed bad repos. Mine loads in seconds and that's on a slow day.

 

If you want to do it yourself and you're confident your list is complete, manually go through your list, edit each one and change the name/description slightly (No need to change the url portion). When you save it your box will check if the site is valid and responding. If any have problems with one, remove it or try to find the new url, if it has changed. When you're done going through your list you will see that yours now loads more quickly.

 

Also remember to adjust the trust level in settings general. Remove any edit to your host file for payment.synology.com.

Link to comment
Share on other sites

  • 2 weeks later...
  • Schnapps changed the title to Synology Community Package Sources (UPDATE 2024)

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...