I am getting the error "System.Net.WebException: The operation has timed out" frequently from around 25 sep. It was working fine before, i havn't change any code, internet is working.
i am sending request for LTP (Kite.GetLTP) and quote (Kite.GetQuote).
@Nivas Thank you for the suggestion, I tried steps suggested by @tonystark
1. Try opening https://api.kite.trade/ in browser. If this loads then it is not internet issue. 2. Try `ping api.kite.trade` in command prompt. If this works then your DNS is fine. 3. Try a new sample project and see if that is able to access Kite data. If this works then your firewall has blocked your main program.
1. Working for me. 2. I am getting request time out.
This issue doesn’t seem to be related to the Kite Connect itself. It’s likely due to something in the local setup, so a bit of trial and error will help narrow it down.
You could try temporarily disabling any antivirus or security software (other than Windows Firewall), as these sometimes interfere with API traffic.
It may also help to test on a different network (for example, a mobile hotspot or home Wi-Fi) to see if the issue is specific to your current ISP or office connection.
If possible, testing from another machine on the same network would also confirm whether the issue is tied to the device or the network.
My home and work place, both has same ISP and at both place i am facing same issue of request timed out. I tried using mobile hotspot and guess what, it worked. ISP is the culprit here.
1. Try opening https://api.kite.trade/ in browser. If this loads then it is not internet issue.
2. Try `ping api.kite.trade` in command prompt. If this works then your DNS is fine.
3. Try a new sample project and see if that is able to access Kite data. If this works then your firewall has blocked your main program.
1. Working for me.
2. I am getting request time out.
3. I allowed my app through firewall.
What should i do to fix step 2.
My home and work place, both has same ISP and at both place i am facing same issue of request timed out.
I tried using mobile hotspot and guess what, it worked. ISP is the culprit here.
Once again thank you for the help.