invalid request, please check your server timestamp or recv_window param
See original GitHub issueAfter starting my robot I’m always getting this error after a while:
arg1: {ret_code: 10002, ret_msg: 'invalid request, please check your server timestamp or recv_window param', result: null, ext_code: '', ext_info: '', …}
ext_code: ''
ext_info: ''
rate_limit: 0
rate_limit_reset_ms: 0
rate_limit_status: 0
result: null
ret_code: 10002
ret_msg: 'invalid request, please check your server timestamp or recv_window param'
time_now: '1669045126.582107'
It solves by itself by retrying multiple times. I suppose the time is sometime unsync ?
Issue Analytics
- State:
- Created 10 months ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
REST API Error: "invalid request,please check your server ...
invalid request,please check your server timestamp or recv_window param is the error message. I've sync'd my server time. It doesn't happen ...
Read more >Timestamp for this request is outside of the recvWindow
I know that it has something to do with the time synchronization between my computer and the server. I don't get this error...
Read more >Bybit Connection Issue - Bookmap forum
Please edit credentials and try again. Reason: Unable to login. invalid request, please check your timestamp and recv_window param.
Read more >API Frequently Asked Questions
How come I keep getting this error “Timestamp for this request is outside of the recvWindow.” ?This usually means that your system time...
Read more >FAQ — python-binance 0.2.0 documentation
Q: Why do I get “Timestamp for this request is not valid”. A: This occurs in 2 different cases. The timestamp sent is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thank you for your fast answer. I’m using:
"bybit-api": "^3.0.2",I just switched on the latest version"bybit-api": "^3.3.3",.I added a
datetimeon everyconsole.logandconsole.errorto see if the time go off more than 5sec. + I will log the latency spot as well.I’m going to let you know when I will have more data or if this is reproduced with the latest version.
Nope didn’t pass any options :
I just got the issue again on my main project where I refresh the
getWalletBalanceevery 5sec. I’m logging all requests to the API that are taking more than 1s.Here is the output of the
latencyscript running in parallel (refresh every 500ms):