subsonic.org is registered, but could not connect

[CarstenM]

Hello with my first post,

I am with interest investigating Subsonic. I have one problem though. My easy to remember internet address is registered but will not connect.
I get an HttpHostConnectException.

What can I do to overcome this??

Regards
Carsten

[hornetjockey]

I have noticed that the subsonic.org DNS service seems to make a silly assumption; I'm still working to confirm this.

I assume your scenario is something like this:

Two or more computers behind the same NAT router, one is your sever, the others are your workstations.

When accessing myserver.subsonic.org from outside your LAN, it correctly directs you to your router's IP, and assuming you have port forwarding set up correctly, it brings up your subsonic server.

When accessing myserver.subsonic.org from inside your LAN, the subsonic DNS service sees this and directs you to localhost, assuming that you are connecting to your server, FROM your server.

If that were the case, redirecting your browser to localhost would work, but if you are on a workstation that is not hosting subsonic, it fails.

The assumption seems to be that if the subsonic DNS service sees your request coming from the IP currently registered with them, that you are coming from the same host. The inclusion of NAT in the equation makes this assumption false and silly. DynDNS doesn't do this, which is why I've switched.

That's what seems to be happening to me. It's entirely possible that I've completely blown your problem out of proportion, too.

[adico]

when can we expect a a fix for this issue?

[atlana]

same issue here,
CAN connect wonderfully via IP:PORT but via myserver.subsonic.org it's a no go, getting also the "HttpHostConnectException" error.

I noticed though that the virtual-DNS has some issues regarding the ports, it automatically assumes you're hosting subsonic-server on the HTTP port 80. which in my case is not possible since a different service/program is already occupying port 80 (TeamViewer). It seems when you register your myserver.subsonic.org virtual-domain, it does NOT forward also the non-standard-http port you're intending to use.

I personally do not have any issues accessing my subsonic-server via IP:PORT from WITHIN my LAN, considering that my subsonic's "outbound visible IP" is my VPN-service's IP (who has Remote-Port-Forwarding); which still works like a charm accessing my subsonic server via IP:PORT.

So, is that a design flaw or intended that the virtual-DNS goes automatically to port 80 "only"?

if that's not intended, how can i change that port ?

[jerryyyyy]

Hi, I am having this same issue. Looks like it is not resolved. I have registered and paid for my domain, but it is not seen externally. If I use the correct port and external IP address, I can see the server. Ideas?

[Qbix]

Still not working?
Did you try to run a DNS resolve to see if your IP is showing up?

[GJ51]

All these issues are most likely due to improper router setup.

DO NOT use 80 or 443 for Subsonic.

DNS - is NOT involved. Subsonic.org is just a redirection service that routes servername.subsonic.org back to the host server that registered the name. Let's use my public server set up on my network at 192.168.1.252 as an example. I have Subsonic congigurd to use port 8092 for http and 452 for https. My external ip address provided bu my ISP is 108.17.27.224.

The first step that has to be taken is to set up the ports used by SS. I would suggest only setting up http first and getting that working properly before implementing SSL.

After installing SS and telling it to use port 8092 I then had to tell the router to send all external requests for 8092 to 192.168.1.252 by setting up a working forwarding rule in the router. That way, whenever anyone requests http://108.17.27.224:8092/ through a browser the router knows that it must send the request to 192.168.1.252, the internal address. SS is there listening to port 8092 and responds.

So when I go to setting/network in SS and enter my servername, http://maplegrovepartners.subsonic.org and hit the Save button, the program sends the name to the subsonic.org server and tell it that this instance of subsonic is at http://108.17.27.224:8092/

Therefore, whether you request http://108.17.27.224:8092/ or http://maplegrovepartners.subsonic.org you still get a response from my server. The subsonic.org service just translates the request and send it to the proper ip:port#

If your port forwarding is not set up properly, Subsonic will still SEND the information to the subsonic.org server, but if the port forwarding is not valid it will not be able to verify the connection because it can't get through your router to get back to the server.

I've been through this hundreds of times with many users both here on the forum and through email and pm's. IT"S ALWAYS THE ROUTER SETUP. Well 99% of the time anyway. I suggest setting up SS on port 808X and then verifying that the port is open with canyouseeme.org

The complete guide is here: http://forum.subsonic.org/forum/viewtopic.php?t=4867

Also remember that even after you enable ssl, subsonic.org still uses http to make the initial connection. You still use the http address to connect. Once the connectiopn is established, your sever will respond and initiate the https connection. So if you are able to connect using your ip:sslport# but can't connect with the subsonic.org name, you most likely do not have the http port open.

[momerath]

I can confirm an issue with subsonic's DNS mechanism, which is definitely not related to port-forwarding. My port-forwarding has been working for some time, as evidenced by my usage from android over 3g.

I just upgraded to 4.5beta1 for the linking feature, which requires a subsonic subdomain (why, exactly?). I registered one, and it works perfectly from outside my LAN.

However, if I make the request from inside, the resulting IP is one of the server's VPN IPs, even after explicitly setting the host to bind to (subsonic.sh) to the NAT IP (which would be the most useful for the subsonic DNS to respond with to requests from within the NAT, obviously).

It doesn't really get in my way, but I thought I'd do my beta-testing duty and report it.

[GJ51]

The myname.subsonic.org service does not use DNS.

[momerath]

Of _course_ it uses DNS. I'm sure you mean that dns resolves to a subsonic ip, and the web server redirects to the IP and port your server has sent it. So what?

The important part of my post is that the IP it redirects to depends on whether the requester is inside the same NAT (has the same external ip); in this case, it redirects to an IP that was obviously meant to have been the internal IP, but is, in my case, a VPN IP, despite my having set the internal IP explicitly in the startup script.

[GJ51]

Let me clarify: The myname.subsonic.org service is not based on DNS but uses HTTP redirect to forward the REST requests to the user's server.

For instance, if you type http://sindre.subsonic.org in your browser you will be redirected to http://79.161.78.5.

http://forum.subsonic.org/forum/viewtop ... t&start=15

[rickrack]

Hi, when I type my http://rickrack.subsonic.org it tries to redirect to my internal IP address, which works when I am inside my lan, but from outside is not visible and so I have no access to my music. Port forwarding is all set up correctly as far as I can see. It looks like the problem is due to whatever is redirecting to my pc/server is redirecting to my internal ip address rather than my external static ip address.

[vsteel]

I hope this helps but here is what I did.

I had port forwarding setup in my router. So for example my external port was 100 but in my local network my computer was really listening on port 8080. When I tried to use the http://<YourSiteName>.subsonic.org address it kept forcing port 8080 because that is what the server is using but not what is really seen outside on the Internet. So if I tired the address on my home machine it would recognize that I was inside my local network and just hit the 192.168.0.100:8080 address which of course worked because it had the proper port. Hitting it on another machine that wasn't inside my local network failed because it also was trying to hit the address 44.55.66.77:8080 which wasn't open. Address 44.55.66.77:100 is the port which is open.

So to force the port here is what I do. Change your settings file (/etc/default/subsonic) to use port 100, or whatever you have open to the outside world, next restart the server, then go to your network settings and hit save to update your http://<YourSiteName>.subsonic.org address. Change the settings file back to what it used to be, the port that you used to have open in your local network. Restart the server one more time. Now when you are not at your local machine you can hit the http://<YourSiteName>.subsonic.org address and it will hit the correct port.

It will break the local port address, so if you try the http://<YourSiteName>.subsonic.org address it won't work because now the local network is trying to hit port 100, but I have the correct IP version saved as a bookmark on my local machines (the bookmark is saved as 192.168.0.100:8080 on my machine).

I do wish that there was a field that we could set the local and remote port so the address would work no matter where we were.

I have my machine setup on a port that I probably shouldn't because I like to listen at work and my work blocks pretty much all ports but just a few. So having tons of other ports to choose from is not an option for me. (My work is fine with me listening to the music, it just has to come through a port they have open.)

[GJ51]

Hi, when I type my http://rickrack.subsonic.org it tries to redirect to my internal IP address, which works when I am inside my lan, but from outside is not visible and so I have no access to my music. Port forwarding is all set up correctly as far as I can see. It looks like the problem is due to whatever is redirecting to my pc/server is redirecting to my internal ip address rather than my external static ip address.

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

[vsteel]

Hi, when I type my http://rickrack.subsonic.org it tries to redirect to my internal IP address, which works when I am inside my lan, but from outside is not visible and so I have no access to my music. Port forwarding is all set up correctly as far as I can see. It looks like the problem is due to whatever is redirecting to my pc/server is redirecting to my internal ip address rather than my external static ip address.

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

I think the problem is that on the server SS is listening on port 8081. The router then port forwards this to port 100 (or whatever) to the rest of the Internet. The server at subsonic.org just assigns the port that is on the server. So when you use the http address it then redirects to 12.34.56.78:8081 but that port isn't open, port 100 is open.

I guess the question is what is the best way to force the port that the subsonic.org site directs to? In this case he wants the http address to use port 8081 on the local LAN but for everyone else out on the Internet it needs to direct to port 100 because the router will forward it internally to port 8081.