Getting 404 for `script.js` #1

bogy0 · 2022-10-25T21:59:35Z

First of all, great work with the updates. Watching the conference was really inspiring.
Of course, my first thing to do was to update one of my Next.js projects and try the new goodies.

At one point I decided to try out this new Analytics feature called Audiences, but after adding it to the project I am getting these errors in the console.

After some quick search in the vercel org I came across this repository where I found a reference for this va/script.js file.

Overall, the audiences feature is working, I am getting visitor data in the newly enabled dashboard page; the issue only is that the browser logging this error.

If you need further details, example codes, let me know, but what i did was basically follow your guide:

install @vercel/analytics
import and place the Analytics react component into the _app.jsx file, like this:

import { Analytics } from '@vercel/analytics/react';

import '../styles/globals.css'

const MyApp = ({Component, pageProps }) => {
  return (
      <>
        <Component {...pageProps} />
        <Analytics />
      </>
  );
}

export default MyApp

The text was updated successfully, but these errors were encountered:

frontsideair · 2022-10-25T22:15:02Z

I'm also having a similar problem. I don't get any analytics data on my dashboard though.

I added this to my Gatsby project by adding inject to gatsby-browser.js, which does its job and adds the script to the <head>. But the va/script.js gives a 404, which makes sense because there's no such file anywhere. Is Vercel supposed to intercept and serve this file?

I also have rewrites defined in my project so maybe this is overriding the hypothesized intercept. This may be an edge case.

NuroDev · 2022-10-26T00:01:25Z

But the va/script.js gives a 404, which makes sense because there's no such file anywhere. Is Vercel supposed to intercept and serve this file?

Yeah same here. Have another site that has this package working & manually added the /va/script.js to my public/ directory but then got another error from failing to post to /va/view.

Does seem like it's usually expected that Vercel will add / intercept any requests to /va/... endpoint(s) but it isn't for some reason?

alex-grover · 2022-10-26T03:59:48Z

Seeing a 404 as well with an Astro project, using both the plain HTML approach as well as using inject().

max · 2022-10-26T04:23:10Z

Possibly not the reason y'all are seeing the error but I was also getting a 404 for the injected script when deploying @vercel/analytics. Turns out you first have to enable the feature in the dashboard and then deploy the library (a re-deploy fixed it for me).

bogy0 · 2022-10-26T08:14:19Z

Unfortunately, re-deploying my project is not solved the error log in my case.

chriswdmr · 2022-10-26T08:41:56Z

As @max correctly pointed out, the mentioned path /va/script.js will become available on your next deployment after you enabled the feature.

If you added the package before you enabled the feature, you can trigger a redeployment which has the same effect.

@bogy0 It seems like the error you're seeing is related to your browser as you already get data. Have you tried disabling all extensions/ad-blockers?

tomegger · 2022-10-26T10:24:14Z

Same problem here. I´ve already tried all steps (re-deploying, enabling/disabling, etc.) but still have the same error as @bogy0.

chriswdmr · 2022-10-26T10:38:23Z

Would you mind creating a minimal reproduction?

Ideally a small repo that gets deployed to Vercel so we can have a closer look!

bogy0 · 2022-10-26T11:13:42Z

will do later today

tomegger · 2022-10-26T11:33:31Z

I´ve also a simple app if you want to take a look

frontsideair · 2022-10-26T11:51:10Z

I also tried redeploying but didn't work in my case. It's not minimal but my blog, for which I want to use the analytics, is open-source.

chriswdmr · 2022-10-26T12:46:02Z

I also tried redeploying but didn't work in my case. It's not minimal but my blog, for which I want to use the analytics, is open-source.

Thanks for providing an example!

It seems like that your custom 404 page is catching all routes – including the /va/script.js URL.
You have to instrument Gatsby in a way that it ignores this URL.

frontsideair · 2022-10-26T14:42:07Z

Thanks, I added the redirect manually to bypass Gatsby with the this config, which is transformed with gatsby-plugin-zeit-now plugin. This fixed the 404 issue and requests are actually sent and response is received, but my dashboard doesn't load any data.

chriswdmr · 2022-10-26T15:13:44Z

@frontsideair the script is available behind your own domain and not via vercel.com.
Please change vercel.com to your own domain.

frontsideair · 2022-10-26T15:55:20Z

I understand and removed the redirect to vercel.com, I haven't found a good workaround so I'm giving up on this for now. Waiting for an official solution.

mehulmpt · 2022-10-26T19:04:52Z

Same for us. With rewrites enabled the @vercel/analytics script throws 404.

GizmoRay · 2022-10-26T21:04:04Z

+1 - facing the same issue. Some guidance on how best to handle both a 404 page + allowing the analytics package to come through would be great.

pyronaur · 2022-10-27T05:40:23Z

I created a static blank /va/script.js on my Astro site in hopes that would get replaced, but looks like that didn't do anything either.

vojto · 2022-10-27T08:24:15Z

Same issue with SvelteKit.

schnubor · 2022-10-27T14:31:35Z

Having the same problem (script 404) on a Next 13 app (still using /pages) with a custom 404 page. disabled & enabled the feature in the vercel UI again and redeployed, still 404ing. Also not seeing any data in the Audience dashboard which I think is just a side effect. It says "Vercel Analytics is set up, but detected a non-production environment." on my local though, so it's at least trying to do something.

diffTed · 2022-10-27T16:05:49Z

Same here (Next 13)

tobiaslins · 2022-10-27T18:36:13Z

We're actively working on a solution for this issue. We'll keep you posted!

sgarcia22 · 2022-10-27T23:15:22Z

Same problem, I get a Uncaught SyntaxError: Unexpected token '<' (at script.js:1:1) and cannot access any analytics.

I'm using Vue v2, and tried injecting it with the inject() call in both the app.js mounted() callback, and in main.js when creating the Vue app.

Also tried using it in the HTML <script async src="/va/script.js"></script>.

In my routes I have this however, not sure if that is causing a problem like the comments above or how I would go about fixing that.

  {
    path: "/:catchAll(.*)",
    name: "NotFound",
    redirect: "/",
    meta: {title: "😔 - 404"},
  },

remisture · 2022-10-28T16:17:21Z

We're actively working on a solution for this issue. We'll keep you posted!

Any updates?

aprendendofelipe · 2022-10-29T16:51:49Z

There seems to be an incompatibility with the i18n configuration in next.config.js.

JoshLittlewood · 2022-10-29T19:34:00Z

Removing i18n from my next.config.js did resolve the issue for me.

frontsideair · 2022-11-02T14:36:03Z

Works for me as well, thanks! As a docs suggestion, I added the inject script to gatsby-node.js for Gatsby, as it seemed like the correct place for it.

paulmwatson · 2022-11-02T14:40:17Z

Thanks @dglsparsons, just did a re-deploy there (leaving analytics enabled) and same error.

darasus · 2022-11-02T14:49:45Z

Same, redeployed multiple times while analytics enabled and still seeing 404

dglsparsons · 2022-11-02T14:51:25Z

Okay, it seems like we still have some issues relating to i18n interfering with analytics. We're working on a fix for sites using i18n now. I believe sites without i18n should work fine though.

vacodoceo · 2022-11-02T15:37:18Z

@tobiaslins still having the same error with SvelteKit

tobiaslins · 2022-11-02T15:39:14Z

@vacodoceo can you please share the last deployment url with us to take a closer look?

Robin-w151 · 2022-11-02T16:42:31Z

I can confirm that it is now working for my SvelteKit app after I did a redeployment and leaving audiences enabled.

dglsparsons · 2022-11-02T16:58:02Z

Hi, further update here: we've shipped a change that should resolve any issues with i18n interference. You'll need to redeploy (again) to see the changes, but 🤞 this resolves any remaining issues! Let me know if it doesn't work :)

vacodoceo · 2022-11-02T17:04:22Z

@tobiaslins I just checked again and it's working. I enabled audiences, redeployed, and it started working. It's strange because I redeployed a couple of times an hour ago and it didn't work, and I don't think enabling audiences was what fixed it.

Anyway, thanks for the support!

tobiaslins · 2022-11-02T17:11:54Z

@vacodoceo we just rolled out a fix for i18n, it takes a while until it's available for everyone!
thanks for confirming 🤗

tjkohli · 2022-11-02T17:14:24Z

It works with SvelteKit after redeploying! Thank you so much. 🙏🏼

tomegger · 2022-11-02T17:46:09Z

It works now! 🙌

paulmwatson · 2022-11-02T18:40:17Z

Excellent, it works now, thanks for the work

mehulmpt · 2022-11-02T19:47:28Z

Works for us too 🙌

schnubor · 2022-11-02T19:48:05Z

Works, thanks! :)

aprendendofelipe · 2022-11-02T20:04:49Z

Now it's working with i18n. Thanks!

Dogtiti · 2023-04-30T03:38:27Z

same issue

tobiaslins · 2023-05-02T06:34:32Z

@FlatMapIO @Dogtiti can you please send me a deployment URL so I can take a look for you? Happy to dig deep!

Dogtiti · 2023-05-02T06:47:42Z

@tobiaslins https://auto-agentgpt.com/

tobiaslins · 2023-05-02T07:03:08Z

@Dogtiti It seems like you've already collected data once with that domain but currently Web Analytics for that project is disabled. Head over to the Analytics tab for this project, enable it & redeploy to start collecting data again!

Dogtiti · 2023-05-02T07:05:02Z

ok,thanks

…

---Original--- From: "Tobias ***@***.***> Date: Tue, May 2, 2023 15:03 PM To: ***@***.***>; Cc: ***@***.******@***.***>; Subject: Re: [vercel/analytics] Getting 404 for `script.js` (Issue #1) @Dogtiti It seems like you've already collected data once with that domain but currently Web Analytics for that project is disabled. Head over to the Analytics tab for this project, enable it & redeploy to start collecting data again! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

reevosolutions · 2023-06-16T04:52:11Z

I think this happens when you integrate the analytics on your project without activating the analytics on Vercel

valdemardev01 · 2023-10-26T17:23:39Z

Found out that mby if you use adblock, that will stop the script.js from running.

rkreicbergs-sorsera · 2023-11-15T11:50:54Z

We also get 404 errors in Datadog, but not sure it's the same issue.

We've enabled Analytics for our app and we actually see data in dashboard
we use the NPM package in our _app.tsx:

 import { Analytics } from "@vercel/analytics/react"; 
 [....]
<Analytics />

in DataDog we an error about 404 from https://vitals.vercel-insights.com/v1/view?dsn=vxVf....
If I understand corretly, the plugin calls /_vercel/insights/view which gets the error and the logs it
as noted, we do see data in the dashbaord and this issue is intermittent, but seems to happen at least once in 2 days and we've done a bunch of new deployments since enabling it - the problem persists
last error today was for sorsera-bzouxhxkx-sorsera.vercel.app

Can any of this be explained by ad blockers? IIUC, that could not explain it - it would simple not call /_vercel/insights/view at all and thus we'd not get any errors, no?

Can this be explained by a crawler or smth accessing /_vercel/insights/view directly? if I open it manually, just got the same type of error in DataDog. Can I enable some input validation for that page or something? If nothing else, we'll just ignore all those logs completely, which doesn't seem like the right approach.

oucar · 2024-04-14T16:04:39Z

I got the exact same error, in my environment my ad blocker was causing the issue. Disabling it solved the problem.

bogy0 changed the title ~~Browser error logged in the console after adding Audiences to a Next.js app~~ Browser error logged in the console after adding @vercel/analytics to a Next.js app Oct 25, 2022

zernonia mentioned this issue Oct 27, 2022

How to use this module in a Nuxt 3 app? #5

Closed

tobiaslins added the bug Something isn't working label Oct 27, 2022

aprendendofelipe mentioned this issue Oct 28, 2022

Atualiza para Next.js 13, além de atualizar outras dependências e habilitar o Analytics filipedeschamps/tabnews.com.br#792

Merged

aprendendofelipe mentioned this issue Nov 2, 2022

Habilita Analytics filipedeschamps/tabnews.com.br#794

Merged

tobiaslins closed this as completed Nov 3, 2022

kempsterrrr mentioned this issue Nov 4, 2022

[Bug]: Vercel Analytics not working Developer-DAO/developer-dao-dot-com#45

Closed

10 tasks

agurtovoy mentioned this issue Feb 17, 2023

HTTP 404 on /_vercel/insights/script.js #49

Closed

Yidadaa mentioned this issue Apr 5, 2023

如果没有使用 Vercel 部署，如何关闭相关功能避免输出报错 ChatGPTNextWeb/ChatGPT-Next-Web#487

Closed

Getting 404 for script.js #1

Getting 404 for script.js #1

Comments

bogy0 commented Oct 25, 2022

frontsideair commented Oct 25, 2022

NuroDev commented Oct 26, 2022

alex-grover commented Oct 26, 2022 • edited

max commented Oct 26, 2022

bogy0 commented Oct 26, 2022

chriswdmr commented Oct 26, 2022 • edited

tomegger commented Oct 26, 2022

chriswdmr commented Oct 26, 2022

bogy0 commented Oct 26, 2022

tomegger commented Oct 26, 2022

frontsideair commented Oct 26, 2022

chriswdmr commented Oct 26, 2022

frontsideair commented Oct 26, 2022

chriswdmr commented Oct 26, 2022

frontsideair commented Oct 26, 2022

mehulmpt commented Oct 26, 2022

GizmoRay commented Oct 26, 2022

pyronaur commented Oct 27, 2022

vojto commented Oct 27, 2022

schnubor commented Oct 27, 2022 • edited

diffTed commented Oct 27, 2022 • edited

tobiaslins commented Oct 27, 2022

sgarcia22 commented Oct 27, 2022

remisture commented Oct 28, 2022

aprendendofelipe commented Oct 29, 2022

JoshLittlewood commented Oct 29, 2022

frontsideair commented Nov 2, 2022

paulmwatson commented Nov 2, 2022

darasus commented Nov 2, 2022

dglsparsons commented Nov 2, 2022

vacodoceo commented Nov 2, 2022

tobiaslins commented Nov 2, 2022

Robin-w151 commented Nov 2, 2022

dglsparsons commented Nov 2, 2022

vacodoceo commented Nov 2, 2022

tobiaslins commented Nov 2, 2022

tjkohli commented Nov 2, 2022

tomegger commented Nov 2, 2022

paulmwatson commented Nov 2, 2022

mehulmpt commented Nov 2, 2022

schnubor commented Nov 2, 2022

aprendendofelipe commented Nov 2, 2022

Dogtiti commented Apr 30, 2023

tobiaslins commented May 2, 2023

Dogtiti commented May 2, 2023

tobiaslins commented May 2, 2023

Dogtiti commented May 2, 2023 via email

reevosolutions commented Jun 16, 2023

valdemardev01 commented Oct 26, 2023 • edited

rkreicbergs-sorsera commented Nov 15, 2023 • edited

oucar commented Apr 14, 2024

Getting 404 for `script.js` #1

Getting 404 for `script.js` #1

alex-grover commented Oct 26, 2022 •

edited

chriswdmr commented Oct 26, 2022 •

edited

schnubor commented Oct 27, 2022 •

edited

diffTed commented Oct 27, 2022 •

edited

valdemardev01 commented Oct 26, 2023 •

edited

rkreicbergs-sorsera commented Nov 15, 2023 •

edited