While feteching order_book
***** STORE NOTIF: HTTPSConnectionPool(host='apiconnect.angelbroking.com', port=443): Read timed out. (read timeout=7)
Couldn't parse the JSON response received from the server: b'<html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body bgcolor="white">\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>nginx/1.14.1</center>\r\n</body>\r\n</html>\r\n'
@admin getting too many timed out and gateway errors from today morning. fix it.
@pari said in Timeout errors happening:
Correct. This issue is not about exceeding the rate access limit of 10 per second. Even my program sleeps for 1 second after sending 10 requests. My script also polls only once a minute. Currently I'm only polling for 'ltp' for 4 scrips, which is well within the limit. This issue is clearly about 'http' timeouts happening at the server level and not due to the script.
It's now past 12:18, the issue seems to have stopped and the script is running as before. I wonder if it will occur again at 1:08.
true. it is not client specific when everyone faces it. i am appalled by @admin 's silence on this thread. not a single reply in this thread from @admin after almost 20 minutes of downtime in 3 hrs.
as usual, @admin will ask for if we are running locally/cloud, timestamp, error code and forget as if nothing happened.
Jan 03 10:25:18 instance-20251211-2333 python[196314]: 2026-01-03 10:25:18,424 - candle_collector - ERROR - Provider Connection Error: HTTPSConnectionPool(host='apiconnect.angelbroking.com', port=443): Max retries exceeded with url: /rest/auth/angelbroking/user/v1/loginByPassword (Caused by ConnectTimeoutError(<HTTPSConnection(host='apiconnect.angelbroking.com', port=443) at 0xf98f120ec6d0>, 'Connection to apiconnect.angelbroking.com timed out. (connect timeout=7)'))
Jan 03 10:25:18 instance-20251211-2333 python[196314]: 2026-01-03 10:25:18,424 - candle_collector - INFO - Retrying in 30 seconds...
Jan 03 10:25:48 instance-20251211-2333 python[196314]: [I 260103 10:25:48 smartConnect:121] in pool
Jan 03 10:25:55 instance-20251211-2333 python[196314]: [E 260103 10:25:55 smartConnect:218] Error occurred while making a POST request to https://apiconnect.angelbroking.com/rest/auth/angelbroking/user/v1/loginByPassword. Headers: {'Content-type': 'application/json', 'X-ClientLocalIP': '127.0.0.1', 'X-ClientPublicIP': '106.193.147.98', 'X-MACAddress': '17:07:dd:3f:e7:f4', 'Accept': 'application/json', 'X-PrivateKey': 'Cl6etsLX', 'X-UserType': 'USER', 'X-SourceID': 'WEB'}, Request: {'clientcode': 'A591645', 'password': '1998', 'totp': '765240'}, Response: HTTPSConnectionPool(host='apiconnect.angelbroking.com', port=443): Max retries exceeded with url: /rest/auth/angelbroking/user/v1/loginByPassword (Caused by ConnectTimeoutError(<HTTPSConnection(host='apiconnect.angelbroking.com', port=443) at 0xf98f11b2b450>, 'Connection to apiconnect.angelbroking.com timed out. (connect timeout=7)'))
Jan 03 10:25:55 instance-20251211-2333 python[196314]: 2026-01-03 10:25:55,434 - candle_collector - ERROR - Provider Connection Error: HTTPSConnectionPool(host='apiconnect.angelbroking.com', port=443): Max retries exceeded with url: /rest/auth/angelbroking/user/v1/loginByPassword (Caused by ConnectTimeoutError(<HTTPSConnection(host='apiconnect.angelbroking.com', port=443) at 0xf98f11b2b450>, 'Connection to apiconnect.angelbroking.com timed out. (connect timeout=7)'))
Jan 03 10:25:55 instance-20251211-2333 python[196314]: 2026-01-03 10:25:55,435 - candle_collector - INFO - Retrying in 30 seconds...
Jan 03 10:26:25 instance-20251211-2333 python[196314]: [I 260103 10:26:25 smartConnect:121] in pool
Jan 03 10:26:32 instance-20251211-2333 python[196314]: [E 260103 10:26:32 smartConnect:218] Error occurred while making a POST request to https://apiconnect.angelbroking.com/rest/auth/angelbroking/user/v1/loginByPassword. Headers: {'Content-type': 'application/json', 'X-ClientLocalIP': '127.0.0.1', 'X-ClientPublicIP': '106.193.147.98', 'X-MACAddress': '17:07:dd:3f:e7:f4', 'Accept': 'application/json', 'X-PrivateKey': 'Cl6etsLX', 'X-UserType': 'USER', 'X-SourceID': 'WEB'}, Request: {'clientcode': 'A591645', 'password': '1998', 'totp': '765240'}, Response: HTTPSConnectionPool(host='apiconnect.angelbroking.com', port=443): Max retries exceeded with url: /rest/auth/angelbroking/user/v1/loginByPassword (Caused by ConnectTimeoutError(<HTTPSConnection(host='apiconnect.angelbroking.com', port=443) at 0xf98f13bfef50>, 'Connection to apiconnect.angelbroking.com timed out. (connect timeout=7)'))
Jan 03 10:26:32 instance-20251211-2333 python[196314]: 2026-01-03 10:26:32,445 - candle_collector - ERROR - Provider Connection Error: HTTPSConnectionPool(host='apiconnect.angelbroking.com', port=443): Max retries exceeded with url: /rest/auth/angelbroking/user/v1/loginByPassword (Caused by ConnectTimeoutError(<HTTPSConnection(host='apiconnect.angelbroking.com', port=443) at 0xf98f13bfef50>, 'Connection to apiconnect.angelbroking.com timed out. (connect timeout=7)'))
Jan 03 10:26:32 instance-20251211-2333 python[196314]: 2026-01-03 10:2
@admin orderbook down.. getting HTTPSConnectionPool error. Fix it.
@StocksDeveloper
angel is a big joke now. their new and old web portals are also down. so no way to square off any positions.
@admin
welcome back, admin. we missed you here for past few months..
back to business. created new API. still tokens not generating due to following error as usual.
"Read timed out. (read timeout=%s)" % timeout_value
urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='apiconnect.angelbroking.com', port=443): Read timed out. (read timeout=7)
tried a dozen times to generate tokens with newly created API key and failed.
While feteching order_book
***** STORE NOTIF: HTTPSConnectionPool(host='apiconnect.angelbroking.com', port=443): Read timed out. (read timeout=7)
While feteching order_book
***** STORE NOTIF: Couldn't parse the JSON response received from the server: b'<html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body bgcolor="white">\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>nginx/1.14.1</center>\r\n</body>\r\n</html>\r\n'
@admin happening too often.. getting 100s of such errors every hour these days, @admin .
you have turned a deaf ear to our error reports. there are dozen other topics created since last 1-2 days by other users. But you don't even care to reply.
you are leaving us no choice but to move out.
While feteching order_book
***** STORE NOTIF: HTTPSConnectionPool(host='apiconnect.angelbroking.com', port=443): Read timed out. (read timeout=7)
Couldn't parse the JSON response received from the server: b'<html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body bgcolor="white">\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>nginx/1.14.1</center>\r\n</body>\r\n</html>\r\n'
@admin getting too many timed out and gateway errors from today morning. fix it.
@admin facing the internal server error as usual. look into it.
HARISH Couldn't parse the JSON response received from the server: b'<!doctype html><html lang="en"><head><title>HTTP Status 500 \xe2\x80\x93 Internal Server Error</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:
@pari said in Timeout errors happening:
Correct. This issue is not about exceeding the rate access limit of 10 per second. Even my program sleeps for 1 second after sending 10 requests. My script also polls only once a minute. Currently I'm only polling for 'ltp' for 4 scrips, which is well within the limit. This issue is clearly about 'http' timeouts happening at the server level and not due to the script.
It's now past 12:18, the issue seems to have stopped and the script is running as before. I wonder if it will occur again at 1:08.
true. it is not client specific when everyone faces it. i am appalled by @admin 's silence on this thread. not a single reply in this thread from @admin after almost 20 minutes of downtime in 3 hrs.
as usual, @admin will ask for if we are running locally/cloud, timestamp, error code and forget as if nothing happened.
@Mnagesh, we know this. and we don't cross any of the suggested rate limits as I said in last post.