ERR_CONNECTION_TIMED_OUT - angular4-httpclient

enter image description herei have call Post/Get api when running app they show me error ERR_CONNECTION_TIMED_OUT in angular4

Either your internet connection is interrupting (most of the time faced by me when using mobile data tethering) or the server you are connecting is busy so that your request is in a queue or rejected at the network level of the server.

Related

The error that can't send and receive event in Kaa cluster

I deployed 3 Kaa clusters follow the kaa Cluster setup guide document.
The databases are MongoDB and MariaDB. When I run C Client(I make a code change that every client can login in three kaa servers in random) firstly, it can login in kaa server and send or receive event.
But after I stop the Client and start it secondly, it can not send or receive event.
Then I try to do it again and again. But almost it is bad. I will upload the server log and the Client log .
The error maybe caused by kaa cluster.
I generated a Java and Android Client SDK.The problem would also take place while I run Java and Android Client .

Problems with configuration of Bluemix server

I'm trying to increase timeouts in Bluemix. I've set all the timeout settings to 5 min. But after 2 min of a request I got an error:
500 Error: Failed to establish a backside connection
How do I solve this problem?
"This particular message probably comes from the L1 load balancer in Bluemix when it fails to get a timely response from the application it tries to route to. One of the possible cause here is because your application does not send any response back before the load balancer times out, which is 2 minutes if my memory serves me well."
https://developer.ibm.com/answers/questions/25439/bluemix-500-error-failed-to-establish-a-backside-connection-on-web-service-call.html
I would open up a support ticket if you need any additional help.

NSURLRequest Timing out without making connection to server

I have an application written in swift that communicated with my server using PHP. Throughout my testing the app has worked perfectly until I began testing on multiple devices simultaneously. When i try to load both devices at the same time it will sporadically (not 100%) create this timeout:
Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=
{NSUnderlyingError=0x127ea9fb0 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, NSErrorFailingURLStringKey=https://myhttpsdomain/my_page.php, NSErrorFailingURLKey=https://myhttpsdomain/my_page.php, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-2102, NSLocalizedDescription=The request timed out.}
Error with domain:https://myhttpsdomain/my_page.php
It creates this timer without ever making the connection to the server. Once the issue has been triggered all web requests from that device will create the error for a few minutes.
I am using a basic let task = session.dataTaskWithRequest to send post requests to my server.
To decide whether the server connection was made or not the first line in my php file is error_log("Page has been called"); And this line isn't even printing.
This is probably one of the following:
a DNS problem
a routing problem/network problem
a server configuration issue
First, check the server logs and see if the request suddenly appears in the logs whenever the client gives up on the connection. If so, you'll need a packet trace to know for sure, but chances are, your PHP script is wedging forever before it sends headers or the server is otherwise misconfigured in some way.
If not, then sniff the network and see if it is even sending out a request. And make sure that both devices can ping each other.

iOS App in background longer than 10 minutes and communicating with Web Service

I have a app using Location Updates and it can run in the background longer than 10 minutes. This app can communicate with Web Service A both in the background less than and greater than 10 minutes. The problem I'm facing is that it cannot communicate with Web Service B when my app is in the background greater than 10 minutes--I get a 500: internal server error. I can communicate with Web Service B when my app is in the background less than 10 minutes.
Note: I can communicate with Web Service A & B in the foreground as well. Also note that I use the same code/libraries to communicate with Web Service A & B whether they are in the foreground or background.
Has anyone experienced this same problem? Can you please ideas for debugging? Once my Server admin is available I will ask him to analyze the request being received and also check if the socket is being closed prematurely.
I get a 500: internal server error
This hasn't really got anything to do with iOS background services. Your application is running and communicating with the server.
To debug this issue, hook your app up to a proxy like Charles, and look for the difference between requests that succeed and requests that fail.
I suspect your session might be timing out on the server. Look at your server configuration to see if your timeout parameter matches up with what you are observing.

Issues with httpd over 3G

I am experiencing a strange issue with connecting to my web server from my Iphone4.
I have an app that connects to my web serer and downloads a chunk of JSON. This works fine when i'm connected via WIFI, but fails through 3G. I don't think it's my app, as Safari also fails to retrieve any page on my web server when using 3G.
My web server has a fixed i.p and is running apache/Centos pretty fresh out of the box, I have not messed with the firewall or iptables settings.
The error obtained from the iphone is "The network connection was lost"
It feels like a firewall issue, but i have not explicitly denied any ips. Is there some aspect of a 3g connection that gets denied by default on Linux?
I realise this is all vague at this time, but does anyone have any wisdom to offer?
Many thanks in advance.
Here is a topic related to iphone connection loss through 3G cellular data whereas WiFi works fine, also giving the error "The network connection was lost"
Couple suggestions:
Ensure that your web server is
responding in a timely fashion. If
it is taking a little too much time,
the 3g connection might give up.
Check your web server logs and see if the connection is reaching
your web server at all, and if any
errors are being recorded. If so,
investigate.
There isn't anything special about a 3g connection wrt you web server. Only difference would be that it is less reliable or slower.
How are you actually trying to connect to your web server? When its over wifi you are local on your network and the name of the server will probably work. But when its over 3g its on the interwebs and will probably not respond to the name of the server.