
qonstrukt wrote:@steve1977:
In your setup the ports all have to be set to 80, that's the default HTTP port. I'm pretty sure I'll be adding Headphones support in the future, but you'll have to wait a bit longer for it as I'll first have to polish all the other functionality a bit more.


bbaraniec wrote:Why do you use password for reverse proxy when you have built one for SABnzbd it self? It working for me but I'm not using any additional authentication in Apache


location /couch/ {
proxy_pass http://127.0.0.1:8082/;
proxy_redirect default;
} 
bbaraniec wrote:http://bit.ly/vJo4ax



qonstrukt wrote:For 1.1.x users running a reverse proxy, I can recommend not using a user/pass on your web server, but only on the application itself. SABnzbd+ cannot connect using a user/pass on the web server at the moment. If you want to add a user/pass later (for 1.2) make sure it is the same as on your web server as there won't be any separate fields for it. I don't really see why you'd want to do that.

Really cool app! Looking forward to updates! 






steve1977 wrote:qonstrukt wrote:For 1.1.x users running a reverse proxy, I can recommend not using a user/pass on your web server, but only on the application itself. SABnzbd+ cannot connect using a user/pass on the web server at the moment. If you want to add a user/pass later (for 1.2) make sure it is the same as on your web server as there won't be any separate fields for it. I don't really see why you'd want to do that.
Using the app user name and password is actually a quite insecure way to protect your apache server. One thing which I am not fully clear. Those (like myself) using .htaccess to protect their apache server and properly configured reverse-proxies will actually not even need the user name and password of the apps anymore. The reverse-proxy will include those after entering the apache .htaccess password.
