Spy-JS in WebStorm does not capture

Question

I am using WebStorm 8 with Spy-js integration
(more details http://blog.jetbrains.com/webstorm/2014/04/spy-js-webstorm-secret-service/ )

When I start SpyJS from the Run IDE configuration, I cannot get it to capture requests

When I access the URL through Local Proxy mode, http://localhost:3546/?spy-js=localhost:9000 it works, but with its limitations ... (more info https://github.com/spy- js / spy-js # local-proxy )

The system proxy seems to be configured correctly:

Content http://localhost:3546/spy-js-proxy.pac -

 function FindProxyForURL(url, host) { return "PROXY localhost:3546; DIRECT"; } 

---

Trace Proxy Log from WebStorm

 /usr/local/bin/node /opt/homebrew-cask/Caskroom/webstorm/8.0.0/WebStorm.app/plugins/spy-js/server/spy.js --port=3546 session store created: /var/folders/gm/r9vjzd1926v4sxdv54c9tl240000gn/T/spy-js-session114324-29723-1xl36wv Starting 8 workers.. info: socket.io started spy-js has started, proxy is available at http://localhost:3546 session (qzj9e): new session created: qzj9e session (qzj9e): dynamic config created: /var/folders/gm/r9vjzd1926v4sxdv54c9tl240000gn/T/114324-29723-1yo5izj.js session (qzj9e): new session started: qzj9e Worker 29770 ready. Worker 29768 ready. Worker 29769 ready. Worker 29771 ready. Worker 29773 ready. Worker 29772 ready. Worker 29774 ready. Worker 29775 ready. proxy connection issue: socket hang up 

Answer 1

First, try clearing the URL to trace field (optional), restart the trace session, and force the page to refresh. If this works, it could be a problem with the URL (try using localhost instead of 0.0.0.0).

In addition, if you use Chrome, when starting a trace session, make sure that the chrome: // net-internals / # proxy page "Effective proxy settings" uses spy-js-proxy.pac (if not, try the settings application again or removal of a bad proxy list on the page, if any).

Answer 2

Disable chromatic extensions that affect proxy settings.

I used the Chrome VPN extension, and this affected the settings of the chrome proxy (I did not see the PAC script: http://localhost:3546/spy-js-proxy.pac in chrome: // net-internals / # proxy, and re-settings did not help).
A simple shutdown helped, now everything works well.