Subsonic Forum

OK, this puzzles me. I'm using a standalone installation on ubuntu LTS 10.04.

Both the port redirection (UPnP) and the web forward service thinks the ip address is 127.0.0.1, instead of the correct one, 192.168.1.100.

The only thing I can think is that I have several network cards, but eth1 (not eth0) is the one in use.

Sadly I don't understand java, so I can't really see where the logic fails.

I've also tried to specify --host=192.168.1.100 with the same result - e.g. subsonic using 127.0.0.1 instead.

Setting all the other interfaces to 'down' and restarting subsonic does not help.

as do I.

so I switched to DynDNS ;-}
guess there will come a fix in time.

one thing to remember is to specify the port eg. in your case:

http://192.168.1.100:4040

oeh wrote:guess there will come a fix in time.

Lets hope so

oeh wrote:one thing to remember is to specify the port eg. in your case:

http://192.168.1.100:4040

Of course, locally and if I set up the port forwarding manually it works just fine

Port forwarding I don't mind to fixing manually, but I do find the *.subsonic.org stuff very valuable and would love that it got fixed.

Another thing; I switched main interface (from wlan1 to eth1 - wireless really sucks on servers (= ) about a week ago and it worked prior to the switch. Does subsonic save this sort of info anywhere?

A shameless bump so that it catches Sindres attention

twiztar wrote:A shameless bump so that it catches Sindres attention

HI.
All in it's time, this error most certainly get the attention it deserves.
Have in mind that Sindre actually has a normal day job as well ;-}

Sorry to bump an old thread, but it appears that this bug still exists. I just installed on Ubuntu 14.04 and had Subsonic automatically configure my router with UPnP - and it appears that my router was instructed to forward the port to itself (127.0.1.1:4040). So, trying to access my server remotely using my *.subsonic.org address does not work if I'm using UPnP. Using manual port forwarding, it works just fine.

Worth noting is that I am coming from a Windows 7 installation that was working properly, and that all other threads I have seen which mention this problem are from people running on Ubuntu. This seems like it should be a pretty minor fix, hopefully we can get this addressed!