CORS issue since v2

[marc-on-github]

Access to fetch at 'https://analytics.xx.com/api/send' from origin 'https://xx.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.

[mikecao]

Nothing has changed on the CORS end of things and we are running the same codebase in production. Is it possible you have something else sending different headers?

[mauricerenck]

I do have the same issue and was wondering because I didn't change anything. What I saw then, is that I get an error 503 which results in this CORS message (in firefox). Maybe have a look if that is happening with your setup, too. That cors message may be confusing.

In general umami keeps crashing as soon as a request is sent from a website.

error Command failed with signal "SIGKILL".
ERROR: "start-server" exited with 1.
error Command failed with exit code 1.

I run this on a koyeb instance. This keeps happening with new and old migrated mysql databases. Maybe have a look in your logs, to see if something similar is happening.

[jazerix]

I am experiencing the same in my instance. It worked fine before migration. Service is running as it should, and Umami is reporting no errors in the cli.

[mauricerenck]

I am experiencing the same in my instance. It worked fine before migration. Service is running as it should, and Umami is reporting no errors in the cli.

I had to upgrade the machine to micro, after that it's working fine. Running not from docker but directly from the repo showed a nextjs error saying it needs more RAM.

[marc-on-github]

Okay for me, the error was that I was still on Node version 14. After the Update to Node 16 everything works again.

[BradNut]

Nothing has changed on the CORS end of things and we are running the same codebase in production. Is it possible you have something else sending different headers?

I had the same issue described in this bug and, like @marc-on-github, upgrading from Node version 14 to 16 allowed everything to work correctly without CORS issues. My deploy and issue was on Vercel.

Maybe the minimum Node version requirements differ on different platform deployed?

[X-Ryl669]

Nope, on a Debian Buster system it also requires a more recent Node version than 14. I'm using NodeJS 18 LTS and it works.

[RamaHerbin]

Hello everyone,
I have a similar issue when I post login credential to the /api/auth/login endpoint.

I request from my front-end on localhost:3000 to umami on localhost:8080

The request works fine in Postman.
What am I doing wrong ?

  fetch("http://localhost:8080/api/auth/login", {
    method: "POST",
    headers: {
      "Content-Type": "application/json",
      'Accept': '*/*',
      "Access-Control-Allow-Headers": "*",
      "Access-Control-Allow-Methods": "*",
      "Access-Control-Allow-Origin": "*",
    },
    body: JSON.stringify(formState),
  })

[mdestafadilah]

same here, i'm using v2 with node v18. now cors has issued.