Yes, it seems like it is same issue as in the other thread. Is shouldn’t be related to rate limit. There should be a specific error for rate limit
Hi all, seems im having similar problems. I had pipelines running that used moralis and worked before but as of today they are failing but occasionally they work. I found out that they are 502 errors and the majority of times i get ChunkedEncodingError: ("Connection broken: InvalidChunkLength(got length b’’, 0 bytes read) using python requests. Does anyone have a similar issue as well?
1 Like
I’m also having new issues. Using aiohttp in Python - until today has been working great to get owners of ERC-1155 on Polygon: ```
https://deep-index.moralis.io/api/v2/nft/0x3f07f64D5431D3f26fa322B730b5F350ae79C159/owners?chain=polygon&format=decimal
Perhaps of interest, the web3Api page allows that to work BUT it first hits Chrome with a "do you want to wait or continue" message.we don’t know yet in what conditions this happens, it looks like an intermittent error
I don’t know how to reproduce it yet
For me (linked topic REST API Errors) the error is as follow:
cURL error 18: transfer closed with outstanding read data remaining (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://deep-index.moralis.io/api/v2/0x8482a932536fad492dcdbcedeb60cb9421ac384b/logs?chain=bsc&offset=0&to_date=2022-03-06%2005:14:53
CURLE_PARTIAL_FILE (18)
A file transfer was shorter or larger than expected. This happens when the server first reports an expected transfer size, and then delivers data that does not match the previously given size.
If you DM me, I’ll send you my API key to test with. My pro account is currently for testing. I dont have any data in Moralis. I just use it for node access.
I don’t think that the api key is the problem in this case
Was there any change in your API response headers configuration recently? @cryptokid @ivan
Most of my jobs stopped working properly so it’s a big blocker for me .
Thanks for your time guys
I don’t know of any change in API response headers configuration
can you try to make the requests from a different location to see if there is a difference?
I tested it with another network and it worked properly so I’m pretty sure it’s on cloudflare side then. Same as @shrimplypibbles, I do a lot of calls and I suspect my IP to be banned from. When we do a lot of calls we should face rate limiting errors from Moralis but not be blocked by Cloudflare…
Is it possible to be whitelisted again?
if the IP would be banned, then you could not do any call in a specific time interval
anyway, send me the IP din DM
I believe I’m experiencing this. I haven’t been able to make a call since this thread was posted.
what error do you get?
For the logs endpoint, I get unknown error or request aborted.
For erc20 metadata, sometimes empty response. Ex: https://deep-index.moralis.io/api/v2/erc20/metadata?chain=eth&addresses=0x8a6D4C8735371EBAF8874fBd518b56Edd66024eB
this works for me now, I tried 10 times
I switched my IP to a VPN provided IP and it works again. I have not triggered any rate limits yet. I suspect if I do, this same issue will happen to my new IP. So I will test that out after I finish building, or if im able to obtain another IP.
1 Like
I increased my requests per second to 20, and now im facing the 502 errors again. This time, subsequent requests are met with a 504
and if you decrease it now it works well?
we did a change in API backend recently (~15-30 minutes ago), if you see something strange it could also be because of that change
correct, it works fine at 10 requests per second for small payloads.
Longer payloads now timeout with a 504 after a few minutes.
Its a bit disappointing though because the pro plan should be netting us about 60 requests per second if im not mistaken
you have a request example for this?