
When I added a platform to my project I specifed localhost
as the hostname. But when making requests I get this error:
Access to XMLHttpRequest at 'https://cloud.appwrite.io/v1/account' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Localhost is allowed by default. You're probably getting that error for some other reason...like incorrect project id. Or you don't have access to whatever API you're hitting.

Share the network logs if you still need help

I double checked and re-copied the correct IDs into my env file. In terms of services, I have everything enabled except for GraphQL. When I looked at the network tab this is really all I saw:
Request URL: https://cloud.appwrite.io/v1/account
Request Method: POST
Status Code: 404
Referrer Policy: strict-origin-when-cross-origin
On my frontend I'm just calling:
const userAccount = await account.create(
ID.unique(),
email,
password,
`${firstname} ${lastname}`
);
Also, just wondering, on my self-hosted instance of appwrite, what should I do to also allow localhost just like you say localhost is allowed by default on the cloud solution?

Ah, I figured out the issue - my env was named something like APPWRITE_PROJECT_ID
which was fine because I initially was doing my appwrite calls from the backend but since I am moving the calls over to the frontend, I needed to use NEXT_PUBLIC_APPWRITE_PROJECT_ID
.

[SOLVED] How to allow appwrite to accept requests from localhost?
Recommended threads
- my database attribute stuck in processin...
when i created attributes in collection 3 of those attributes become "processing", and they are not updating, the worst thing is that i cant even delete them s...
- Error 1.7.4 console team no found
In console when i go to auth, select user, select a membership the url not work. Only work searching the team. It is by the region. project-default- and i get ...
- Is Quick Start for function creation wor...
I am trying to create a Node.js function using the Quick Start feature. It fails and tells me that it could not locate the package.json file. Isn't Quick Start ...
