500 Internal Server Error for random js files
Deployment ID: 9e4ea0f3-58ef-4827-87e7-1a7f4b5b3f72
12 Replies
I second this. Some css and js files just get 500 error. Created a new CF Pages project, deployed the same files and there css loads but other js files get 500 error. So it's very random. Deployment ID 5061f269-5303-41c1-883e-ad980bc52114
Got an update to this. My original build had ~2500 files and everything was uploaded successfully through wrangler. Several random js and css files got 500-error however when accessing them. The amount of files are due to articles on the site.
I did a test now and only prerendered part of the articles, ending up with 1050 files, and deployed that. Now everything on CF works and there are no 500-errors, but I need to be able to publish all my articles.
@harshjv @DiAvisoo can you please share a repro URL?
also how did you do this upload? Was it using Pages CI or just through Wrangler?
If Wrangler, what Wrangler version?
@Walshy | Deploying Can I send the url in a private message? Don't want to publish it.
Uploading using wrangler 3.60.0
yeah dm me
Here's a screenshot showing the error, and also a screenshot showing the file was uploaded successfully to Pages if I check under that same deploy
Here it is when I open the file in the browser, 500 error. If I try to open a file that is not there, like XX.pages.dev/testing/something.js I get a blank page. Looking in the console it says 404, so that's to be expected.
Pages CI
DM'ed you url
I am facing the same issues: a generated static website upload using wrangler (tested using 3.60.0 and 3.59.0 as well). I upload about 16K files, which takes a while, and I notice the progress suddenly jump from 8K -> 16K and indicated as success. I suspect wrangler fail to upload all the files (especially if it is a large site), thus the random 500 errors on some files.
Deployment ID: 9e4ea0f3-58ef-4827-87e7-1a7f4b5b3f72
Pages URL: DM'ed @Walshy | Deploying
share following info ^^^ so @Walshy | Deploying can help
Thanks all for reporting. This has now been resolved. If you're using the
wrangler pages deploy command, please update to wrangler 3.60.1 and re-deploy. If you're using Pages CI/CD, you can trigger a new build.Much appreciated!