504's and and cloudflare blocking requests

Technical Issue Reporting
#1

Hello.

I currently use the Moralis web3 API as well as speedy nodes to get information about NFTs on the ETH chain. Since launching into production, my app has seen hundreds of errors per day pertaining to the web3 api calls & speedy nodes.

Web3 API ā€“ Im often receiving ā€œ504 Gateway Timeoutā€ errors when hitting these endpoints:

GET /{address}/nft/transfers

GET /{address}

These endpoints are VERY slow for me. Sometimes up to 5000ms/call

Im also experiencing issues using speedy nodes. Im getting this as a response:

Too many requests for speedy-nodes-nyc.moralis.io. Try again later.

Would love some help on this if possible. Thanks

#2

We will investigate the part with Too many requests for speedy-nodes-nyc.moralis.io

#3

did you see any improvements for the cloudflare limiting problem? it still gives those errors now?

#4

Yes, Iā€™m still getting errors. They are intermittent tho.

#5

you had errors in the last hour?

#6

Getting these 504ā€™s again today. Iā€™m dealing with this in a production environment (happening on dev as well) and itā€™s causing some major issues. Anyone have any solution to this? Itā€™s starting to becoming frustrating dealing with this constantly.

#7

Now it looks like a problem on our side.

#8

Hey, we are seeing these problems as well. We see ā€œ504 Gateway Timeoutā€ under heavy load when calling GetNFTs. Any pointers?

#9

can you share more information, as an example of a request that gets that error?
you can share it in DM if you donā€™t want to post it publicly.

#10

Apologies for waking a ā€œsleepingā€ thread, but Iā€™m having this same issue randomly as well.

Been testing an app in beta. It runs fine for hours at a time (even overnight), but will randomly start getting blocked by CloudFlare. No amount of rebooting or waiting works. I end up having to acquire a different IP (via VPN or otherwise), and everything starts working again.

While I recognize the need to protect endpoints, an issue like this is absolutely not tolerable on a paid plan.

#11

In case that you are using walletconnect then there is a rate limit per IP for the public RPC url that is used. If you try it too many times then you will get that rate limit error.

#12

Iā€™m making use of direct Mongo connections and V1 Web3API calls. The application is a NodeJS app. I generate a ā€œsingletonā€ Moralis instance and use it throughout the entire application. It does generate a decent number of calls, and while I might expect one or two calls to get bounced, I definitely donā€™t expect CloudFlare to get involved. šŸ« 

#13

For what url in particular you get errors?

#14

Most recently Web3API.token.getTokenPrice. But it seems fairly random. We make use of a substantial portion of the Web3API calls.

But the bigger issue is that the IP gets blocked. Not sure if itā€™s permanent, but long enough that we must change it, and of course manually change the IP for Mongo access.

#15

Can you check the http headers for when you get those errors? How many requests do you make?

You shouldnā€™t get easily blocked for that request unless you make thousands per second

#16

Iā€™ve already cleared the most recent series of errors and logs. Letting it run again overnight and Iā€™ll check it in the morning.

Not making thousands per second, but some bursts between 50-200 per second. Weā€™re making various calls regarding Swap ā€œactorsā€. Token prices, holder information, etc. ā€“ for multiple token swaps at a time.

Iā€™m offloading as much as possible to direct contract calls, but we canā€™t always rely on a contract to be verified or the source to be accessible, so we rely on Moralis in those instances.

Regardless, it would be nice to know what the explicit limitations were in all circumstances so as to code around it (or drop the feature(s)).

#17

You donā€™t get rate limited for 200 requests per second?

#18

FYI, this is my second time posting this ā€“ from the same test IP. The first reply apparently got blocked due to, well, CF/Moralis blocking traffic. Swapped my IP and now this works.

Yes, I will occasionally get transactions rejected during bursts, but CF doesnā€™t usually step in and completely block my IP in those situations. But, for some reason, at some point, CF/Moralis decides it doesnā€™t want to hear from us anymore and simply blocks the IP.

Here is the most recent error output. Not sure if it pertains to the issue, but it happened hours ago while I was asleep:

2022-08-29T06:44:20.375Z - Error: {}
    at fetch (/moralis-server/lib/cloud-code/plugins/helpers/apiUtils.js:218:26)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
2022-08-29T06:44:20.368Z - Failed running cloud function getTokenBalances for user undefined with:
  Input: {"chain":"bsc","address":"0xD4825ad5B1A863587e7116f3DE1387C1238e4319","to_block":"20858573"}
  Error: {"message":"{}","code":141}
2022-08-29T04:57:32.391Z - Error: Invalid function: "getPluginSpecs"
    at handleCloudFunction (/moralis-server/lib/Routers/FunctionsRouter.js:201:13)
    at /moralis-server/lib/PromiseRouter.js:85:20
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

For what itā€™s worth, Get all logs in your terminal: Learn about Moralis CLI is a dead link and needs to be fixed.

#19

you are using a Moralis Server to make web3api requests from a backend?
asking because that looks like server log

in that case what IP was blocked, your local IP, server IP?

#20

Itā€™s a node application. Yes, just using the existing Web3API collection (rather than axios/fetch with endpoints on the backend). Is the EVM object available in V1? What do you recommend?

There are a few devices (hardware and docker) behind the same VPNā€™ed firewall so theyā€™re all sharing the same external IP. But only one VM is interacting with Moralis. Itā€™s blocking that shared VPN IP