I’m running a test sandbox locally. Anyone know an easy way to make my sandbox RPC service add a Access-Control-Allow-Origin: * header so that I can avoid CORS errors while testing locally?

rpc.tzbeta.net seems to add the header, so I can access it from my web app just fine, but it isn’t currently running the latest proposal code, so I can’t use it for testing.

One option for testing would be a proxy, but if there is a way to tell the RPC service to do it for me, that would be ideal.

1 Answer 1


You need to start the node with these options: --cors-header='content-type' --cors-origin='*'.

Once you’ve started the node with these options the response headers should allow a JavaScript application to make RPC calls to a Tezos node.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.