ECONNREFUSED 127.0.0.1:6080

I could not try debugger.html because of below error on

> "npm start"

debugger.html@0.0.6 start /Users/shanmuv/Desktop/Training/debugger.html
start-dev-server

Listening for WS on *:9000
Will proxy to TCP on *:6080 on first WS connection
Protocol messages can be logged by enabling logging.firefoxProtocol in your local.json config
Hot Reloading can be enabled by adding "hotReloading": true to your local.json config
Development Server Listening at http://localhost:8000
View debugger examples at http://localhost:7999
[BABEL] Note: The code generator has deoptimised the styling of "/Users/shanmuv/Desktop/Training/debugger.html/packages/devtools-sham-modules/sham/css-property-db.js" as it exceeds the max of "100KB".
TCP connection failed: Error: connect ECONNREFUSED 127.0.0.1:6080
WS connection closed, disconnected from TCP

Please consider this as a low priority issue.

I wanted to give Debugger.html and I followed steps mentioned in the README and above is the error I got.

[wldcordeiro]

Odd, looks like you may have something else using that port?

I tried killing all the process using 8000. and there were no process that was using 6080.

Which port should I try killing ?

Also, I am able to see some content at http://localhost:7999/

One more information. I get below message only when I Open http://localhost:8000/ Whilst opening http://localhost:7999/ doesnt throw any error and it gives me some page.

TCP connection failed: Error: connect ECONNREFUSED 127.0.0.1:6080
WS connection closed, disconnected from TCP

[wldcordeiro]

@imvetri try opening the Firefox Developer Toolbar (Shift+F2) and typing listen 6080 then go to localhost:8000

Okay. I'll try that and update the thread.

On a curious note, am I not following the steps mentioned in readme?

[wldcordeiro]

@imvetri sometimes the steps in the readme don't work for specific cases, I know that for me I often have to enable the port listening because of the Firefox configuration I run.

I think I didn't follow the steps as instructed. After some hard tries following worked for me.

1. npm install
2. firefox -> about:config -> make firefox debuggable -> restart
3. npm start
4. firefox ->debug console -> listen 6080
5. hit http://localhost:8000/
6. a page with "about:config" and "Firefox Debugger" opens
7. Click "Firefox Debugger" -> no response in Firefox
8. start from step 5 in Chrome. -> debugger appears 👯‍♂️

@wldcordeiro I have following questions.

1. I think this is not a bug, Its simply because I didn't follow the steps correctly.(hence closing this)
2. Is the above setup sufficient to start contributions?

Update: I couldn't see any page on click of "Firefox Debugger" in both firefox(v48) and firefox nightly.

[montogeek]

I am hitting this issue in OSX Sierra, nothing is running in any of the ports used by the debugger

Log:

> debugger.html@0.0.6 start /Users/montogeek/Infinite/Lov/debugger.html
> start-dev-server

Listening for WS on *:9000
Will proxy to TCP on *:6080 on first WS connection
Protocol messages can be logged by enabling logging.firefoxProtocol in your local.json config
Hot Reloading can be enabled by adding "hotReloading": true to your local.json config
Development Server Listening at http://localhost:8000
View debugger examples at http://localhost:7999
[BABEL] Note: The code generator has deoptimised the styling of "/Users/montogeek/Infinite/Lov/debugger.html/packages/devtools-sham-modules/sham/css-property-db.js" as it exceeds the max of "100KB".
TCP connection failed: Error: connect ECONNREFUSED 127.0.0.1:6080
WS connection closed, disconnected from TCP
TCP connection failed: Error: connect ECONNREFUSED 127.0.0.1:6080
WS connection closed, disconnected from TCP

When opening http://localhost:8000, I get a 500 error:
http://localhost:8000/get?url=http://localhost:9222/json/list with response: ECONNREFUSED

[jasonLaster]

don't worry about that. that's the dev-server trying to connect with chrome.

I have a PR that cleans that up so it's more clear.