OwnCloud 9.0.2 (all ReadyNAS platforms)

owncloud_logo

Totally forgot to announce that ownCloud 9.0.2 is available for all ReadyNAS platforms:

SABnzbd 1.0.2 (all ReadyNAS platforms)

sabnzbd_logo

Since there’s a new release of SABnzbd the add-ons for the various ReadyNAS platforms have been updated as well:

NZBGet 16.4-3 (R4x86)

nzbget

Thanks to Andrea I was able to fix a bug in the NZBGet add-on for ReadyNAS OS 4 (x86) that could prevent NZBGet from starting up on some systems. The base problem was that this version was compiled against libssl1.0.2 but I forgot to include that lib in the add-on. Since some other add-ons already come with libssl1.0.2 it was already present on my testing box. Sorry for any inconvenience.

SABnzbd 1.0.1 (All ReadyNAS Platforms)

sabnzbd_logo

SABnzbd has been updated to version 1.0.1 and so the add-on is now available in version 1.0.1 as well:

The versions for ReadyNAS OS 4 and 5 also contain a fix for the bug that prevented changes made to the port SABnzbd should listen on from getting picked up by the add-on. Please also note that users on the ReadyNAS 4 x86 platform are encouraged to upgrade their Python add-on to the latest release (see below) for an additional bug fix.

Bye-bye Slack!

Well, switching to Slack as the primary support channel didn’t work out either. Actually, I did work perfectly for the first couple of days. And then the spammers found the invite form and from there everything went downhills. I can’t restore the invite functionality for all invites have been used up and there’s no way to get them back. So I’ll close the Slack channel again and check out other options. For the time being there’s still email but given the amount of mail I receive daily due to my job there’s a good chance I’ll overlook a message or simply forget about it at the end of the day.

A side note to all those who complained that there is no email address to send support mail to: That’s not true, you for some or other reasons just didn’t try to simply use the “reply” function of your email client. Additional hint: There’s no “noreply” type mailbox here.

OwnCloud 9.0.2 (all ReadyNAS platforms)

owncloud_logo

Totally forgot to announce that ownCloud 9.0.2 is available for all ReadyNAS platforms:

SABnzbd 1.0.2 (all ReadyNAS platforms)

sabnzbd_logo

Since there’s a new release of SABnzbd the add-ons for the various ReadyNAS platforms have been updated as well:

NZBGet 16.4-3 (R4x86)

nzbget

Thanks to Andrea I was able to fix a bug in the NZBGet add-on for ReadyNAS OS 4 (x86) that could prevent NZBGet from starting up on some systems. The base problem was that this version was compiled against libssl1.0.2 but I forgot to include that lib in the add-on. Since some other add-ons already come with libssl1.0.2 it was already present on my testing box. Sorry for any inconvenience.

SABnzbd 1.0.1 (All ReadyNAS Platforms)

sabnzbd_logo

SABnzbd has been updated to version 1.0.1 and so the add-on is now available in version 1.0.1 as well:

The versions for ReadyNAS OS 4 and 5 also contain a fix for the bug that prevented changes made to the port SABnzbd should listen on from getting picked up by the add-on. Please also note that users on the ReadyNAS 4 x86 platform are encouraged to upgrade their Python add-on to the latest release (see below) for an additional bug fix.

Bye-bye Slack!

Well, switching to Slack as the primary support channel didn’t work out either. Actually, I did work perfectly for the first couple of days. And then the spammers found the invite form and from there everything went downhills. I can’t restore the invite functionality for all invites have been used up and there’s no way to get them back. So I’ll close the Slack channel again and check out other options. For the time being there’s still email but given the amount of mail I receive daily due to my job there’s a good chance I’ll overlook a message or simply forget about it at the end of the day.

A side note to all those who complained that there is no email address to send support mail to: That’s not true, you for some or other reasons just didn’t try to simply use the “reply” function of your email client. Additional hint: There’s no “noreply” type mailbox here.