Subsonic Forum

After many months of happy video streaming, my subsonic android app cannot seem to connect. I now get a network errors 1 through 4 and then have a network error.
I previously used the PC netbios name, but the same error comes up with http://192.168.0.100.

Any suggestions, or is there a logfile somewhere I can check? Thanks in advance
Cliff

I can reach subsonic using my xxxxx.subsonic.org address. Trying to access it with a http://192.168.0.100 doesn't want to work. I assume this has something to do with increased license checking.

If I access my subsonic server using the xxx.subsonic.org while on my local LAN, will it stream directly to the phone, or is it going out on the internet?

And your SS version is ?
Is the problem only affecting the android client?

Also make sure your server hasn't changed its internal IP address

I'm using Beta 4.61 build 2501. My server has an address assigned to it by the router, and I've confirmed it is correct.

Does anyone know if accessing xxxxx.subsonic.org from my local lan will incur internet connections?

My subsonic version is: 4.6.beta1 (build 2501) – November 1, 2011

My server ip address is static dhcp from the router, and I've confirmed it hasn't changed.

If I enter
http://I5 OR http://192.168.0.100
from a browser it works. It brings up a subsonic login.
However, using either one from my android app results in a network error. I see nothing at the subsonic server.
Using
http://xxxxx.subsonic.org
does work, but I'm worried this will incur internet traffic even though I want to stream on my local LAN.

I am assuming this new restriction is a licensing thing(?). Am I doing something wrong? Is there a logfile somewhere I can view?

PS: Sorry about the multiple names, bluetooth and clifford are both me.

You are probably correct in your assumption in the extra security precautions being the root cause.
I am not an android user so I may not correct but the only internet traffic should be accessing the subsonic.org server to get the redirect and then you should be back within your local lan.
This is how it works within a web browser so I cannot see the Android client working differently.

I am getting this issue now, and the frustrating part is that is hit or miss. Sometimes it works great, but it seems more and more often I am getting network error 1 through 4. I am using ss 4.6 and am updated to the latest android version. I'm also wondering if there is some kind of log to check to see if I can diagnose this issue.

Love, love, love subsonic, by the way.

edit: I'll add that it works fine from anywhere else, and I can even browse the subsonic page from my phone's browser. I had also changed the android app server config to use dyndns instead of subsonic, both seem to produce the same hit-or-miss results.

Does anyone have any ideas on how to resolve this?

This is most often the result of poor bandwidth. If you're on a strong wifi connection within the local network getting strong bandwidth, it should load quickly. If you try to connect over a poor 3g connection you'll see it take 2-4 attempts to load the list. If it takes too long, the server will time out trying to make the connection and terminate.

I guess this problem could be exacerbated by a really long list then?

By the way this is being accessed by a 4g phone with a nice strong signal.

Are there any ways to adjust the timeout settings? Also is there a log of some sort that I can use to verify this theory?

YES! folder structure can be a problem. X:\Music\Artist\Album\tracks is the preferred library setup for SS.

Just dumping tons of tracks into a single folder will kill things.

Logs: Read the "About" screen.

UPLOAD speed from the server is also a factor.

I do believe there are ways to mod the timeout. They are probably discussed somewhere here in the forums. Try using the search feature.

You will get much better overall performance if you set up the library as suggested. Increasing the timeout might prevent the termination of the connection, but performance will still be really slow.

I was able to resolve this by invoking 'clear data' on the android app.
HTH