-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bybit does not recover after computer's sleep mode #228
Comments
Seems that Bybit's private subscription is down as the new order clOrdID=1264836825.BTCUSDT.linear did not appear in the Orders' widget. After reboot (F3) the order showed up.2024-06-05 11:44:55,277 - functions - INFO - Emboldening SQLite |
2024-05-16 05:08:06,506 - root - INFO - Emboldening SQLite
2024-05-16 05:08:15,350 - api.bybit.pybit._websocket_stream - ERROR - WebSocket Unified V5 (wss://stream-testnet.bybit.com/v5/public/linear) encountered error: Connection to remote host was lost..
2024-05-16 05:08:15,350 - api.bybit.pybit._websocket_stream - INFO - WebSocket Unified V5 attempting connection...
2024-05-16 05:08:15,405 - api.bybit.pybit._websocket_stream - ERROR - WebSocket Unified V5 (Auth) (wss://stream-testnet.bybit.com/v5/private) encountered error: Connection to remote host was lost..
2024-05-16 05:08:15,405 - api.bybit.pybit._websocket_stream - INFO - WebSocket Unified V5 (Auth) attempting connection...
2024-05-16 05:08:16,108 - websocket - INFO - Websocket connected
2024-05-16 05:08:16,110 - api.bybit.pybit._websocket_stream - INFO - WebSocket Unified V5 connected
2024-05-16 05:08:16,116 - websocket - ERROR - Connection to remote host was lost. - goodbye
2024-05-16 05:08:16,174 - websocket - INFO - Websocket connected
2024-05-16 05:08:16,174 - api.bybit.pybit._websocket_stream - INFO - WebSocket Unified V5 (Auth) connected
2024-05-16 05:08:16,175 - websocket - ERROR - Connection to remote host was lost. - goodbye
2024-05-16 05:08:16,388 - websocket - ERROR - error from callback <function _WebSocketManager._connect.. at 0x70e9cc2360e0>: Authorization for Unified V5 (Auth) failed. Please check your API keys and resync your system time. Raw error: {'success': False, 'ret_msg': 'Params Error', 'op': 'auth', 'conn_id': 'cno3fi5daugt7mgdqvtg-242lv'}
2024-05-16 05:08:16,601 - websocket - ERROR - error from callback <function _WebSocketManager._connect.. at 0x70e9cc236290>: Authorization for Unified V5 (Auth) failed. Please check your API keys and resync your system time. Raw error: {'success': False, 'ret_msg': 'Params Error', 'op': 'auth', 'conn_id': 'cno3fi5daugt7mgdqvtg-242lv'}
2024-05-16 05:08:16,602 - websocket - INFO - tearing down on exception Authorization for Unified V5 (Auth) failed. Please check your API keys and resync your system time. Raw error: {'success': False, 'ret_msg': 'Params Error', 'op': 'auth', 'conn_id': 'cno3fi5daugt7mgdqvtg-242lv'}
2024-05-16 05:08:16,673 - api.bitmex.ws - INFO - (https) sending GET to announcement/urgent: ""
2024-05-16 05:08:26,867 - api.bitmex.ws - INFO - (https) sending GET to announcement/urgent: ""
2024-05-16 05:08:32,874 - api.bitmex.ws - ERROR - Error: Connection to remote host was lost.
2024-05-16 05:08:32,874 - websocket - ERROR - Connection to remote host was lost. - goodbye
2024-05-16 05:08:32,875 - api.bitmex.ws - INFO - Bitmex - Websocket closed
2024-05-16 05:08:32,968 - api.bitmex.ws - INFO - (https) sending GET to instrument/active: ""
2024-05-16 05:08:33,141 - api.bitmex.ws - INFO - Connecting to websocket
2024-05-16 05:08:33,142 - api.bitmex.ws - INFO - Authenticating with API key.
2024-05-16 05:08:33,142 - api.bitmex.ws - INFO - (https) sending GET to user: ""
2024-05-16 05:08:33,144 - api.bitmex.ws - INFO - (https) sending GET to position: ""
2024-05-16 05:08:33,484 - websocket - INFO - Websocket connected
2024-05-16 05:08:34,145 - api.bitmex.ws - INFO - Connected to websocket.
2024-05-16 05:08:34,346 - api.bitmex.ws - INFO - Data received. Continuing.
2024-05-16 05:08:34,364 - api.bitmex.ws - INFO - (https) sending GET to execution/tradeHistory?count=500&reverse=false&startTime=2024-05-15 17:35:47: ""
The text was updated successfully, but these errors were encountered: