Network error on Android app

[interr0bangr]

So I think there's been a million threads started about this issue but none of them ever seem to have any solutions.

So here's my deal...

- On any computer, I can easily connect to my Subsonic server without any issues
- On my phone, when on wi-fi, I can easily connect to my Subsonic server without any issues
- On my phone, when I turn off wi-fi and use 4G I can access every other website and streaming service with no issues, including the Subsonic "demo" server but when trying to connect to my server there's a 75% chance I receive a "Network error occured, retrying, 1, 2, 3, 4" type of error

It works, on occasion, usually if I've had wi-fi off for an hour or two and I try to connect again. It seems extremely random however especially since I can connect to the demo server 100% of the time. When trying to test the issue, i've found that if I try to connect via 4G immediately after turning off wi-fi there is a 100% chance I won't be able to connect to my home server.

Is there some sort of setting or fix that can solve this issue so I can reliably connect via 4G? Or even some sort of app or whatever that could flush my phone's internet settings when needed if it has anything to do with that. It's a crapshoot for me at the moment and it's the one thing that makes me question if I want to subscribe to Subsonic regularly.

If it helps, my server address is http://interr0bangr.asuscomm.com/subsonic and can be logged in via the "guest/guest" username and pw combo.

Thanks.

[gurutech]

Try adding :4040 to the address. I have the same issue and that works for me.

[interr0bangr]

My server is on port 80 because that's the only way I could get it past my filters at work. Putting a port at the end of any URL immediately causes my work to block any connection.

I will play around with that though, thank you.

[interr0bangr]

So i think the problem stems from my DDNS server I was using. My router (ASUS RT-N66U) has built in DDNS functionality (hence the asuscomm.com address) but I tried using no-ip.com's DDNS service last night instead and so far it's smooth sailing with no connection errors!