Sorry for such a long delay in responding. I finally have some time to get back to troubleshooting this issue.
Ok, so before I was using port 8080, but I have since changed that back to using the subsonic defaults of 4040. I have also upgraded to version 4.5. I followed bigfoot's instructions on creating a webapp and modifying the .conf file. Here is my modified .conf file:
Code: Select all
<VirtualHost *:80>
ServerName subsonic
ServerAlias subsonic.[i]mynetworkname[/i].net
ProxyPass / http://localhost:4040/
ProxyPassReverse / http://localhost:4040/
DocumentRoot /var/hda/web-apps/subsonic/html
<Directory "/var/hda/web-apps/subsonic/html">
Options Indexes FollowSymLinks +ExecCGI
AddHandler fcgid-script .fcg
AllowOverride AuthConfig
Order allow,deny
Allow from all
</Directory>
ErrorLog /var/hda/web-apps/subsonic/logs/error_log
CustomLog /var/hda/web-apps/subsonic/logs/access_log combined env=!dont$
</VirtualHost>
What works now:
- typing in 'subsonic/' in any browser on any machine from within my network.
- typing '
username.subsonic.org', which is the subsonic supplied dynamic dns entry to my server, works from outside my network and the browser from my server running amahi. In all cases when I type in '
username.subsonic.org' the url has been changes to 10.8.0.1:4040 which resolves correctly when run on the amahi server, but fails everywhere else.
- I also have a dyn-dns address that points to my router and wherever I am (inside or outside of my network) I can use '
dyn-dns.address.com:4040' and get to subsonic.
What I want is to be able to type in '
username.subsonic.org' from inside my network and have that resolve to my amahi server running subsonic. Instead of resolving to 10.8.0.1:4040 if it resolved to my amahi ip address in the 192.168.x.x range all would probably be good.
This isn't a show stopper by any means as I can use my dyn-dns address wherever I go, but it would add a level of polish for running subsonic on amahi.
Thanks for all your help.
Dave