All of a sudden the WS chrome plugin decided to stop connectiong.
I have WS open, I have my JS config set to debug the address http://localhost:63342..//testControl.html
and the WS options are set to localhost and port is 63342
yet when I start debug, WS at the bottom of the debug pane stagnates saying "Waiting for connection from JetBrains IDE Support extension for Chrome.
Please ensure you have installed the extension or see
I've reinstalled the WS plugin but no luck.
I don't get how this can all of a sudden just stop working.
I also noticed that I am able to get a successful connection from within WS proxy settings which tells me WS is able to connect to the Browser I think:
yet when I load that page which loads ok, the WS Plugin shows greyed out still in Chrome. The port and host match in the WS plugin.
Also in the past when I had started debug, WS would launch a new tab in Chrome and run that url. Now when I start debug, it opens a NEW chrome instance instead of just adding a new tab in my existing Chrome instance and when it opens a NEW window/instance it doesn't bring up any url, it just starts up Chrome with blank in the address.
No idea why WS decided to go awal on me and I've tried all I can think of here. Reingstalled WS itself, reinstalled the Plugin, cleared Chrome cache, cleared WS's cache, yada yada.
Noticed if I debug with FireFox, the WS plugin works fine and I can connect and Debug and step through code in WS.