vuetifyjs / vuetify

🐉 Vue Component Framework
https://vuetifyjs.com
MIT License
39.94k stars 6.97k forks source link

[Documentation] Documentation website is down #20367

Closed eldhosereji541 closed 3 weeks ago

eldhosereji541 commented 3 months ago

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 commented 3 months ago

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

b-maslennikov commented 3 months ago

Looks ok to me

KaelWD commented 3 months ago

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

Screenshot_20240821_202402

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 commented 3 months ago

works now. thanks for the support

KaelWD commented 2 months ago

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 commented 2 months ago

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

joel-wenzel commented 2 months ago

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

userquin commented 2 months ago

Same here:

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

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

jacekkarczmarczyk commented 2 months ago

it does image

KaelWD commented 2 months ago

@jacekkarczmarczyk were you having problems though?

userquin commented 2 months ago

Yes, here the response headers:

access-control-allow-origin: *
age: 3089
cache-control: public, max-age=2678400
cf-cache-status: HIT
cf-ray: 8bd6a6f8be505e1c-MAD
content-disposition: inline; filename="index-BohZX1iR.js"
date: Tue, 03 Sep 2024 15:07:55 GMT
etag: W/"c0ba6d2dad0b42398692e590cda24aa6"
expires: Fri, 04 Oct 2024 15:07:55 GMT
server: cloudflare
strict-transport-security: max-age=63072000

vary: Accept-Encoding
x-vercel-cache: HIT
x-vercel-id: cdg1::76964-1725372986448-068bef019ea2
jacekkarczmarczyk commented 2 months ago

@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 commented 2 months ago

No, still 404 for me in incognito

userquin commented 2 months ago

@KaelWD everything inside the assets folder shouldn't be immutable? I'll check the sw handlers. Looks like the sw has old version but requesting previous /assets/index-BohZX1iR.js and it shouldn't, maybe wrong globPatterns or excluding assets to generate the revision:

imagen

userquin commented 2 months ago

forgot previous comment, I guess the problem in vercel response chache headers...

KaelWD commented 2 months ago

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

userquin commented 2 months ago

no, 404

KaelWD commented 2 months ago

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

userquin commented 2 months ago

yes, it is working: imagen

steeevio commented 2 months ago

Yes, that looks good

KaelWD commented 2 months ago

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

felicienfrancois commented 2 months ago

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

steeevio commented 2 months ago

All working for me now

KaelWD commented 2 months ago

I didn't even touch cloudflare yet lol.

brettvd commented 2 months ago

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 commented 2 months ago

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 commented 2 months ago

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 commented 2 months ago

Me too, on Edge on firefox, it's impossible to navigate into the documentation, it's a critical a bug error_vutify Vuetify website doesn't display on firefox in private image

j-tap commented 1 month ago

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

image

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 commented 1 month ago

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 commented 1 month ago

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 commented 3 weeks ago

We no longer use vercel.