Like I was saying after upgrading to version 0.4.11 I decided I wanted to close port 8080 (the one sabnzbd is using) to the outside word. Now I know apache has some nice proxy functions so it should be easy.

Make sure apache is compiled with the following modules: apache2_modules_proxy apache2_modules_proxy_http apache2_modules_proxy_balancer

That was the hard part. Now just add a vhost:


ServerName yourserver.com

order deny,allow
deny from all
allow from all
ProxyPass http://localhost:8080/sabnzbd/
ProxyPassReverse http://localhost:8080/sabnzbd/a

ErrorLog /var/log/apache2/error.sabnzb.log
LogLevel warn
CustomLog /var/log/apache2/access.sabnzb.log combined



This assumes that you have sabnzbd listening on localhost:8080. Now you probably do not want the whole world watching your downloads (or deleting them or whatever). So we just add some basic apache authentication, use htpasswd2 to create a file with authorized users and add the following lines into the location block.


AuthName "Login Required"
AuthType Basic
AuthUserFile <>
require valid-user


That is all.
Happy downloading!

Changes to the ebuild:

• All templates in the original package are now installed
• More info at the end of the ebuild
• Passes repoman, well not totally since it uses local use flags.
• Changelog enty

If you have the time please grab the ebuild here and give it a spin.

About a week back I saw that in my feed reader all the messages from the SABnzbd project were empty. Which means that there was no activity for a very long time. So after browsing trought the forums I found that SABnzbd was abbandond. It made me sad. But the good thing is that I saw that a new group of people has started a succesor for SABnzbd, SABnzbdplus.

SABnzbdplus: Binary Newsgrabber written in Python, server-oriented using a web-interface. The active successor of the abandoned SABnzbd project

Now what does this mean for the SABnzbd users? Well it comes down to that their usenet download tool is supported again and actively developed. So you can expet new features. Bug fixes etc. So all good news. (for current changes see the changelog).

Now the response I got to my SABnzbd-0.2.5 ebuild (see original blog post) was quite a lot. People thanking me and sending in suggestions. Unfortunatly the ebuild never made it into gentoo portage. But times have changed. Currently Cherrypy-2.2.1-r1 is in portage. So that means this ebuild does not need any other ebuilds.

Having said that I must admit that is not entirely true. It still need yenc if you want that. However we come to that. Since well that package is quite small and only a few python script being installed. It should be no problem getting that into portage. However I do not yet feel quite ready to sumbit my new ebuild to portage since it needs some testing and some features (like the included Nova themes) are not yet available after installing the ebuild. So it will need a lot of fine tuning. However that is proces that will take some time and I could really use your help. So please if you got some spare time emerge the ebuild, try it and let me know how it works out.

I now have only tested it on amd64 but since it are all python scripts it should work on any arch that has the required deps. As stated you will need the yenc ebuild. Other than it should all work fine.

Now if you were using my pervious ebuild be sure to unmerge that first. Else you will get file collison!

And finally here the ebuild can be found.