Deep Index Errors: 520, 502

Technical Issue Reporting
#1

Hi,

I’ve been using the deep index api with varying levels of success without changes to my request… sometimes it works, other times it doesn’t. I’m not sure what is causing this. I have a Pro plan.

Trying this request with Insomnia results in a 520, then a 502.

https://deep-index.moralis.io/api/v2/0x8a6D4C8735371EBAF8874fBd518b56Edd66024eB/logs?chain=eth&limit=500&from_date=2022-04-01T05%3A00%3A00.000Z&to_date=2022-04-02T16%3A13%3A22.956Z

I tried many other configurations, same result.

Screen_Shot_2022-04-03_at_4.17.06_PM
Screen_Shot_2022-04-03_at_4.17.06_PM1080×390 41.6 KB

Sometimes, I receive an unknown error, and in the raw response of that error, I see that data was partially streamed before the request died and failed as a whole. I dont believe its a timeout issue since my timeout setting is at 15mins and these requests take less than 10 seconds to fail.

REST API Errors 520, solved with a proxy
#2

@cryptokid following up here from our conversation on discord

#3

I tried a new set of credentials from a different account and the same requests that failed, worked once. Then it started giving me 520 statuses as well…

#4

I’m testing now to see if I can reproduce that error

#5

I tried this request 3-4 times in web3api interface (https://admin.moralis.io/web3Api)
https://deep-index.moralis.io/api/v2/0x8a6D4C8735371EBAF8874fBd518b56Edd66024eB/logs?chain=eth&from_date=2022-04-01T05%3A00%3A00&to_date=2022-04-02T16%3A13%3A22

and I didn’t get an error now

#6

Could it be that rate limiting is causing this to happen? Maybe i’m getting banned by cloudflare. My service sends a lot of requests, but with outgoing throttling applied. So for my account, it rarely gets more than 4 rate limit exceeded responses for payloads of over 200 requests. And when that does happen, it applies a cooldown before re-trying.

None of it makes sense because it works Sometimes. But recently, all of my requests don’t give a response. The request gets aborted.

I believe my issue is directly related to this one REST API Errors

#7

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

#8

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
#9

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.
#10

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

#11

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.

#12

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.

#13

I don’t think that the api key is the problem in this case

#14

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

#15

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?

#16

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?

#17

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

#18

I believe I’m experiencing this. I haven’t been able to make a call since this thread was posted.

#19

what error do you get?

#20

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