[SOLVED] Blocked by CORS policy

Moralis General
#1

New here and Im just setting up my first cloud function to perform a simple save to the database but I seem to be getting the follow error

Access to XMLHttpRequest at ‘https://owexnxuzf2ev.usemoralis.com:2053/server/functions/createAvatar’ from origin ‘http://localhost:3000’ 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.

	const logger = Moralis.Cloud.getLogger();
	logger.info("Request coming 6: " + JSON.stringify(request));

	// logger.info("User : " + JSON.stringify(user));

	request.user.set("username", "new_usernname");
	await user.save();

	return user;

As soon as I enable the save function I get this error

The server is brand new ganache and I have set up hardhat for my localchain

#2

You could get that error when server is not working, when it gets a timeout or when you have something that blocks that connection like a vpn.

#3

The server is running fine and I can even make calls via the js console

#4

Can you look in browser network tab to see what it says there?

#5

image
image1056×482 57 KB

#6

That is browser console. Browser network is somewhere near console, it is something different.

#7

image
image1208×483 24.6 KB

#8

yes, this is the network tab

for me it worked if I paste directly in browser https://owexnxuzf2ev.usemoralis.com:2053/server/functions/createAvatar

#9

Ok any idea what may be causing the cors policy error?

#10

try to see if it works in the browser directly

#11

Ok I just got one that passed and one that failed upon a single submission

image
image1209×282 17.8 KB

Weird though

#12

Yeah it works in the browser

#13

ok, then try with http://127.0.0.1:3000’ instead of http://localhost:3000’

#14

2022-04-29T19:24:24.096Z - ReferenceError: user is not defined

Moralis info logs
Error: {“message”:“user is not defined”,“code”:141}

#15

image
image1234×706 38.9 KB

1 single submission and it seems to be firing 2 times, perhaps this is the issue

1 fail 1 passs

#16

that is expected one is OPTIONS for Request Method

click on the one where it says bad request

2 Likes
#17

image
image1278×739 40 KB

Seems there are 2 calls made one is a “post” and one is an “options”

#18

{“code”:142,“error”:“Validation failed. Please login to continue.”}

Getting validation failed probably because of the “requireUser: true”

#19

So the cors issues seems to have stop, not im getting set errors and user not defined

#20

This fixed the CORS issue, thank you!

1 Like