-
Notifications
You must be signed in to change notification settings - Fork 334
wrangler dev: panicked at 'Failed to connect to devtools instance' #1510
Comments
I have the same issue:
|
This is now happening every minute. I have now observed my WiFi icon flicker into no internet connection icon in my Windows Taskbar right as the error happened. Adding some e2e tests with unstable internet connection would be a great first step in diagnosing the problem. |
Yea I have this very often as well. Did not happen as much with old wrangler version: v1.10.x |
I'm having this problem on Linux (Ubuntu) on 1.11.0, if I downgrade to 1.10.0 it works perfectly. |
Same problem for me on macOS 10.15, this Issue is open since August, can't someone finally fix this? It's super annoying. 😩 |
Same problem with different version and stack Is there some temp workaround for it. Can't start developing it at all currently $ cat /etc/os-release
$ wrangler --version
$ RUST_BACKTRACE=full wrangler dev
|
same issue: |
Exact same issues as above. There's no work around and we can't work like this... |
For me it worked to go back to 1.10.0 and restart it several times. With 1.10.0 it seemed to fail only every 4th run or so |
I have this error on macOS Big Sur 11.1 |
I have this error running |
Downgrading to |
Tried with |
Also getting this error, tried I can work around it by:
Does this work for anyone else? |
@ags799 Yep. I've been doing that too. But it only works for a little while. |
Installed @cloudflare/wrangler@1.13.0, now getting this error every time:
Downgrading like @aleclarson did to 1.10.3 seems to work. |
🤦 I think I switched switched off WebSockets in the Network configuration panel. Once I switched it on everything immediately worked again (with the periodic panic later on…). |
Oh, that's the reason? Lifesaver, thanks! |
I ran into a similar issue when both |
same issue reverting to my
|
This issue has been automatically marked as stale because it has not had recent activity in the last 180 days. It will be closed if no further activity occurs in the next week. Please feel free to comment if you'd like it to remain open, and thank you for your contributions. |
I just wanted to rerun an older project of mine, and same happens for me randomly when trying to run wrangler dev |
Please try running your Workers project with the latest Wrangler ( |
🐛 Bug Report
Environment
rustc -V
: rustc 1.44.1 (c7087fe00 2020-06-17)node -v
: v14.5.0wrangler -V
: wrangler 1.10.3wrangler.toml
Steps to reproduce
If I leave
wrangler dev
running for a long time sometimes this happens. It is unclear for me why. It may be my unstable internet connection, but still if so, I'd expect for wrangler to keep retrying until the connection is restored or something like that for a more graceful experience.What did you expect to see?
What did you see instead?
message 'Nieznany host' means 'unknown host'
With
FULL
backtrace, this is right after starting the command, and my internet connection seemed fine.Another one:
The text was updated successfully, but these errors were encountered: