Closed kamerat closed 2 years ago
ascorbic
commented
2 years ago Hi. If you go to the deploy page, there should be a tiny little arrow link to download the deploy:
Could you do that and see if the missing files exist in the bundle? They would be in static
kamerat
commented
2 years ago If you go to the deploy page, there should be a tiny little arrow link to download the deploy:
Wow, I've never seen that button. Really neat! Thanks for the tip.
Could you do that and see if the missing files exist in the bundle? They would be in
static
I can confirm that they do exist in the bundle under /static. However I noticed in the network tab on the failing site, the path is https://deploy-preview-152--nyladeklar.netlify.app/_next/static/chunks/webpack-f6f3c391358fe789.js not
https://deploy-preview-152--nyladeklar.netlify.app/static/chunks/webpack-f6f3c391358fe789.js
In /_next there is only a sub-folder data, no static folder.
I tested to go to https://deploy-preview-152--nyladeklar.netlify.app/static/chunks/webpack-f6f3c391358fe789.js (without _next prefix) and it works.
Seems the _next part of the url is messing things about?
Is this something I have configured wrongly, or is this a bug?
Thank you for your quick reply.
vpreponen
commented
2 years ago I had the same issue and fixed it with a redirect.
[[redirects]]
from = "/_next/static/*"
to = "/static/:splat"
status = 301
force = trueThe strange thing is that if you look at the build logs you can see that there is already a rewrite that does that:
{ from: '/_next/static/*', to: '/static/:splat', status: 200 }
The file will be in the top level in static, rather than in _next, and the rewrite should handle it. Is the file in there?
kamerat
commented
2 years ago I do not have this rewrite rule written myself as far as I'm aware, but you are correct that it's present in the build logs. - Is it provided by default?
I don't quite understand your question, @ascorbic.
This is what my static folder looks like from the downloaded build zip:
ascorbic
commented
2 years ago Thanks. So it looks like the pages are there, but for some reason the auto-generated redirect isn't working. Looking at the logs it seems you have an existing _redirects file. Coudl you share it please?
kamerat
commented
2 years ago This is the current _redirects file:
kamerat
commented
2 years ago I noticed now when providing you with the_redirects file, that the hidden gem /* /404/ 404/ was lurking at the bottom there. 🤦♂️ I removed this in a test commit and now netlify builds correctly! 🎉 I have to talk to a team member on why this was added previously. However, odd that this does not break the page when using netlify-plugin-nextjs@3.9.1 🤔
ascorbic
commented
2 years ago Aha! That's great news. I spotted that and was just about to reply. I think I'll add the _redirects file to the issue template, but also add a build time check for root level redirects liek that.
kamerat
commented
2 years ago That's some good ideas! Thank you a lot for helping out here, and thanks for the good tips along the way. I really appreciate your time.
ascorbic
commented
2 years ago No worries. Thanks for the report and your help in tracking it down.
eramdam
commented
2 years ago Sorry to bump this thread, but I'm running into a similar issue, I have no conflicting redirects in _redirects and the workaround shared by @vpreponen doesn't seem to fix the issue either.
Here are relevant the links:
I also attached the zip generated on the deploy page, and I can confirm that the JS/CSS assets return a 404 when running locally. However, when viewing in a browser, they seem to return a 200 just fine, but there's a CSP error popping in the console.
deploy-61caf38bc8ffb800084bdfdf.zip
Local:
Live:
EDIT: After playing around, it seems like the culprit is the asset optimization feature, I had it enabled on my project (that previously used Gatsby) and the CSS part of it is what causes the issue. I assume this is a bug on Netlify's end? I'm not sure, in any case, hopefully, this helps anybody running into the same issue 😁 After disabling the CSS optimizations, the styles load properly!
iankduffy
commented
2 years ago Had the same issue removing CSS optimizations fixed it. Not sure the reason why it is failing though.
ascorbic
commented
2 years ago Hi @iankduffy: yes, you should never use asset optimizations with frameworks like Next which perform their own optimization. We've updated the docs to make this clearer.
q-luisnesi
commented
1 year ago Hi I have the same issue but asset optimisation is disabled and not toml file for redirect is created can someone help us to identify the real reason why this is happening. Our project is still in early stages.
alex-major-digital
commented
1 year ago Hi I have the same issue but asset optimisation is disabled and not toml file for redirect is created can someone help us to identify the real reason why this is happening. Our project is still in early stages.
Same issue here, recently just happened after making a small CSS push
niklashigi
commented
1 year ago @q-luisnesi @alex-major-digital Same here; in our case we didn't change anything about the code; we only had our CMS trigger a build due to some content changes and now our site is effectively down (without any CSS). I just reached out to Netlify support and will post an update if I hear anything!
q-luisnesi
commented
1 year ago @shroudedcode and @alex-major-digital i Contacted netlify and they said is code issue and i cannot find the issue funny enough now the website is working and i did not changed anything i believe this is a cache problem. I will post more info if i found the cause. Thanks
niklashigi
commented
1 year ago Hey guys, still don't know what caused this issue, but a temporary fix for us was going back to a previous deploy that we know still worked and pressing "Publish" to basically "bring back" that old version. Our site is back online now (but I'd imagine the next deploy would wreck it again).
q-luisnesi
commented
1 year ago @shroudedcode I tried that solution but the problem is immediately the error came back once a new deploy landed.
niklashigi
commented
1 year ago @q-luisnesi Yeah, this seems to be an issue Netlify has to resolve on their end. See this incident they just posted on their status page.
q-luisnesi
commented
1 year ago @shroudedcode agreed they are investigating that what support told me
4lm
commented
1 year ago I have the same issue. Did a change in a Markdown file and pushed it to main, which triggered a re-deploy, which resulted in 404s for all JS and CSS of that deployment. I took a deploy preview from Sunday to fix this. I think it's an issue on Netlifys end. Hopefully, they will inform us soon about what to do.
Edit: As @shroudedcode noted, they seem to work and investigate on this issue.
Steps to reproduce
A link to a reproduction repository
No response
Plugin version
4.0.0
More information about your build
netlify.toml)What OS are you using?
No response
Your
netlify.tomlfile
No .toml file for this project, everything is default except this: netlify.tomlNetlify build settingsRelevant log output (or link to your logs)
Build logs
https://app.netlify.com/sites/nyladeklar/deploys/61b8ba533ac12329b6de8d74 ``` 4:37:55 PM: Build ready to start 4:37:57 PM: build-image version: a6bb34428a07e7de82f4df5dfe1843fbde91f670 (focal) 4:37:57 PM: build-image tag: v4.5.1 4:37:57 PM: buildbot version: 5284b4d1b8b4cf691b29019968d8e4eb3089acdd 4:37:57 PM: Fetching cached dependencies 4:37:57 PM: Starting to download cache of 407.4MB 4:37:59 PM: Finished downloading cache in 1.968286478s 4:37:59 PM: Starting to extract cache 4:38:18 PM: Finished extracting cache in 18.981575001s 4:38:18 PM: Finished fetching cache in 21.105437945s 4:38:18 PM: Starting to prepare the repo for build 4:38:19 PM: Preparing Git Reference pull/152/head 4:38:19 PM: Parsing package.json dependencies 4:38:20 PM: Starting build script 4:38:20 PM: Installing dependencies 4:38:20 PM: Python version set to 2.7 4:38:21 PM: Started restoring cached node version 4:38:23 PM: Finished restoring cached node version 4:38:24 PM: v16.13.1 is already installed. 4:38:24 PM: Now using node v16.13.1 (npm v8.1.2) 4:38:24 PM: Started restoring cached build plugins 4:38:24 PM: Finished restoring cached build plugins 4:38:24 PM: Attempting ruby version 2.7.2, read from environment 4:38:26 PM: Using ruby version 2.7.2 4:38:27 PM: Using PHP version 8.0 4:38:27 PM: Started restoring cached node modules 4:38:27 PM: Finished restoring cached node modules 4:38:27 PM: Started restoring cached go cache 4:38:27 PM: Finished restoring cached go cache 4:38:27 PM: go version go1.16.5 linux/amd64 4:38:27 PM: go version go1.16.5 linux/amd64 4:38:27 PM: Installing missing commands 4:38:27 PM: Verify run directory 4:38:29 PM: 4:38:29 PM: ──────────────────────────────────────────────────────────────── 4:38:29 PM: Netlify Build 4:38:29 PM: ──────────────────────────────────────────────────────────────── 4:38:29 PM: 4:38:29 PM: ❯ Version 4:38:29 PM: @netlify/build 20.3.1 4:38:29 PM: 4:38:29 PM: ❯ Flags 4:38:29 PM: baseRelDir: true 4:38:29 PM: buildId: 61b8ba533ac12329b6de8d72 4:38:29 PM: deployId: 61b8ba533ac12329b6de8d74 4:38:30 PM: 4:38:30 PM: ❯ Current directory 4:38:30 PM: /opt/build/repo 4:38:30 PM: 4:38:30 PM: ❯ Config file 4:38:30 PM: No config file was defined: using default values. 4:38:30 PM: 4:38:30 PM: ❯ Context 4:38:30 PM: deploy-preview 4:38:30 PM: 4:38:30 PM: ❯ Loading plugins 4:38:30 PM: - @netlify/plugin-nextjs@4.0.0 from Netlify app 4:38:30 PM: 4:38:30 PM: ──────────────────────────────────────────────────────────────── 4:38:30 PM: 1. @netlify/plugin-nextjs (onPreBuild event) 4:38:30 PM: ──────────────────────────────────────────────────────────────── 4:38:30 PM: 4:38:31 PM: Next.js cache restored. 4:38:31 PM: Netlify configuration property "build.environment.NEXT_PRIVATE_TARGET" value changed. 4:38:31 PM: 4:38:31 PM: (@netlify/plugin-nextjs onPreBuild completed in 641ms) 4:38:31 PM: 4:38:31 PM: ──────────────────────────────────────────────────────────────── 4:38:31 PM: 2. Build command from Netlify app 4:38:31 PM: ──────────────────────────────────────────────────────────────── 4:38:31 PM: 4:38:31 PM: $ npm run build 4:38:32 PM: > eloway-io@0.1.0 build 4:38:32 PM: > next build 4:38:33 PM: info - Checking validity of types... 4:39:04 PM: ./components/Footer/components/Socials.tsx 4:39:04 PM: 29:29 Warning: Do not use