[Documentation] Documentation website is down

[eldhosereji541]

Environment

Browsers: Chrome 127.0.6533.120
OS: Windows 11 Home

Steps to reproduce

just open the documentation website

Expected Behavior

open and load contents normally

Actual Behavior

blank page, error on the console:
GET https://vuetifyjs.com/assets/index-CmOmPrj2.js net::ERR_ABORTED 404 (Not Found)

Reproduction Link

https://vuetifyjs.com/en/

[maniper]

I encounter the same issue. I cannot view the documentation anymore.

[b-maslennikov]

Looks ok to me

[KaelWD]

We've been having intermittent CDN problems in some regions:

Does https://vuetify-3-jojqdczgg-vuetifyjs1.vercel.app/ load? If not you can try running it locally: https://github.com/vuetifyjs/vuetify/blob/master/packages/docs/src/pages/en/getting-started/contributing.md#local-development

[eldhosereji541]

works now. thanks for the support

[KaelWD]

If anyone else is getting this can you please post the failed request path and its x-vercel-id response header?
Also try opening the failed asset in an incognito window.

[steeevio]

Down for me
request url: https://vuetifyjs.com/assets/index-BohZX1iR.js
x-vercel-id: cdg1::zwwd4-1725372979425-a3884859715e

[joel-wenzel]

Also me:
request url: https://vuetifyjs.com/assets/index-BohZX1iR.js
x-vercel-id: iad1::89lmz-1725372978834-79c720d0e137

[userquin]

Same here:

Request-URL: https://vuetifyjs.com/assets/index-BohZX1iR.js
x-vercel-error: NOT_FOUND
x-vercel-id: cdg1::zwwd4-1725372979425-a3884859715e

[KaelWD]

Does https://vuetifyjs.com/assets/index-BohZX1iR.js load in an incognito window?

[jacekkarczmarczyk]

it does

[KaelWD]

@jacekkarczmarczyk were you having problems though?

[jacekkarczmarczyk]

@jacekkarczmarczyk were you having problems though?

Actually no, I've just tried if .js opens in non-incognite mode and it redirected to https://vuetifyjs.com/en/assets/index-BohZX1iR.js/ (that's why I though there might be a problem with the site as well), but in network tab (when I'm on the page) it loads fine

[steeevio]

No, still 404 for me in incognito

[KaelWD]

Yes BohZX1iR is current. Is the page loading for you now @userquin?

[userquin]

no, 404

[KaelWD]

How about https://vuetify-3-eod0x2mgd-vuetifyjs1.vercel.app/assets/index-BohZX1iR.js @steeevio

[userquin]

yes, it is working:

[steeevio]

Yes, that looks good

[KaelWD]

But https://vuetifyjs.com/assets/index-BohZX1iR.js is still broken? I'll try purging cloudflare, it shouldn't be caching 404s though.

[felicienfrancois]

I have the same issue on chrome right now (vercel ID cdg1::zwwd4-1725372979425-a3884859715e).
Work correctly on Firefox

[steeevio]

All working for me now

[KaelWD]

I didn't even touch cloudflare yet lol.

[brettvd]

I'm still seeing the issue. Receiving a 404 on the GET for an index file. Different index file name (index-D0V9Cts6.js). I tried using the same direct URL @KaelWD provided above, but replaced with my file name and that didn't work (not sure it should, though).

I've tried Incognito and tried other browsers, all get the same error.

[KaelWD]

There has been another deployment since then, the new one is https://vuetify-3-ngene0f1n-vuetifyjs1.vercel.app/

Use a fresh incognito window between attempts to rule out service worker shenanigans or curl -sS -D - '...url...' -o /dev/null to rule out the browser entirely.

$ curl -sS -D - 'https://vuetify-3-ngene0f1n-vuetifyjs1.vercel.app/assets/index-D0V9Cts6.js' -o /dev/null
HTTP/2 200 
accept-ranges: bytes
access-control-allow-origin: *
age: 2010
cache-control: public, max-age=3600, s-maxage=60, must-revalidate
content-disposition: inline; filename="index-D0V9Cts6.js"
content-type: application/javascript; charset=utf-8
date: Tue, 03 Sep 2024 17:18:27 GMT
etag: "6aa92f80cb5dcca66ed5127c893acbd4"
server: Vercel
strict-transport-security: max-age=63072000; includeSubDomains; preload
x-robots-tag: noindex
x-vercel-cache: HIT
x-vercel-id: syd1::xlvp6-1725383907515-ef22b1371d84
content-length: 1171178

$ curl -sS -D - 'https://vuetifyjs.com/assets/index-D0V9Cts6.js' -o /dev/null     
HTTP/2 200 
date: Tue, 03 Sep 2024 17:20:07 GMT
content-type: application/javascript; charset=utf-8
access-control-allow-origin: *
cache-control: public, max-age=2678400
content-disposition: inline; filename="index-D0V9Cts6.js"
etag: W/"6aa92f80cb5dcca66ed5127c893acbd4"
strict-transport-security: max-age=63072000
x-vercel-cache: HIT
x-vercel-id: syd1::rt2hj-1725384007226-5f206f531b53
cf-cache-status: MISS
expires: Fri, 04 Oct 2024 17:20:07 GMT
server: cloudflare
cf-ray: 8bd7689d0f7ca819-SYD

[brettvd]

I wasn't able to run the curl tests, they were timing out (not sure if VPN related or not).

But as I was trying I noticed my dev tools started spamming network calls from an open tab I had been inspecting. It looks like something just happened and now the site is loading.

(For at least a few weeks now, the site wouldn't load at all unless I was in Incognito. I assumed it was work PC related stuff. But now it's loading normally)

[reno184]

Me too, on Edge on firefox, it's impossible to navigate into the documentation, it's a critical a bug

Vuetify website doesn't display on firefox in private

[j-tap]

https://vuetifyjs.com/en/api/v-app-bar/
Display blank page

https://vuetifyjs.com/en/
Correct display

https://vuetifyjs.com/en/api/
Correct display of 404 page

My location: Ecuador
Using vpn doesn't change anything

[SunWuyuan]

https://vuetifyjs.com Display blank page

https://vuetifyjs.com/assets/index-DK_ffwoj.js 404 Not Found
Regardless of privacy mode, multiple devices, multiple browsers

China , The website is provided by [2606:4700::6810:8783]:443 Cloudflare , no vpn

[sbglasius]

Denmark:

Request URL: https://vuetifyjs.com/assets/index-DK_ffwoj.js
x-vercel-error:NOT_FOUND
x-vercel-id: cdg1::tdtnk-1727958708330-5705deab4c5e

The direct url: https://vuetify-3-ngene0f1n-vuetifyjs1.vercel.app/en/components/grids/#margin-helpers is working (and is a workaround for now)

[KaelWD]

We no longer use vercel.