[debugger] "Debugging connection was closed. Reason: WebSocket disconnected"

Glitch Help
1

I’m running into a problem with starting up the Chrome debugger. Copying and pasting Glitch’s debugger URL into Chrome starts up DevTools but does not connect to Glitch; it instead shows a dialog saying: “Debugging connection was closed. Reason: WebSocket disconnected”. I have no browser extensions currently enabled.

I looked at a related thread with some similar errors but found no solutions.

My project name is wakeful-canoe. Thanks to anyone who can help.

2 Likes
2

Yeah this has happened to me as well, still waiting for anyone to help

1 Like
3

You should reach out to support@glitch.com for issues about the debugger.

1 Like
4

Do I Email them about it? None of my Debugging seems to work and my glitch debugger is giving me devtools://devtools/bundled/inspector.html?ws:80=api.glitch.com/project/debugger/undefined this <
Says it’s undefined

5

Yep, you should really email them.

6

Thank you for your patience! The websocket disconnection issue with debugging should be resolved, and debugging should be working again. Let us know if ya’ll are still running into issues with debugging and we’ll check it out!

6 Likes
7

Seems like the issue was resolved recently, but I am still running into a “Debugging connection was closed” error when pasting the link into a new tab in Chrome. Am I missing something?

EDIT: I am using Flask. Does that mean I can’t use the debugger?

8

I don’t know. You should be able to. I don’t use Python that often

9

I thinks that’s what it’s saying. Flask would be in Python and not “Node 8.x or above.”

10

It’s a different debugger you’re talking about that you enable with app.run(somestuff,debug = True).

12

doesnt work again I go to devtools://devtools/bundled/devtools_app.html?experiments=true&ws=rigtools.appleflyer.xyz:5506 and it says debugger disconnected and websocket disconnected any help??? please idk how to fix???

13

what are you connecting to in that case