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

3.7.0 - net::ERR_CONNECTION_RESET 200 [WSL2, Docker] #118

Closed
or2e opened this issue Aug 28, 2023 · 17 comments
Closed

3.7.0 - net::ERR_CONNECTION_RESET 200 [WSL2, Docker] #118

or2e opened this issue Aug 28, 2023 · 17 comments

Comments

@or2e
Copy link

or2e commented Aug 28, 2023

Environment

  • Operating System: Linux
  • Node Version: v18.17.0
  • Nuxt Version: 3.7.0
  • Nitro Version: 2.6.2
  • Package Manager: pnpm@8.7.0
  • Builder: vite

Reproduction

I can't figure out exactly what's wrong yet, I'll try to disable custom modules and plugins, but it's probably not the problem.
Possibly similar issue: vitejs/vite#14190

Describe the bug

Nuxt 3.7.0
3.7.mp4
Nuxt 3.6.5
3.6.5.mp4

Additional context

No response

Logs

No response

@danielroe
Copy link
Member

I think this is likely related to new default listening behaviour. You can try running nuxi --host.

cc: @pi0

@pi0
Copy link
Member

pi0 commented Aug 29, 2023

Listening on loopback interfaces shouldn't cause something like this. Can you please improve reproduction steps? 🙏🏼

@github-actions
Copy link

Would you be able to provide a reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritise it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

We have a couple of templates for starting with a minimal reproduction:

👉 https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz
👉 https://codesandbox.io/s/github/nuxt/starter/v3-codesandbox

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

@or2e
Copy link
Author

or2e commented Aug 29, 2023

@pi0
The problem is reproduced with a "blank" project
https://github.com/or2e/nuxt-sandbox/tree/main

Nuxt 3.7.0 sandbox
370-sandbox.mp4
Win11 + WSL2 + VSCode DevContainer
WSL2 
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.3 LTS
Release:        22.04
Codename:       jammy
Docker
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

@pi0 pi0 transferred this issue from nuxt/nuxt Aug 29, 2023
@pi0
Copy link
Member

pi0 commented Aug 29, 2023

Thanks. Moving to CLI to keep track.

@pi0
Copy link
Member

pi0 commented Aug 30, 2023

Hi @or2e . Can you please try with latest 3.7.3 if can still reproduce?

@or2e
Copy link
Author

or2e commented Aug 30, 2023

@pi0 hi ;)

Sadly, I can't confirm the fix. The problem continues to occur

env

image

Operating System: Linux
Node Version:     v18.17.0
Nuxt Version:     3.7.0
CLI Version:      3.7.3
Nitro Version:    2.6.2
Package Manager:  pnpm@8.7.0

@or2e
Copy link
Author

or2e commented Sep 10, 2023

this recipe nuxt/nuxt#22823 (reply in thread) didn't work for me.

@dosstx
Copy link

dosstx commented Sep 11, 2023

Spent a few days trying to debug this and even searched the issues here and did not see it until someone specifically linked this page for me. Thanks for the heads up! I confirm that simply changing from localhost:3000 to 127.0.0.1:3000 is the fix for me.

Heck, Nuxt even suggests that as the local host when u see the CLI:

Nuxt 3.7.1 with Nitro 2.6.3                                                                                                                                   
  ➜ Local:    http://127.0.0.1:3000/   //<-----------------
  ➜ Network:  use --host to expose

@or2e or2e changed the title 3.7.0 - net::ERR_CONNECTION_RESET 200 3.7.0 - net::ERR_CONNECTION_RESET 200 [WSL2, Docker] Sep 11, 2023
@or2e
Copy link
Author

or2e commented Sep 11, 2023

@dosstx
It didn't work for me ;(
npx nuxi dev --host 127.0.0.1

@or2e
Copy link
Author

or2e commented Sep 14, 2023

keep track #186

@or2e or2e closed this as completed Sep 14, 2023
@pi0
Copy link
Member

pi0 commented Sep 14, 2023

@or2e can you please try npx nuxi-edge@latest dev on your env to see if it resolves your issue?

@or2e
Copy link
Author

or2e commented Sep 14, 2023

@pi0 gladly!

Details

image

@or2e
Copy link
Author

or2e commented Sep 14, 2023

@pi0 gladly!

Details
image

I mean, the problem remains.
if needed, I can provide an environment (discord, AnyDesk)

@pi0
Copy link
Member

pi0 commented Sep 15, 2023

Feel free to DM me in discord (pi0).

@Manusan42
Copy link

I have the same setup with the same problem. Using VSCode with devcontainer (Windows 10 - WSL2).
I have nuxt 3.7.4 and also tried npx nuxi-edge@latest dev.
I often get (sometimes multiple) net::ERR_CONTENT_LENGTH_MISMATCH 200 of random css/js/woff2 resources.

Is there any new information about this? I just started with nuxt/vue and it's a bit frustrating.

@or2e
Copy link
Author

or2e commented Oct 8, 2023

@Manusan42
#181

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants