Cannot access my subsonic address locally

[jonnymnemo]

Hi,
I registered a subsonic address (xxxxxx.subsonic.org)
When I try to access it from a remote connection, it works perfectly.
But, when I want to access it locally, it doesn't work, and redirects me to a wrong ip address.
My subsonic server runs on 192.x.x.37 and my subsonic address redirects me to 192.x.x.32 (where was my first server)

My server runs on Ubuntu 11.10 (GNU/Linux 3.0.0-17-generic i686)
Version 4.6 (build 2585) – 6 décembre 2011
Serveur jetty-6.1.x, java 1.6.0_23, Linux (64,4 MB / 135,4 MB)


On my laptop (on Windows 7) I tried to clear the dns cache with ipconfig /flushdns
I also tried to clear the google chrome dns cache at chrome://net-internals/#dns
I tried with another browser. I tried with my smartphone (android) with the subsonic client (it works remotely but not locally). I tried with another computer which had never accessed to subsonic before.
My router is a Freebox Revolution (v6). I also tried to hard reset it.
Nothing works.
To enter subsonic locally, my only option is to type the ip adress and port directly.

I suppose there is a way, but does somebody has the answer?
Is there a way to correct this redirection problem ?

Thanks very much !

[BKKKPewsey]

settings/network and hit save
That will force an update of the subsonic.org address.
Then try again.

[jonnymnemo]

Already tried... doesn't work either !

[BKKKPewsey]

Hmm! this is the second post which appears to have a similar problem - viewtopic.php?f=2&t=9324#p39593
Can you access subsonic via the subsonic.org address outside of your local domain?
If its difficult to check pm me your subsonic.org address and I can check from my end.

[jonnymnemo]

Actually, there is no problem with an external network. my subsonic address works perfectly in this case.
I think that my subsonic redirection was set up with my previous server (which was on 192.x.x.32).
So, it works well on an external network, because I changed the redirections on my router.
But in local network, it has not been updated.
The subsonic address needs to point to 192.x.x.37, and still points to 192.x.x.32
Also, sometimes, in the settings/network, it says that my subsonic address is already in use, and when I save again, it says "XXXX.subsonic.org responded successfully"
I'm sure the previous server is completely down (i removed it completely)

Is there a way to configure manually my subsonic address (xxxx.subsonic.org) ? Or to reset it completely ?

[BKKKPewsey]

OK if its working correctly outside your local lan then the problem I believe is with your router.
Hopefully someone else will tell me if I am talking out of my a$$ (a situation not unheard of )
but I believe that when you are on your local lan when the information comes in from the subsonic redirect, which uses your external IP,
the router says Hey! that on my lan and will change the IP to 192.168.0.xxx:portNo. thus making it local only.
In your case the router is picking the wrong (old) xxx.
Hopefully someone with a greater knowledge of routers and things will confirm.

(Roll drums and wait for yteckie or GJ )

[jonnymnemo]

I already thought of this issue, so I made a hard reset of my router. It doesn't work either...

[jonnymnemo]

Is still doesn't work even with a complete reset of my isp router/modem.
I posted on the isp bugtracker to see if they have an answer to me, but if nothing comes out of it, I will have to change my subsonic address or to come back to my old ip (with everything to configure again )

[Swixxy]

Also it won't be a router issue, most routers dont have the capability to forward locally like this. Try typing in your Actual IP address into a browser, and it wont forward you to a local IP, unless you have an enterprise class router thats been setup to do this.

Try an ifconfig in the terminal, sounds like you may have more than one network adapter, probably one left over assigning your old server ip, and one for your new one which instead of overwriting has made this instead?

Since if its grabbing your 'old' IP it has to get it from somewhere, unless its not updating it at all. Try adding a 1 or something to the subsonic.org name and see if it updates to the old IP again, if it does its getting it from somewhere on your PC, if it uses your actual local IP then it might be some odd error not letting it update the old ip in the web server

[gurutech]

Run a ping test to your xxxxx.subsonic.org address from within your network, and also from outside your network.

I have the same problem, but was able to workaround it by using the actual "server" name of the machine running subsonic, rather than the subsonic.org address.

The problem is that the router (at least in my case) is configured to only use an external source for DNS, and not use "itself" as the primary DNS, then forward to your ISP if it can't find the lookup. It just forwards without bothering to lookup the IP. So when I ping my subsonic address from inside my network, I get some weird (but valid) IP address outside my personal network that isn't even being used, but if I ping my subsonic address from outside my network, I can reach the appropriate server.

[GJ51]

Something definitely sounds a bit bogus here

It makes no sense that the external address is accessible on on internal ip 192.x.x.37 and intenally on 192.x.x.32 if I'm reading you correctly, unless you have two instances running on the same network.

As confusing as this all can seem, it is really much more straightforward than it seems at first, if you take it one step at a time.

First verify which internal port and ip address the server is running on. In Windows installs you click on the tray icon and open the local instance in the default browser. The browser address will read http://localhost:port#/index.view I'm not sure how you do it in linux, but you do need to verify the port number that the server is using. Again in Windows you can right click on the tray icon, open the control panel and verify that the Settings tab port assignment matches what you saw when you opened the local browser instance.

Once you have verified that the port number is correct, you next need to determine the servers internal ip address. Again, I'm a Windows guy, so I would open a command prompt and type ipconfig /all and determine the IPv4 address. At this point you should know for certain the internal ip and port number.

Next go to canyouseeme.org and verify that Subsonic is responding on the assigned port.

All routers are a bit different, but all my routers have always responded to the server.subsonic.org address when used internally. It will almost immediately be translated into the internal ip:port# when you are inside the local network. I have used several consumer grade routers and all of them have behaved this way.

If the port forwarding rule doesn't match the internal address for Subsonic, there are two ways to skin the cat. You can change the forwarding rule in the router, or, perhaps easier, manually change the ip address of the server to use a fixed ip matching the forwarding rule in the router.

If it turns out that you can't use the server.subsonic.org address internally (I've never seen this on my network) then you just have to use the internal ip:port# to access inside the network or edit the local hosts files on all the workstation to do the DNS internally. (Nobody wants to edit local hosts files - too tedious.)

HTH - Let me know if you have more questions.

[jonnymnemo]

Actually, it was working fine from an external connection, because the forwarding rule in the router was telling to go to 192.x.x.37.
The problem was inside, and I didn't find a way to correct this. It was not a problem with the router or with my computer (I even tested with a live cd).
I finaly never found the reason why it was not working.

The workaround I found was to put back my server on 192.x.x.32. Now everything works perfectly, from outside and inside.
Thanks for your answers anyways !