Zitat von "ryecoaaron"
By a lot more config, you mean a few lines??
Codelocation /sabnzbd/ { proxy_pass http://localhost:8080; }
Arf, I don't use nginx in my prod server, so I've just read this doc : http://wiki.sabnzbd.org/howto-apache .
Well, it's all good for 0.6 then 
Zitat von "davidh2k"Nice solution, but security wise I don't think it adds any security.
Greetings
David
PS: New Version of OpenMediaVault uses nginx instead of apache, so it could be only implemented if nginx would support this too.
Sure, it's possible with nginx, but require a lot more config than apache ...
For the security, it's more than port 80 and 443 are often the only port that are opened/possible in corporate/public proxy or web proxy ...
Hi,
I've just installed openmediavault-sabnzbd from miller-testing repo on a fresh OMV 0.5.53 install. Everything went fine so thx for this plugin !
As I don't like to expose ports other than 80 on internet, I've done these custom steps after sabdnzb installation :
- enabling mod_proxy in apache :
a2enmod proxy
a2enmod proxy_http
then restart apache
/etc/init.d/apache2 restart- creating a conf file for OMV apache2 conf :
add in a a file called /etc/apache2/openmediavault-webgui.d/sabnzbd_proxy.conf the lines :
ProxyPass /sabnzbd/ http://localhost:8080/
ProxyPassReverse /sabnzbd/ http://localhost:8080/
then reload apache conf
/etc/init.d/apache2 reload- I've restrict host where sabnzbd listen to localhost, in sabnzbd configuration.
- I've changed original url for sabnzbd web interface in plugin files : Settings.js and WebInterface.js
With thoses steps sabnzbd interface is only accessible from http://myip/sabnzbd/ (and first time sabnzbd wizard works as well), and can be launch inside OMV web interface even if only port 80 is opened.
Is it something you may consider to add directly in the plugin installation ?
maybe add just a setting for url in plugin parameters (to open the good url) if you can't do automatically apache conf ?