Page 1 of 1

Odd Problem - Can't Connect to SubSonic via IP Address

PostPosted: Mon Apr 06, 2009 2:39 am
by Necro
I'm having an odd issue - I can't connect remotely to Subsonic at all. I can bring the page up locally but when I try to connect to it remotely, nothing. Just times out.

I'm attempting this on a WHS SP2 setup with the Windows Installation verison. I have other server software configured and am able to get into it using specific ports (one being the uTorrent WebUI), and I'm able to access the server via the normal port 80 web page interface...but no matter what port I change subsonic to the page won't load.

No firewall (software-based) running on the computer I'm trying to use to connect with and my router is running Tomato firmware but I don't think that should be restricting anything on my LAN.

Any suggestions or ideas would be greatly appreciated.

Edit: Interesting item - if I access Subsonic from the WHS computer itself using the computers IP instead of localhost, it goes to a white page and doesn't bring up the Subsonic server.

Re: Odd Problem - Can't Connect to SubSonic via IP Address

PostPosted: Mon Apr 06, 2009 6:25 pm
by jigsaw
Necro wrote:Edit: Interesting item - if I access Subsonic from the WHS computer itself using the computers IP instead of localhost, it goes to a white page and doesn't bring up the Subsonic server.

Sounds like maybe you setup subsonic to only listen on localhost (127.0.0.1) and not the public ip-address of your WHS? That could explain this behaviour..

PostPosted: Tue Apr 07, 2009 4:13 am
by bertraze
I've been looking all over for such a setting and have been unable to find one. (I know the port is forwarding correctly since I tried another app on the same port.)

Where is the setting that limits it to localhost?

Thanks!

PostPosted: Tue Apr 07, 2009 6:40 am
by jigsaw
bertraze wrote:Where is the setting that limits it to localhost?

Well, that depends on whether you're running a Tomcat version or standalone I guess.

The simplest way to verify which ip and port you are listening to just open up a cmd-window and type
Code: Select all
netstat -an | find "LISTENING"

PostPosted: Tue Apr 07, 2009 11:58 am
by bertraze
I'm running the Windows version. I tried that command and I am listening to 0.0.0.0:<port number>. I don't really know how that differs from some entries that are [::]:<port number>, but at least it isn't 127.0.0.1:<port number>. I do see some of those.

PostPosted: Tue Apr 07, 2009 12:02 pm
by bertraze
For what it's worth, I started a different canned webserver (which I can access from other computers), and it is apparently listening to [::]:<port number>. I'm not sure how to change the setup for Subsonic, though. I'm pretty new to running a webserver.

PostPosted: Tue Apr 07, 2009 6:37 pm
by jigsaw
0.0.0.0:<port number> basically means all, so that's good.

You could try disabling whatever you have running on port 80 now and try running Subsonic on that port. If that works you at least have pinpointed the problem. I am liking the Router with Tomato as the culprit at this time, but I have never used it myself. It's also been ages since I ran the windows version so I'm not too familiar with that either.

PostPosted: Wed Apr 08, 2009 10:09 am
by Jarod_
I had the same issue as you.
With Vista, it seems the Windows Firewall blocks the application. You need to manually add the Subsonic port into the Windows Firewall! And then it works :-)

WHS

PostPosted: Wed Apr 08, 2009 11:31 pm
by koboabe
I have Subsonic running fine on WHS.
I needed to add an exception to the windows firewall and my router, but it works great