next-axiom: 403 on Vercel

Hello everyone,

I’m using:

next@12.3.3
react@17 (unfortunately, we’re using a must-have dependency that only works on react 17)
next-axiom@0.17.0

My application is being deployed to Vercel. I’ve setup the integration with Axiom (it was as seamless as they come, indeed), the environment variable was created automatically, and Axiom started ingesting data (server-side logs, etc). Then I moved to using the withAxiom HOC, in order to enable client-side log and reportWebVitals.

But, whenever those trigger, I can see a 403 error: Both requests hit this url: https://<my-domain>/_axiom/<web-vitals|logs>

And the response (for either) is an empty object:

Can anyone help me shed some light on this? Thank you!

About this issue

Original URL
State: closed
Created a year ago
Reactions: 3
Comments: 18 (4 by maintainers)

Most upvoted comments

I confirm that I am able to reproduce. I will take a look on why this might be happening and get back to you.

schehata on Apr 5, 2023

Hey everyone, we found the bug and fixed it on our side! Very sorry for the inconvenience — feel free to reopen if you still experience this issue ✌️

bahlo on Apr 13, 2023

Hey, this has high priority for us so expect an update in the next days 👍

bahlo on Apr 11, 2023

Amazing guys ! Thanks for the fix

odcey on Apr 13, 2023

@matthewlilley Oh, that’s interesting! We’re actively working on improving the experience around reaching field limits right now.

Nonetheless this shouldn’t be a 403, looking into that (internal issue #: AXM-1468)

bahlo on Aug 28, 2023

@odcey are you trying on a production deployment or a preview one? have you added any env variables to vercel settings? there should be a NEXT_PUBLIC_AXIOM_INGEST_ENDPOINT that is enabled by default for production.

@schehata yes I have this env variable, it was added automatically to Vercel with production checked

odcey on Apr 5, 2023