Subsonic Forum

I use the " Access your server over the Internet using an easy-to-remember address." feature of subsonic which has been really smart about returning the appropriate IP if I'm on the same network as subsonic or external. I recently started using docker (not with subsonic, just one the same box) and it looks like subsonic is returning an IP from the docker subnet now when I hit the *.subsonic.org address locally. Externally the address is fine. I suspect the way subsonic is calculating it's own local IP is incorrect. Below are my findings (address masked as xxx)

Code: Select all

# curl -v xxx.subsonic.org
* Rebuilt URL to: xxx.subsonic.org/
*   Trying 66.49.215.227...
* Connected to xxx.subsonic.org (66.49.215.227) port 80 (#0)
> GET / HTTP/1.1
> Host: xxx.subsonic.org
> User-Agent: curl/7.42.1
> Accept: */*
>
< HTTP/1.1 302 Moved Temporarily
< Server: Apache-Coyote/1.1
< Access-Control-Allow-Origin: *
< Location: http://172.17.42.1:4040/   #docker subnet
< Content-Language: en-US
< Content-Length: 0
< Date: Sun, 23 Aug 2015 01:14:33 GMT
<
* Connection #0 to host xxx.subsonic.org left intact

Build: 5.2.1 (build 4428) – March 4, 2015

Hi,

maybe this problem is related to mine, which concern the upnp server feature of subsonic with multiple eth interfaces ?

viewtopic.php?f=2&t=15944