Even we have got pro-plan (we have paid) but our node seems no work

Technical Issue Reporting
#13

image
image1920×1080 346 KB

image
image1920×1080 380 KB

we use that export const ProviderAddress: string = “wss://speedy-nodes-nyc.moralis.io/fccc55fe6559f339efb29e25/polygon/mumbai/ws”;

is it suitable way ? because we are getting unkown account error, so we cant popup metamask for users? how can we fix that?. can you share with sendtransaction example which uses speedy nodes provider in a web3…

#14

You can use Moralis.executeFunciron directly

You may need to init web3 first, like using Moralis.enableWeb3, in latest version of Moralis sdk you may get an ethers instance.

And users will need to have polygon network added to MetaMask. And also to have matic in their account in order to be able to make a transaction.

#15

hi we get cors error, can you help us… we are in bad position… all the codes (smart conrtact, whitelist and backend) is ok. but we are stuck in that position. we can use infura with web3. but we cant use moralis. we need your support please…

#16

image
image1920×1080 267 KB

you have written this… what will we do right now. all process is stop for moralis decision???

#17

what is the problem that you have now?

any request doesn’t work to speedy node, or only some requests don’t work

in what situation you get CORS errors? is it because of timeout, networks blocking, error from speedy node?

#18

image
image753×479 27.8 KB

we are getting this

#19

that message looks like a rate limit error, but it doesn’t look like an error from moralis speedy nodes

#20

image
image1920×1080 260 KB

but why we getting this? we use speedy nodes provider and poylgon public url. how can we avoid this?

#21

can you please help us???

#22

it looks like you have public polygon url there for metamask config, that one may be the one that gives that rate limit error, but I don’t know how is that you make 40 requests in a second

#23

what is the rate limits in a one second im speedy nodes?

#24

it depends on what type of call you make, and on the plan

https://docs.moralis.io/misc/rate-limit#speedy-node-requests

for a free plan the limit is of 50 compute units per second

#25

we are using pro plan what is rate limit?

#26

it could be of 88 compute units per second for a pro plan

#27

we are not using ether.js.

  1. we used moralis.enable.web3(provider:‘metamask’)
  2. web3.eth.sendtransaction
    but we get error: unknown accout (but if we use setprovide we get cors error)

what is the suitable code block? can you route us an code block for sendtransaction with speedy nodes provider…

#28

I don’t know how you can do that, it will be used the RPC url that is present in metamask

I still don’t know how is that you are making too many requests, isn’t that from a single user?

#30

we have to solve this issue yes you are right. but we are not sure from following…
if we didnt add speedy node rpc to metamask, even we dont sure stream from web3 provider with speedy nodes. can you guarentee that? and https://docs.moralis.io/misc/rate-limit#speedy-node-requests
sendraw transaction is 35 request… in a one second 3 guys can exceed 88 number… what is you opinion?

#31

I think that you shouldn’t use the speedy node url as a way to send transactions for your users. The users should add a public RPC url in their metamask configuration

#32

we are aware but why is the exceed limit is 40, because you said 88. Although we use speedy node provider and use polygon mumbai in metamask. because you said that we haver 88 request in a second… why the numbers are different?

#33

for me it looks like that error with 40 requests is not from moralis speedy nodes and it is from another public RPC url