Unable to connect to Subsonic...

[BKKKPewsey]

It is times like this when I am glad I'm running Windoze

From very distant memory wont "service --status-all" list running services (or something like that? )

[magnusoverli]

OK! I have a sollution (for my problem at least)!

I needed to set what user Subsonic should be running as in /etc/default/subsonic, and after I had to chown -R <username> /var/subsonic /tmp/subsonic

After this it all worked! Hope this works for you guys as well!
I also change the default port to something other than 4040, but I am not sure of the significance of this step!
Take care!

Magnus

[hexapus]

I just have it set to run under my personal user account, and I mistyped...I meant /etc/default. Sorry about that.

[ChiMatt]

I am hosting subsonic on a windows xp system. Anytime the system is restarted, the system starts subsonic and everything appears to be working fine. I can connect locally within my network. When I try to connect from outside my system, the address will not resolve. I usually go into my router at that point and check to see that the port is properly being forwarded to my router, which it is not. I have to manually uncheck port forwarding and recheck the portforwarding in network settings to get the port to forward to the router properly. Once I have done that and restarted subsonic, it works. This process use to be automated and worked perfectly everytime prior to the last subsonic update. Anyone else having this same issue?

[BKKKPewsey]

UPnP on routers can be problematic, especially on start up, the best course is to disable port forwarding in SS and open the ports manually on the router.

[colli419]

This might be completely unrelated, but I was getting a 503 error as well.

What was causing it was a full boot drive (the drive that subsonic was installed on). As soon as I cleared up some extra room on the drive, the problem disappeared.