CORS Error on Speedynode RPC request

Technical Issue Reporting
#1

Since yesterday I get CORS errors on some JSON RPC requests to my speedy-nodes endpoints:

Access to fetch at ‘https://speedy-nodes-nyc.moralis.io/09cb[..myEndpoint...]beae/polygon/mumbai’ from origin ‘https://rex.cryptox.page’ has been blocked by CORS policy: Response to preflight request doesn’t pass access control check: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled.

Everything worked fine until yesterday.

#2

can you send me your email in DM? we can try to reset the token for your speedy node

1 Like
#4

Hey better to delete this asap :raised_hands: your email is exposed publicly

#5

I looks like you are making requests to speedy nodes, do you get that error every time or only from time to time?

#6

Only from time to time (but very often) and in a large part when listening to events.

#7

It may be better to use a Moralis server to listen for events and sync them directly in the server db

#8

I thought that I don’t need a server because I already have an own backend. Your documentation about speedy-nodes also says: “Need a fast and reliable full node, but already have your own backend? Then Moralis Speedy Nodes are for you! Get direct WebSocket and JSON RPC access to Moralis full nodes and archive full nodes”

#9

We are planning on retiring the speedy nodes in the future. You could try to also use web3api if possible.

#10

Hello, I also encountered the problem of consent today

#11

Today the nodes for the free plan should not work

#12

What’s the reason? Can it work normally in the future

#13

They will not:

#14

It means that the fast node no longer provides services, does it

#15

How can I get such node services

#16

you can try to use chainstack: https://moralis.io/largenodes

#17

Thanks, my DAPP can run again

1 Like