1. Home
  2. Categories
  3. Bugs
  4. Internal Server Error

Internal Server Error

Bugs
Log in to reply
  • C

    @admin
    facing server errors again today. these days, your servers are going down daily.

    ***** STORE NOTIF: While feteching order_book
***** STORE NOTIF: 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:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 500 \xe2\x80\x93 Internal Server Error</h1></body></html>'
    0 A 1 Reply
  • R

    @admin @c_harish

    we put our money at stack everyday.. If there is a new error one can understand.. but error occurring repeatedly be it intermittent or not is a issue for us.. @bhaveshjain kindly resolve such issues..

    0
  • L

    Hi @admin ,

    Internet connectivity is absolutely fine and latency is also very good.

    algoz@ubuntu-blr:~/AlgoTrading$ ping apiconnect.angelbroking.com
PING ec2-35-154-160-119.ap-south-1.compute.amazonaws.com (35.154.160.119) 56(84) bytes of data.
64 bytes from ec2-35-154-160-119.ap-south-1.compute.amazonaws.com (35.154.160.119): icmp_seq=1 ttl=51 time=16.5 ms
64 bytes from ec2-35-154-160-119.ap-south-1.compute.amazonaws.com (35.154.160.119): icmp_seq=2 ttl=51 time=16.5 ms
64 bytes from ec2-35-154-160-119.ap-south-1.compute.amazonaws.com (35.154.160.119): icmp_seq=3 ttl=51 time=16.5 ms
--- ec2-35-154-160-119.ap-south-1.compute.amazonaws.com ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6009ms
rtt min/avg/max/mdev = 16.450/16.461/16.494/0.015 ms

    And I check the server n/w graphs also, when error occurred, the internet connectivity is good only.
    I run my scripts in a Digital ocean Server located in Bangalore.
    This error is especially coming in the first 5 minutes of market. 9.15am to 9.20am.(mostly).

    0
  • A

    Hi @lakshmi_73 we are testing it from our end we want you to check you internet connectivity and its speed.

    0
  • L

    @admin Again similar error

    socket.timeout: _ssl.c:1114: The handshake operation timed out
rllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='apiconnect.angelbroking.com', port=443): Read timed out. (read timeout=7)

    Not able to fetch price, order details or place any orders and after few minutes error is gone.

    Please audit these errors. Getting such errors each and everyday. And still we don't know why these errors.

    0 A 1 Reply
  • C

    @admin I believe you meant "intermittent error".

    so your dev/testing team have no idea what is causing this, despite this happening everyday?

    if you can confirm that this can't be debugged from your side, we will be glad to move our algo to someplace else.

    0
  • A

    HI @c_harish this was an intermediate issue.
    *intermittent

    0 C 1 Reply
  • C

    @admin what is the cause of this error and why is this happening every other day?

    0 A 1 Reply
  • A

    HI @c_harish This issue has been resolved.

    0 C R 2 Replies