ConnectionTimeoutException

[Monotonousblob]

I have subsonic set up and it has found my router on default port 80, but when trying to access the server using either my ip address or subsonic address, I get the message:

Status: xxxxxx.subsonic.org is registered, but could not connect to it. (ConnectTimeoutException)

I don't know what to do to correct this, my router has UPnP enabled and allows port-forwarding, but I still can't access subsonic outside from the localhost.

[bruce2101]

I am having this exact same problem, with the same error message. I've tried manually port forwarding and automatic, and nothing seems to help.

[delcypher]

You need to give a lot more information than that if anyone is going to be able to help you.

What operating system the server is running on?
e.g. Ubuntu Linux 9.10

What Subsonic version and install type (e.g. installer or stand-alone) are you using?

What are you trying to access subsonic from and where from?
e.g. web browser on the same machine as the server

Can you access the subsonic server locally, i.e. on the same machine that is running the subsonic server?

Which IP address are you talking about when you are accessing?
e.g.
127.0.0.1 (local IP)
192.168.x.x (local network IP)
x.x.x.x (Internet/gateway IP)

Have you checked your firewall settings to allow traffic through port 80?

[Kirk]

Also, who is your ISP? Some ISPs block port 80.

[Monotonousblob]

OK, I'm on Windows 7 64-bit using the latest beta version of Subsonic (installer). I can access the Subsonic server locally, but not from other computers or Android. I have tried using ports 80, 4040, 8080, and another port I already had opened, all of which game me the same error. My ISP is Road Runner (Time Warner) if that helps as well.

Here is a screencap of what I get when I try running the test:

[BCallahan121]

BUMP

[GJ51]

Many ISP's block port 80 and/or reserve it for remote administration of the access device.

Change to a different port number. 8080. 8081 8083 ... will work well.

I also recommend setting up a static internal ip for the server and manually setting up the port fwd rule to ensure everything works. I assign my servers from the top of the router's address range downwqard to keep them out of the way of dhcp assignments of the router. I use 192.168.1.254. 192.168.1.253 and so on for servers and fixed equipment such as network printers and VOIP equipment. Once you lock in addressing to fixed devices/servers port fwd rules don't get bollexed up when routers reboot or things get changed. Also set the NIC's to use the address assigned in the router so that both ends are on the same page. It takes a little work to do the initial set up, but it saves a ton of chading your tail around in circles and doing the same fixes over and over when anything on the network changes.

Know your router, know your gear, take control of what they do. Let dhcp handle temporary and wireless connections. You'll have far fewer headaches in the long run.

Good luck.

If you have specific questions please ask and I'll try to help if I can. Understand that each router is unique and the details within the setup pages are not the same as my equipment, but the common functions for all routers do the same things.

[tomosius]

I also recommend setting up a static internal ip for the server

How do I do this on Ubuntu 10.10? Do I do this in my router settings or in subsonic settings?

[GJ51]

Read your router's documentation. A Static NAT just allows you to define a fixed route from the internet to a specific port on a computer on your internal network. You have an external IP address assigned to your network access device by your ISP. This is your external facing IP address. e.g. 198.218.194.52

The incoming traffic then goes to your router for distributions to the various devices on your network. If, let's say, you have setup SS to run on port 8085 on your server, and your server is at 192.168.1.254 on your internal network, you just want to define the incoming traffic for port 8085 to always go to 192.168.1.254. This is usually done on a table in your router, but the specifics are different for each router. Read the manual for your specific router to figure out how to access the table.

On the server you use for SS, there should be a way to specify what the NIC uses for its ip address on the internal network. I don't use Ubuntu, but I'm sure there must be an option for controlling the settings on the NIC. Just set it to the same internal ip address that you gave the server in the static route definition in the router. Once you've done that, the router, the server, and SS will all be on the same page and all traffic for the defined port (8085 in this example) will have nowhere else to go except to SS. Just make sure that you open the port on the server's firewall so that the traffic is received by the server.

[BLACKHAL0]

OK, I'm on Windows 7 64-bit using the latest beta version of Subsonic (installer). I can access the Subsonic server locally, but not from other computers or Android. I have tried using ports 80, 4040, 8080, and another port I already had opened, all of which game me the same error. My ISP is Road Runner (Time Warner) if that helps as well.

Here is a screencap of what I get when I try running the test:

I had the same problem. I had both UPnP *and* Port Forwarding setup on my Router. I went into the router configuration and disabled UPnP. I then manually set up port forwarding and everything began to work fine.

[GJ51]

++ Totally agree.

As much as it would be nice if these auto config setups found in many programs, would actually work, in my experience, they usually don't.

I found the same thing in Windows Home Server. The automatic configuration always failed.

Besides, if you're going to get involved with setting up a server, you really need to know how to manage your home network. Home networks tend to grow and get more complicated. If you really enjoy this sort of thing, you're going to have to learn this stuff sooner rather than later.