Umami Cloud tracking returns 404 on gateway.umami.is/api/send

[JJV-APL]

Hello,

I have just set up Umami Cloud for my website, but no statistics are being recorded.

Website:
https://www.apl-landeron.ch/

Umami website:
APL – Le Landeron

Website ID:
53ede41f-038a-47ee-8dec-a7c5c9229efc

Domain configured in Umami:
apl-landeron.ch

The tracking script is correctly loaded on the website:

<script defer src="https://cloud.umami.is/script.js" data-website-id="53ede41f-038a-47ee-8dec-a7c5c9229efc"></script>

I have verified that the browser sends the correct hostname and website ID:

x-umami-hostname: apl-landeron.ch
x-umami-website-id: 53ede41f-038a-47ee-8dec-a7c5c9229efc

However, the browser console shows:

POST https://gateway.umami.is/api/send 404 (Not Found)

As a result, the Umami dashboard remains at 0 visitors, 0 visits and 0 page views.

I also tested https://gateway.umami.is/api/send directly in the browser. It responds with:

{"error":"GET method not allowed"}

So the gateway itself is reachable.

Could you please let me know why the POST request for this website is returning 404?

Thank you!

[dfbustosus]

This is not a reachability, CSP, consent, or ad-blocker failure. The Cloud gateway is reachable, but it currently does not recognize that Website ID.

I checked the public page and gateway without sending a valid analytics event:

• The live HTML contains the UUID shown above, and https://cloud.umami.is/script.js loads successfully.
• OPTIONS /api/send succeeds with the expected CORS headers.
• A deliberately invalid event type using this UUID returns 404 {"error":"Website not found"} for both apl-landeron.ch and www.apl-landeron.ch.
• The same invalid-type request using a known registered Cloud Website ID reaches schema validation and returns 400 instead. A random validly formatted UUID produces the same 404 as yours.

That isolates the failure to the Website ID lookup. GET /api/send returning “GET method not allowed” only proves the route exists; it does not validate a website registration.

Recommended checks:

1. In Umami Cloud, open the website and copy the tracking code again rather than copying the UUID manually.
2. Confirm the website still exists in the same Cloud account and that Cloud account/data-region setup is complete.
3. Confirm this ID came from Umami Cloud, not a self-hosted Umami instance. Cloud cannot resolve a self-hosted database ID.
4. In the existing failed DevTools request, verify payload.website and save the UTC time, response body, and cf-ray response header. Do not replay the request with a valid event type.

The website Domain value is not the likely cause. The tracker reads window.location.hostname, and your www and non-www hosts both currently serve the page. Domain configuration is used for referrer filtering; exact client-side hostname filtering only applies when data-domains is present, and the live tag does not contain it.

If the Cloud dashboard still displays exactly 53ede41f-038a-47ee-8dec-a7c5c9229efc, this is most likely a Cloud-side registration/provisioning mismatch. Only Umami can distinguish delayed propagation, stale registration, or another account-side issue. Send support the Website ID, selected data region, UTC failure time, response JSON, and cf-ray; provide the account email privately and do not include credentials.

The current tracker includes the Website ID in both its payload and request headers: tracker source. gateway.umami.is is also the current documented Cloud collection endpoint: Cloud changelog. Changing data-host-url or proxying the same request will not repair an unknown Website ID.

[JJV-APL]

Thanks for the detailed investigation.

I confirmed that my Umami Cloud account is configured with the following data region: EU (Frankfurt).

Website ID: 53ede41f-038a-47ee-8dec-a7c5c9229efc
Website: APL – Le Landeron
Domain: apl-landeron.ch

The tracking code shown in the Umami Cloud website settings is still exactly the same as the one installed on the website.

Please let me know what additional information you need to check the Cloud-side registration/provisioning of this Website ID.