Page 1 of 1

Registered, Updated, now ConnectTimeoutException

PostPosted: Sat Feb 05, 2011 4:44 pm
by santucci
Hi,

I just donated, got and installed my license key, and updated to the latest version (4.3), and now Subsonic is no longer working!

Automatic port forwarding and the server worked perfectly during the trial period.

I get a timeout error on the Android app, and when I go to settings>network, it says port forwarding is working, but for the server it says "santucci.subsonic.org is registered, but could not connect to it. (ConnectTimeoutException) ". I thought maybe it was because my domain had expired, so I tried registering another -- that didn't work either.

I searched the forum already, but didn't find any solution. If it is already there, sorry, please post a link.

Thanks!

I am running on Windows 7.

PostPosted: Sat Feb 05, 2011 5:35 pm
by GJ51
First read: http://monroeworld.com/android/subsonic/

Never use port 80 - ISP's often use it or block it. 8080,8081, work fine.

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.

Learn your external IP address assigned by your ISP.

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.

Default Transcoding for video:

ffmpeg -ss %o -i %s -async 1 -b %bk -s %wx%h -ar 44100 -ac 2 -v 0 -f flv -

Stozher: mp4 > flv transcoding:

ffmpeg -v 0 -ss %o -async 1 -i %s -f flv -b %bk -r 30 -s %wx%h -acodec copy -

Good choice for frame rate is a "-r 23.976"...

PostPosted: Sat Feb 05, 2011 10:22 pm
by santucci
Yep, read that -- that's how I initially set up the server.

I appreciate your taking the time to write out the detailed instructions, but I don't see why you think it is the right solution for my issue. Like I said, everything was working before -- port 80, automatic forwarding.

I didn't change my ISP, or change my router -- all I did was put in my license key and install a new version of the software. So why would there suddenly be an issue with my ISP blocking port 80?

I have messed around with port forwarding before, it's not that I'm afraid to do it. But one of the things I really liked about Subsonic was that I didn't have to. Life is complicated enough, we might as well use the solutions that are out there and let the software do the work for us.

Anyone else have any thoughts on why I'm suddenly getting this error? Should I just install the old version and see if that does the trick?

PostPosted: Sat Feb 05, 2011 11:10 pm
by santucci
Issue resolved, by restarting Windows. :roll:

PostPosted: Sun Feb 06, 2011 2:38 am
by alphawave7
santucci wrote:Issue resolved, by restarting Windows. :roll:


That will be Gary's next How-To! :p

PostPosted: Sun Feb 06, 2011 4:27 am
by GJ51
Yeah, guess I should include the obvious. :oops: