Subsonic Forum

I just set up my Subsonic server. Oddly, I can access it via the cell network on our phones, but cannot access it locally, either via wifi on the phones or from another computer on the local network.

Any ideas?

Thanks, Bill

If you tell us what address you are typing in might give us a clue

*.subsonic.org

MOD: Edited out address

I can see your server ok
I would suggest you do not use port 80 as that can sometimes can get blocked.
Also you need to change admin password.

ok. I changed the pw. Then I followed the directions to change the port.

- I gave the server computer a fixed IP address (192.168.1.110)
- In the router's firewall I forwarded external calls as indicated in the doc. I set up
. inbound 80 to 192.168.1.110 port 80
. likewise, 4040 to 4040 and 8080 to 8080
- In the Subsonic Control Panel I set the port number to 4040 and restarted the server. Couldn't access the server from local network or cell phones
- Likewise when I tried 8080.
- Finally I decided that external 8080 should be forwarded to internal 80. With that I can access from my local network (192.168.1.110:8080) but cannot access at all from either of my cell phones, whether or not they have wifi enabled.

Hmm, doesn't make sense that you could access it on port 8080 from the internal network if Subsonic is only listening on 80 internally. Try this:

Ensure that Subsonic is listening on port 8080 (restart the service after saving the change to make sure)
Set your router to forward external requests on port 8080 to the server on port 8080 (no mixing and matching of 8080 > 80, etc)
Check to see if the service works on the internal network on port 8080
Use your phone (no wifi) to connect to your external address on port 8080

Sometimes trying to access the external address (e.g. me.subsonic.org) from an internal device will not work since some routers do not support loop-back (essentially calling out to an external address when the device it ultimately leads to is internal)

My router does not properly handle loopback requests so in my Android app I have two profiles (one with a local IP reference to my server, and one with the external address) and I switch them depending on whether or not I'm on my home wifi.

Just out of curiosity, are you running Windows? If so, disable Windows Firewall on the server and try it also. Sometimes Windows Firewall only allows traffic to certain applications if the network is considered either "Home" or "Work" (their version of trusted). If disabling it works, check there.

I played around some before you replied and here's what I have right now ...

- The router forwards 8080 to 80 (and 4040 to 4040). The server is listening on 8080. Surprisingly, this works. I should have thought this would cause problems if traffic is going to 80 but the server is listening on 8080.

- I can access the server on the local network at http://192.168.1.110:8080/

- On my Sprint Android phone and my wife's T-Mobile Android phone I can access the server at

http://72.191.31.224:8080/ via the cell network (only)
http://192.168.1.110:8080/ via wifi (only)

My router supports dynamic dds via dyndds.org and I'm thinking of using it since that might give me a single address I could use. But if loopback in the router is the issue, then probably not.

Yes, I'm running windows. I can try killing the firewall and see what happens ...

Mean time, I'll try your suggestions and see what happens.

So what exactly is NOT working as you seem to be able to access SS with no problem
The only thing I cannot see in your list is your subsonic.org address which I know was working ok.

Well, my gripe is that I have to switch back and forth between servers: use the local address (192...) at home on wifi and the remote address (72...) when using the cell network. Granted it's a nit, but I was hoping for a resolution. I guess the problem likes in my router.

And, no matter where I am, I don't seem to be able to use the http://blearyeye.subsonic.org:8080 address.

blearyeye wrote:And, no matter where I am, I don't seem to be able to use the http://blearyeye.subsonic.org:8080 address.

That is because that is wrong.
You do not specify the port no. when using the name.subsonic.org address, that gets taken care of automatically.

I guess I finally figured it out. In my original post I had left out a key piece of info. I had previously had Subsonic hosted on one machine, then tried to move it to another machine. Apparently that's where things got confused. I changed the name of the server to blearyeye2, and all works well.