Page 1 of 1

Server just doesn't work, and i can't figure out why.

PostPosted: Sun Apr 04, 2010 7:57 pm
by Demi
So, I set up Subsonic, and tested my domain [demi.subsonic.org] and yet, it's telling me that it's set up, but not working.

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

Anyone know how to fix this? It could be a port forwarding issue, but if it is, I have no idea how to fix it. I'm on Verizon FiOS if that helps. Thanks in advance! :)

-Demi

PostPosted: Mon Apr 05, 2010 10:40 pm
by ootuoyetahi
What port(s) is subsonic listening on? Have you opened this (these) port(s) on your routeR?

PostPosted: Mon Apr 05, 2010 10:46 pm
by 3R3
most of the time you have to let someone else test your servers availability from outside. just because you can not connect to your subsonic.org-adress from inside your lan, does not mean someone else cant connect from the internet.

PostPosted: Mon Apr 05, 2010 10:50 pm
by jcettison
3R3 wrote:most of the time you have to let someone else test your servers availability from outside. just because you can not connect to your subsonic.org-adress from inside your lan, does not mean someone else cant connect from the internet.


Eh, poor reasoning.

Even still, if you needed to test from outside you need not have an additional person, you can test through a proxy. Google will help you with many available free web proxies that should do the job fine.

Demi wrote:So, I set up Subsonic, and tested my domain [demi.subsonic.org] and yet, it's telling me that it's set up, but not working.

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

Anyone know how to fix this? It could be a port forwarding issue, but if it is, I have no idea how to fix it. I'm on Verizon FiOS if that helps. Thanks in advance! :)

-Demi


Couldn't you just use your IP? Or is it dynamic?

You could always setup a service like DyDNS or whatever and forgo their subdomaining alltogether.

PostPosted: Mon Apr 05, 2010 11:46 pm
by Demi
So, thanks for the replies, but I figured it out. Apparently, it was a port forwarding issue. I was forwarding to the wrong port.