Today, I tried to install Liquidsoap on Windows Server.
I installed a Windows Version of Liquidsoap and everything works (reading playlist, mp3s, ...) but I have a problem.
When someone tries to connect to my audio stream, it works but he gets disconnected in 1 second (so he has 2 seconds of music and nothing else).
Where can it come from?
In debug I get :
2012/05/08 16:19:23 Client .... connected
2012/05/08 16:19:23 Client .... disconnected
Thanks for your help.
Related
I have an issue with a single (at least for now) iPhone not being able to connect to websockets. Unfortunately I don't have access to the device and I can't run more tests on it at the moment, so no proper network dumps or anything else deeper level debugging available. Can't test on other network connections either at the moment.
Everything works perfectly with Chrome 45, Firefox 40, Chrome 45 on Android (many devices), Safari on iOS9 (device A), Safari on iOS8 (device B) etc. No errors, no cutoffs, nothing. Just works.
My websocket server runs on IIS 8.5 / ASP.NET, created as an API controller with the typical way (PullHandler is an async Task whileing until connection closes)
if (HttpContext.Current.IsWebSocketRequest)
{
HttpContext.Current.AcceptWebSocketRequest(PullHandler);
return Request.CreateResponse(HttpStatusCode.SwitchingProtocols);
}
else
return Request.CreateErrorResponse(HttpStatusCode.BadRequest, "Bad request");
This should not cause any issues, especially this one. The client side JavaScript is also the simple
new WebSocket("ws://" + window.location.host + "/api/Some/Endpoint);
I am using plain HTTP, no SSL/TLS.
When trying on iPhone device X with iOS9 (13A344, not entirely sure of which model) it just can't get the connection. I am also using SignalR which automatically goes into longPolling transport on this device. With others it's nicely on webSockets transport.
Quick testing on UK Orange 3G connection showed on my HTTP logs that for some reason the request for my endpoint has gone to the else branch, like something had stripped the upgrade headers away.
GET /api/Some/Endpoint 80 - Mozilla/5.0+(iPhone;+CPU+iPhone+OS+9_0+like+Mac+OS+X)+AppleWebKit/601.1.46+(KHTML,+like+Gecko)+Version/9.0+Mobile/13A344+Safari/601.1 - 400
Status 400 is clearly showing the bad request that my code is sending if the request is not a proper websocket request. I don't know if there could be some transparent proxy, that could explain this. The 400 response was received without any delays.
But this was a problem also through wifi on the same device. Again, a laptop with OS X and Safari had no issues on the same wifi to connect to SignalR and my websocket server. Only the iPhone had issues. On wifi I didn't get any attempts to connect on the logs and SignalR also immediately went into longPolling transport. The wifi apparently used Virgin Media's network based on IP address.
On wifi there is first an open event. Then after some time there is a close event with status 1006, which is abnormal termination without a close packet. My code tries to connect again and the same happens. Strangely there is no log entry at the web server, but it might just be Safari's way to post the open event even though an actual connection was not established and after a timeout it sends the close event.
The device should not have any proxies set up and other browsing works without issues. Unfortunately I couldn't get any information about any other site that would use websockets working or not on that device.
Has anyone run into this kind of situation? I do understand that the 3G might just be a misbehaving proxy, but the wifi issue cannot be explained with that.
Just want to expand the universe for this issue.
I Have an app that runs great in simulator. App has both http Jason IO and web socket IO.
Now that I can target my iPhone and not the simulator. App on iPhone successfully does the http Json stuff but not the web socket stuff.
While I am not using safari and js my symptoms are very similar to yours. I am using Xcode 7 to generate code that targets to iPhone 5 using iOS 9.0.
Currently I am working with Streaming API (https://stream.twitter.com/1/statuses/filter.json).
After connection successful, i will record all the tweet from server into database. The problem only occurs after several hours or days of running without issue, and then no more tweets can be retrieved. If I restart the client, processing resumes as normal and everything runs fine until the next hang.
One way is you could restart the service at certain interval, let say every 3 hours so it will stay connected and minimize the issue.
In my app I am using ASIHTTPRequest to get information from a server. That works fine as long as I am using the company's wireless.
However, I need to connect now from outside of the network, by using Cisco AnyConnect. On the PC, the connection to the server via VPN works but I cannot reach the server through the app. I always get timeout although I have increased the timeout interval to 60 seconds (which is already too much).
Is there something special that I need to change in the code when I use AnyConnect? Right now, it does not automatically detect the proxy, I get (null) as proxyHost and 0 as proxyPort.
Thank you a lot for the help, #MarkM. Using the IP solved my problem. I just replaced http://<some-words>.local:<port>/<remaining-part-of-url> by http://<IP>:<port>/<remaining-part-of-url> and it works.
Am using open fire server and iOS xmpp client with Robbie Hanson's framework. My clients runs fine in background, as i have set the voip flag and everything. But after few hours around 15-20, it automatically gets disconnected. Am not sure why it's happening and why it is taking such long duration. I am not sending any messages or receiving any. The ping interval is 360 secs to which my client responds with an error, which is acceptable form of response to remain connected to the server. Anyone got the same issue ?
Openfire server: 3.8.1
iOS version: 6.1.2
Did you try using the setting "Do Not disconnect clients that are idle" available in Server Settings> Client Connections in Openfire server?
The view is not getting painted in BB device when the following steps are done:
First time I run the app, it works fine.
Close the application (System.exit(0))
Re-open the appllication, the device hangs.
I use the following stuffs in my app:
http connection
Storage
NOTE: The http request is sent and the response is also received. But the device hangs and view is not getting painted.
Kindly help me in this regard, please.
I suggest you switch to Codename One since Oracle ended support for blackberries.