Connection to subconic.org refused

[usalabs]

Well guess what, I have everything working and access is possible from outside the LAN using http://saundcom-music.no-ip.org but when attempting to register my SS server on subsonic.org in the Network options of SS, I get:-

Status: Failed to test web address. Connection to http://subsonic.org refused (HttpHostConnectException)

I searched this forum and everyone seems to think it's a router problem, WRONG!, if I and anyone else can access my SS server login page using http://saundcom-music.no-ip.org then subsonic.org should have no trouple either, my assumption is that subsonic.org's forwarding server is set to use port 4040 by default, and any SS setup that uses a port other than 4040 is refused connection, I can't use 4040, hence the use of 8080, and further more, SS's uPnP detection stinks big time, I'm using a NetGear WGR614v9 router with uPnP enabled, and SS can't detect it, "Router not found", so I had to manually forward port 8080, and disable SS use uPnP option.

[GJ51]

You are right about Subsonic and Plug and Pray. I always do the manual setup.

But you're wrong about Subsonic using the 4040 default for the vanity url.

It's a simple redirection service, When you save the url in network settings, Subsonic transmits your license information, your external ip, and the port number that Subsonic is using to the redirection server.

When someone requests http://myserver.subsonic.org the request is routed in reverse order wherein the.org domain locates subsonic.org which in turn see a request for your servername and then uses the registered information in it's database to then send the request to http://http://72.201.109.97:8080/login.view?

If Subsonic is not accepting your request to register the requested name, there could be a problem at their end that could be related to your license or perhaps that name already being used.

Your site is responding to http://saundcom-music.no-ip.org, so it is open. I don't know your setup, but I've often seen this type of issue in the Linux camp when users try to set up a double reverse proxy with a half - gainer and a double flip. You aren't one of those guys are you?

[usalabs]

I've often seen this type of issue in the Linux camp when users try to set up a double reverse proxy with a half - gainer and a double flip. You aren't one of those guys are you?

No, definately not, lol, I don't uses proxies, or VPN, just a server and router and dynamic DNS service.

For future knowledge, my setup is OpenSuSe 11.4 (runlevel 3) on a quad core AMD A6-3650 APU, with 8GB RAM and 1TB HDD, Apache, PHP5, Mysql, and SSH, (Mysql and SSH only have local LAN access), only Apache has WAN access, no mail server, because my ISP blocks port 25 and 110, also an Einstein is required to setup a very secure mail server using a port 25 redirection service, and setting up MX records etc, etc.

NOTE:
If anyone is trying my url for testing, and can't gain access to the login page, it's not because of url or router problems, as GJ51 said my url is accessible, it'll be because I'm still working on the server with other projects, and every so often, I have to either take down apache, or do a server reboot, but keep trying, and eventually the SS login page will be seen.

[GJ51]

"only Apache has WAN access"

My guess is that might be the place to look. Admittedly, I'm not well versed in Linux/Apache but if is the primary handler for the WAN traffic then that is most likely were the breakdown is occuring if the router is passing an incoming request to Apache.

Just a thought. Hope it helps.

[alphawave7]

Has your .org ever been registered? What does a traceroute to the redirect server return? (subsonic.canaca.com)

[usalabs]

Has your .org ever been registered? What does a traceroute to the redirect server return? (subsonic.canaca.com)

Code: Select all

traceroute to subsonic.canaca.com (66.49.215.227), 30 hops max, 60 byte packets
1  192.168.0.1 (192.168.0.1)  1.869 ms  3.413 ms  6.373 ms
2  * * *
3  wsip-184-178-205-162.ph.ph.cox.net (184.178.205.162)  15.613 ms  15.947 ms  19.797 ms
4  70.169.75.153 (70.169.75.153)  27.127 ms  26.118 ms  26.567 ms
5  68.1.5.139 (68.1.5.139)  38.791 ms  42.663 ms *
6  te0-0-0-30.ccr22.lax05.atlas.cogentco.com (38.104.84.69)  69.779 ms te0-0-0-21.ccr22.lax05.atlas.cogentco.com (38.104.84.13)  54.768 ms  55.424 ms
7  be2024.ccr22.lax01.atlas.cogentco.com (154.54.30.193)  62.299 ms be2026.mpd22.lax01.atlas.cogentco.com (154.54.6.229)  61.212 ms be2024.ccr22.lax01.atlas.cogentco.com (154.54.30.193)  61.512 ms
8  be2068.mpd22.iah01.atlas.cogentco.com (154.54.7.157)  62.589 ms  62.936 ms be2066.ccr22.iah01.atlas.cogentco.com (154.54.7.53)  69.159 ms
9  be2146.ccr22.dfw01.atlas.cogentco.com (154.54.25.242)  68.508 ms be2147.ccr22.dfw01.atlas.cogentco.com (154.54.27.18)  67.608 ms  68.072 ms
10  be2010.ccr22.mci01.atlas.cogentco.com (154.54.46.217)  79.034 ms be2141.mpd22.mci01.atlas.cogentco.com (154.54.5.157)  78.628 ms be2010.ccr22.mci01.atlas.cogentco.com (154.54.46.217)  78.012 ms
11  te0-2-0-5.mpd22.ord01.atlas.cogentco.com (154.54.88.54)  94.719 ms te0-7-0-4.ccr22.ord01.atlas.cogentco.com (154.54.30.102)  95.151 ms te0-5-0-1.ccr22.ord01.atlas.cogentco.com (154.54.84.78)  78.915 ms
12  be2082.ccr22.yyz02.atlas.cogentco.com (154.54.28.10)  93.035 ms  91.605 ms  96.339 ms
13  38.111.102.68 (38.111.102.68)  93.779 ms  94.742 ms  99.016 ms
14  66.49.255.5 (66.49.255.5)  96.995 ms  97.705 ms  97.306 ms
15  subsonic.canaca.com (66.49.215.227)  102.391 ms  101.984 ms  101.213 ms