Subsonic Forum

The first problem I have is the Now Playing pane.

The chat doesn't work, you type something in and press enter and nothing happens, and when a user logs out they don't dissapear.

Also I was accessing my Subsonic setup from www.cambates.co.uk/subsonic/ quite happily using the apache ProxyPass settings.

Now however I have a new domain. I've added this domain to the apache setup and set up the Proxy settings and can access subsonic on port 80.

However on the new domain when I enter my log in details, it doesn't log in, just loads the login page again with no error.

It works when accessing from port 8080 though.

Any ideas?
Cheers.

EDIT: Forgot to mention

Ubuntu Server 10.04
Tomcat6
Apache2.2

I'm not sure what you mean by a user "doesn't disappear" when they log out. If you're referring to their entry in the Now Playing pane, that is supposed to stay there for 60 minutes after the last song is played. After about 5 minutes it will say "5 minutes ago." etc under the entry. After 1 hour it will disappear. It has to do with the last song played, not when the user logged out of Subsonic.

As for the chat box, I will leave that problem for someone else. It always worked perfectly for me, I have little knowledge of its underlying work since I've never had a problem with it.

I use Apache's reverse proxy settings, or rather I did for a long time. I forget the line I had to include, but there's something about Proxy Preserve that preserves the target URL after a refresh, etc. Maybe you need that configuration directive. If you have no idea what I'm talking about, you MIGHT not have done it, and I can try to find the name of the configuration directive for you.

My best suggestion at the moment, is change Subsonic to run on port 80 on whatever internal server it's on. I'm thinking the redirection problem has something to do with Subsonic trying to reload your browser on port 8080 even though your browser is on port 80. If the Subsonic port matched the external port, that might work properly. I've seen some strange stuff with Apache's mod_proxy.

Cheers,
Kirk