last comment
⌘K
Patrick Donahue This is the filesystem check. With cleanUrls: true, /about maps to about.html and / maps to index.html, and the vercel.json docs say rewrites only run after the filesystem: "The source property should NOT be a file because precedence is given to the filesystem prior to rewrites being applied." So for any path that has a real HTML file, the rewrite never fires. Your headers rule still matches though, which is why you can end up with HTML in the body and a markdown content type on top. What worked for me is moving the Accept-header rule into routes, which is evaluated before the filesystem. I re
Izumie Thanks, yeah I've changed rewrite into route and it worked. but agents are accessing different markdown paths like for about.html(with clean url 'about') getting the request at about/_markdown/about.md instead of accessing the page itself.
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Amy Egan Did you try the debugging tips linked above? I'd recommend checking the build settings and output to figure out why the page is missing
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/domains/troubleshooting
Hali Is anyone there
Amy Egan Hey, James. Appreciate you reaching out about this. The team shipped an update yesterday so your dashboard now reflects each day's deployment storage amount instead of the billing period maximum. I'm linking some Deployment Storage optimization tips in case you still need help reducing the amount of storage used vercel.com/docs/deployment-storage/optimize
James Singleton Hi Amy. Yea after doing some Googling I was able to find stuff about it. It's a little concerning that this was pushed out without an email letting users know. All of a sudden I was getting emails saying that I was using 40 GB of the 10 GB of deployment storage with a single deployment taking up like 30 GB. I started to panic! One issue I ran into is that retention policies were defaulted to 30 days for everything. Even after setting some to 1 week and in some cases 1 day, I wasn't seeing deployments being removed. I had to go through and manually delete deployments. I basically had to delete
James Singleton To add to this, there are projects where the retention is 30 days and I have deployments from January still in my Deployments tab. This project was defaulted to 30 days and I have deployments from Jan-May still there.
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Amy Egan Thanks for sharing the project name. That helped me find the deployment. It looks like the 404 error has code NOT_FOUND rather than DEPLOYMENT_NOT_FOUND. That means the index/home page of your project doesn't exist where it was expected. The debugging tips linked above have more info about how to check the deployment output and solve the issue
system While a member of our team prepares to jump in, you might find your answer even faster in our community resources. Official Documentation: v0.app/docs The v0 expert walkthrough: community.vercel.com/t/become-a-v0-expert/5981 Watch v0 in Action: community.vercel.com/live#v0
Ro84833 study-dashboard-two-pied.vercel.app this is the app if you want to see the problem yourself the data and the hours are added before my actions
