Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server crashing when serving videos #61

Closed
erikvanek opened this issue Mar 23, 2023 · 1 comment
Closed

Server crashing when serving videos #61

erikvanek opened this issue Mar 23, 2023 · 1 comment
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@erikvanek
Copy link

Hey,
I have recently migrated to eleventy 2.0.

I'm experiencing one DX issue that fortunately does not impact the outcome of file transformation. Just reduces the developer experience I have when using eleventy.

My site hosts several *.mp4 videos that I'm embedding to several reveal.js presentations. When I click a link on my site that points to the presentation, console immediately throws

(node:37344) UnsupportedWarning: Status message is not supported by HTTP/2 (RFC7540 8.1.2.4) (Use node --trace-warnings ... to show where the warning was created)

When I use node --trace warnings I get this

(node:38119) UnsupportedWarning: Status message is not supported by HTTP/2 (RFC7540 8.1.2.4) at statusMessageWarn (node:internal/http2/compat:118:13) at Http2ServerResponse.set statusMessage [as statusMessage] (node:internal/http2/compat:660:5) at write (/home/erik/dev/erikvanek.github.io/node_modules/finalhandler/index.js:279:23) at AsyncResource.runInAsyncScope (node:async_hooks:203:9) at listener (/home/erik/dev/erikvanek.github.io/node_modules/on-finished/index.js:170:15) at onFinish (/home/erik/dev/erikvanek.github.io/node_modules/on-finished/index.js:101:5) at callback (/home/erik/dev/erikvanek.github.io/node_modules/ee-first/index.js:55:10) at Http2ServerRequest.onevent (/home/erik/dev/erikvanek.github.io/node_modules/ee-first/index.js:93:5) at Http2ServerRequest.emit (node:events:513:28) at endReadableNT (node:internal/streams/readable:1358:12)

Once that has happened server is no longer running and I have to restart manually again. When I inspect the Network tab within my client the requested resource (video) does not even have a response code. It is just a failed request.

Attaching a picture of my running site and failed network requests.
eleventy-bug

@zachleat
Copy link
Member

zachleat commented Jun 4, 2024

I think this is a duplicate of #51, fixed with dev server 2.0

@zachleat zachleat closed this as not planned Won't fix, can't repro, duplicate, stale Jun 4, 2024
@zachleat zachleat added this to the Eleventy Dev Server v2.0.0 milestone Jun 4, 2024
@zachleat zachleat added bug Something isn't working duplicate This issue or pull request already exists labels Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants