Subsonic Forum

by **boognish523** » Fri Mar 04, 2011 4:23 pm

I have not been able to access my subsonic server locally, on the home network, or remotely for about a week. I get an error of 503. I have uninstalled, reinstalled, turned off my firewall etc., but cannot get past this error.

Any clues?

by **GJ51** » Fri Mar 04, 2011 4:27 pm

Here's a few:

Most problems are due to improper setup on the router. Setting a fixed internal ip address for the server and proper port forwarding rules on the router are essential for long term stability.

Disable any DHCP services in any VOIP equipment you have. Only one device per network should handle DHCP assignments.

First read: http://monroeworld.com/android/subsonic/ This is the Windows tutorial but most of the concepts apply to any setup. Specific setup instructions for other Operating Systems are available in the Tutorials section. http://forum.subsonic.org/forum/viewforum.php?f=6 and on the Subsonic website at http://www.subsonic.org/pages/installation.jsp

Never use port 80 - ISP's often use it or block it. 8080,8081, work fine. 808X always works. I've seen others use different port numbers that have caused install failure.

Start with a fresh Java install to the latest version. If you have Java already, uninstall, then do a clean install of the latest version. If you use a 64 bit browser be sure to get both 32 & 64 bit Java.
http://www.java.com/en/download/faq/java_win64bit.xml

In Subsonic Settings/Network - UNCHECK " Automatically configure your router to allow incoming connections to Subsonic (using UPnP or NAT-PMP port forwarding)." make sure to hit the SAVE button, you may have to scroll down to see it depending on your screen size. UPnP or Plug & Pray works sometimes, but not very often and you're better off learning what's going on anyway. You're dipping your toe into the network mgmt. thing anyway, might as well learn what's going on as home networks don't get simpler as time goes on. As your network gets more complex, you're going to have to learn this stuff! No time like the present.

Manually assign a fixed intenal IP and static route to your server at the upper end of the address range of the router, out of the way of DHCP, e.g. 192.168.1.254

Set up your router manually. uPNP might work, but most often it doesn't. Learing how to do it will be a skill you'll love having as your network grows.

Check the Subsonic Control Panel to make sure it's using the right port you're going to use. I typically use 8080, 8081, etc.

Set up port forwarding in your router to direct traffic on the selected port to your server. Consult your router documentation to do this, they are all a bit different.

Learn your external IP address assigned by your ISP. Go to http://www.canyouseeme.org/ enter your SS port number and click the Check box to be sure the Subsonic port is open.

Test your setup by entering your external IP:port# to see if it connects. e.g. http://98.117.185.5:8084/ If it works, you're good to go.

If your still having problems. Clear browser cache. Reboot the server. If that doesn't work, uninstall/reinstall Java. If still no joy, try reinstalling SS right over the top of the current SS using the latest version.

by **boognish523** » Fri Mar 04, 2011 8:52 pm

oh well, everything seems to be right, but still getting same message. Moving this weekend, gonna have a different router and ISP, will just try to reset up once I get there and see if it continues.

Thanks for your help!

by **myeary** » Sun Mar 13, 2011 4:29 pm

Same problem here. I've rebooted, confirmed port forwarding, uninstalled and reinstalled Java, and everything else suggested here. The one thing that worked was downgrading to a clean-installed Subsonic 4.3

I'm running Windows XP SP 3, Java 6 update 24

- Mark

by **GJ51** » Sun Mar 13, 2011 4:32 pm

HTTP Error 503 - Service unavailable

Introduction

The Web server (running the Web site) is currently unable to handle the HTTP request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. Some servers in this state may also simply refuse the socket connection, in which case a different error may be generated because the socket creation timed out.

503 errors in the HTTP cycle

Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with the Web server:
•Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
•Open an IP socket connection to that IP address.
•Write an HTTP data stream through that socket.
•Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.

This error occurs in the final step above when the client receives an HTTP status code that it recognises as '503'. Frank Vipond. September 2010.

Fixing 503 errors

The Web server is effectively 'closed for repair'. It is still functioning minimally because it can at least respond with a 503 status code, but full service is impossible i.e. the Web site is simply unavailable. There are a myriad possible reasons for this, but generally it is because of some human intervention by the operators of the Web server machine. You can usually expect that someone is working on the problem, and normal service will resume as soon as possible.

Please contact the system operators of the Web site (e.g. your ISP) to determine why the service is down. They will be in a much better position to help you than we are for this type of error.

by **JoyMonkey** » Sun Mar 13, 2011 5:49 pm

I've also run into this problem after upgrading from 4.3b1 to 4.4 on my Ubuntu machine. Everything was running fine until I installed 4.4.

Has anyone found a solution other than downgrading back to 4.3?

by **GJ51** » Sun Mar 13, 2011 11:42 pm

Are you sure that the port settings in the SS Control Panel and the internal IP address of the host machine stayed the same between versions? I've done several upgrades to multiple servers without any of the issues you describe.

by **myeary** » Sat Mar 26, 2011 2:59 am

IP address is static, port 4040, port forwarding confirmed operational. Works with 4.3, doesn't with 4.4. This is likely not a configuration issue; I followed the same steps for both versions, with the same router settings.

- Mark

by **GJ51** » Sat Mar 26, 2011 3:29 am

Go to http://www.canyouseeme.org/ enter your SS port number and click the Check box to be sure the Subsonic port is open.

Make sure that SSL is disabled. Establish http access first. Sometimes a router reboot helps as well. I've done this literally hundreds of times now. It's always in the router setup.

Is the server working inside the network?

by **myeary** » Sun Mar 27, 2011 3:30 pm

Port forwarding confirmed at canyouseeme.org, and https is disabled in the control panel. So I just re-installed 4.4, and now it's working. Go figure; I've changed nothing, but confirmed lots of things, over the past few weeks. Thanks for your patience!

- Mark

by **JoyMonkey** » Wed Apr 20, 2011 1:25 pm

It's been a while so I figured I'd try getting Subsonic going again. I downloaded the 4.4.deb and tried using Ubuntu's gui installer. Unfortunately I got the same results as before; the 503 error when I tried to browse to localhost:4040.
I uninstalled it from the Synaptic Package Manager (doing a complete removal, so all configuration files were removed) and tried re-installing it again, this time from terminal using sudo dpkg -i subsonic-4.4.deb
I got the same results.

I uninstalled again and tried doing the same with 4.3, but that's also giving the same error.

So I did a complete removal of 4.3, then a complete removal of openjdk-6-jre and openjdk-6-jre-headless, then I did a sudo apt-get install openjdk-6-jre, then sudo dpkg -i subsonic-4.4.deb again.

The output went like...

Code: Select all: user@myputer:/tmp$ sudo dpkg -i subsonic-4.4.deb (Reading database ... 272093 files and directories currently installed.) Preparing to replace subsonic 4.3 (using subsonic-4.4.deb) ... start-stop-daemon: warning: failed to kill 15924: No such process Unpacking replacement subsonic ... Removing any system startup links for /etc/init.d/subsonic ... /etc/rc0.d/K99subsonic /etc/rc1.d/K99subsonic /etc/rc2.d/S99subsonic /etc/rc3.d/S99subsonic /etc/rc4.d/S99subsonic /etc/rc5.d/S99subsonic /etc/rc6.d/K99subsonic Setting up subsonic (4.4) ... Installing new version of config file /etc/default/subsonic ... Adding system startup for /etc/init.d/subsonic ... /etc/rc0.d/K99subsonic -> ../init.d/subsonic /etc/rc1.d/K99subsonic -> ../init.d/subsonic /etc/rc6.d/K99subsonic -> ../init.d/subsonic /etc/rc2.d/S99subsonic -> ../init.d/subsonic /etc/rc3.d/S99subsonic -> ../init.d/subsonic /etc/rc4.d/S99subsonic -> ../init.d/subsonic /etc/rc5.d/S99subsonic -> ../init.d/subsonic Started Subsonic [PID 16293, /var/subsonic/subsonic_sh.log] Processing triggers for ureadahead ...

...which says that it was upgrading 4.3 - which I had already supposedly uninstalled. So for some reason my old version is just not being removed properly. So I tried removing it from terminal...

Code: Select all: user@myputer:/tmp$ sudo apt-get remove subsonic Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: subsonic 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 0B of additional disk space will be used. Do you want to continue [Y/n]? Y (Reading database ... 272092 files and directories currently installed.) Removing subsonic ... Removing any system startup links for /etc/init.d/subsonic ... /etc/rc0.d/K99subsonic /etc/rc1.d/K99subsonic /etc/rc2.d/S99subsonic /etc/rc3.d/S99subsonic /etc/rc4.d/S99subsonic /etc/rc5.d/S99subsonic /etc/rc6.d/K99subsonic Processing triggers for ureadahead ...

Then re-installed 4.4, this time the terminal output looked right...

Code: Select all: user@myputer:/tmp$ sudo dpkg -i subsonic-4.4.deb Selecting previously deselected package subsonic. (Reading database ... 272088 files and directories currently installed.) Unpacking subsonic (from subsonic-4.4.deb) ... Setting up subsonic (4.4) ... Adding system startup for /etc/init.d/subsonic ... /etc/rc0.d/K99subsonic -> ../init.d/subsonic /etc/rc1.d/K99subsonic -> ../init.d/subsonic /etc/rc6.d/K99subsonic -> ../init.d/subsonic /etc/rc2.d/S99subsonic -> ../init.d/subsonic /etc/rc3.d/S99subsonic -> ../init.d/subsonic /etc/rc4.d/S99subsonic -> ../init.d/subsonic /etc/rc5.d/S99subsonic -> ../init.d/subsonic Started Subsonic [PID 16429, /var/subsonic/subsonic_sh.log] Processing triggers for ureadahead ...

..but I'm still getting the 503 error. So I did an apt-get --purge remove subsonic and got...

Code: Select all: user@myputer:/tmp$ sudo apt-get --purge remove subsonic Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: subsonic* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 0B of additional disk space will be used. Do you want to continue [Y/n]? Y (Reading database ... 272092 files and directories currently installed.) Removing subsonic ... Removing any system startup links for /etc/init.d/subsonic ... /etc/rc0.d/K99subsonic /etc/rc1.d/K99subsonic /etc/rc2.d/S99subsonic /etc/rc3.d/S99subsonic /etc/rc4.d/S99subsonic /etc/rc5.d/S99subsonic /etc/rc6.d/K99subsonic Purging configuration files for subsonic ... Removing any system startup links for /etc/init.d/subsonic ... Processing triggers for ureadahead ...

I also removed the /var/subsonic directory. And still the 503 error.

I really liked Subsonic and have paid for a license, but this is killing me.
Is there anything else I can try?

Subsonic Forum

503 Error after 4.4 update

503 Error after 4.4 update

Yes, I'm sure

Who is online