search

kdzwinel / betwixt

:zap: Web Debugging Proxy based on Chrome DevTools Network panel.
MIT License
4.54k stars 125 forks source link

nothing gets captured #20

Closed zinking closed 8 years ago

zinking commented 8 years ago

after started and setting the proxy. I get nothing captured.

log screen is filled with FEConnection error: Connection not ready, message not sent.

I am using the node 5.1 on macosx

kdzwinel commented 8 years ago

I've seen that happen to me. Backend (node script) is not able to connect with the frontend (devtools). It tries to do so via localhost:1337, maybe this port is blocked on your machine?

In the future, we probably should get rid of websocket connection all together and use internal electron communication.

dgospodarets commented 8 years ago

Hey @kdzwinel are you applying Web Proxy after betwixt has been started?

kdzwinel commented 8 years ago

hey @dgospodarets - the issue that @zinking has is not related with the proxy, it's related with communication between front-end (devtools) and back-end(node). It will be fixed via #23. Are you seeing the same issue?

Proxy starts as soon as app starts. It does so on port 8008. It doesn't meter (from what I've tested) when you set the proxy in the system settings (at least on OSX).

shospodarets commented 8 years ago

@kdzwinel yep, I'm seeing the same issue. Works only when Web Proxy is activated after starting betwixt

kdzwinel commented 8 years ago

ok, I'm moving this discussion to #24 as it's different than error reported by OP.

@malyw @damoonrashidi please provide more details in #24 .

kdzwinel commented 8 years ago

@zinking this should be fixed now, backend and frontend no longer use websocket to talk to each other.