binance-trading-bot-new-coins
binance-trading-bot-new-coins copied to clipboard
Published
20 hours ago •
CyberPunkMetalHead
CyberPunkMetalHead
several error logs of the last few days
hey, just FYI:
config.yml:
RUN_EVERY: 0.3 (I understood this doesn't matter anymore?)
TEST: True
log #1:
working...
HTTPSConnectionPool(host='api.binance.com', port=443): Max retries exceeded with url: /api/v3/ticker/price (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x000001A023CD9C10>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))
HTTPSConnectionPool(host='api.binance.com', port=443): Max retries exceeded with url: /api/v3/ticker/price (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x000001A023CD9D90>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))
HTTPSConnectionPool(host='api.binance.com', port=443): Max retries exceeded with url: /api/v3/ticker/price (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x000001A023CD9C10>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))
HTTPSConnectionPool(host='api.binance.com', port=443): Max retries exceeded with url: /api/v3/ticker/price (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x000001A023CD9D90>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))
...
log #2:
working...
HTTPSConnectionPool(host='api.binance.com', port=443): Read timed out. (read timeout=10)
HTTPSConnectionPool(host='api.binance.com', port=443): Max retries exceeded with url: /api/v3/ticker/price (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x000001E9D7DC9520>, 'Connection to api.binance.com timed out. (connect timeout=10)'))
HTTPSConnectionPool(host='api.binance.com', port=443): Max retries exceeded with url: /api/v3/ticker/price (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x000001E9D7DC68B0>, 'Connection to api.binance.com timed out. (connect timeout=10)'))
...
log #3:
working...
HTTPSConnectionPool(host='api.binance.com', port=443): Read timed out. (read timeout=10)
APIError(code=0): Invalid JSON error message from Binance: <html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
HTTPSConnectionPool(host='api.binance.com', port=443): Read timed out. (read timeout=10)
HTTPSConnectionPool(host='api.binance.com', port=443): Read timed out. (read timeout=10)
...
I had the same error for response #1 https://github.com/CyberPunkMetalHead/binance-trading-bot-new-coins/issues/31
RUN_EVERY is obsolete now yes. I've come across the same issues, as above. They might be due to a brief drop in the Internet connection but can't verify that. I was expecting the try and except block to resolve this.
