I wanted to use https://<my domain>/music/ to use subsonic outside my LAN. There is already https://<my domain>/docs/ up and running.
Miserably failed over the course of 3 evenings, but won finally. This is how. This was on Ubuntu 12.04, so ymmv.
1 Subsonic
in /etc/default/subsonic added the bold item
SUBSONIC_ARGS="--max-memory=150 --context-path=/music"
(restart subsonic server, test, my internal ip was 192.168.11.3 and subsonic was on 4040, yours will be different - http://192.168.11.3:4040/music/ should give the login screen )
2 Apache
in /etc/apache2/sites-available default-ssl
Assuming you have ssl set up and mod_proxy enabled (look in the docco - mod_proxy:http://httpd.apache.org/docs/2.2/mod/mod_proxy.html ssl certs:http://www.onlamp.com/2008/03/04/step-by-step-configuring-ssl-under-apache.html for full info.
- Code: Select all
#added to make subsonic work over 443
ProxyRequests Off
#RequestHeader unset Accept-Encoding
#Order allow,deny
#Allow from all
ProxyPass /music/ http://192.168.11.3:4040/music/
ProxyPassReverse /music/ http://192.168.11.3:4040/music/
(restart apache, get outside your lan, try https:<your domain>/music/)
I am sure others out there can point out where this is non-optimal, but if you do not want to expose 4040 at home / want to get through other peoples firewalls / dont want to be overheard (except by the nsa), this may be a start point.
