Fail to access the hosted site

Hi there I am facing an issue with the sites. My site is properly hosted on Appwrite but the issue is that when accessing the site from this URL https://instantmocks.appwrite.network/ it just gives the error shown in the attached image. However, if I access the another version of this hosted site URL which is this https://6903079ef3333df930d1.appwrite.network/ in this case I could access my project from my Mac, but from my phone, it shows the same error as in the image.

This project is for the hackathon that’s why I’m a bit concerned about this issue

If possible could you provide GitHub repo for the project?

Here you go

https://github.com/GurneeshBudhiraja/InstantMocks

<@287294735054274560> sorry looks like this got buried under the other support. This is for the hackathon submission and would appreciate to know how this could be fixed

Access to font at 'https://assets.appwrite.io/fonts/inter/Inter-Regular.woff2' from origin 'https://instantmocks.appwrite.network' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Eh, I guess that error shows up on your https://6903079ef3333df930d1.appwrite.network/ also

You know what that error appears even if I just clone the Appwrite next.js template. The system is trhowing cors error somehow

yeah and it somehow working when that deployement is not even active

are you having the same issues with the appwrite sites <@243998465451884544>

Instead of clonning Appwrite template, could you create a new fresh temporary sites and connect with GitHub and setup your deployment. See if still issue exist

Do you want me to connect this new template with my hackathon repo or standalone new git repo

I would suggest first create a new starter next js project locally the push to new GitHub repo, connect to sites.

If everything works fine, this make sure next js 16 is running fine. Now copy hackathon project code and update your newly created repo and push to GitHub, and then see. It will tell if your code has problem or not

I am not running the 16 version. I am still using the 15 but would try your approach

just did that setup a new next.js project locally, pushed and deployed to sites and still shows this error

Looks like all this time it was just an issue with the location. I just created a new project in Franfurt region and it worked perfectly

Maybe, as Frankfurt was from the beginning of Appwrite and is much stable. You probably found the solution, try moving everything to that region, that might solve the issue 👍 Looks like you already did