# \[VS Code\]Repeatedly message "Unable to connect to Pinegrow at http://localhost:40001/editor..." when Pinegrow is not running

**URL:** <https://forum.pinegrow.com/t/vs-code-repeatedly-message-unable-to-connect-to-pinegrow-at-http-localhost-40001-editor-when-pinegrow-is-not-running/4130>\
**Category:** Questions\
**Created:** [May 18, 2020, 9:18am UTC](https://forum.pinegrow.com/t/vs-code-repeatedly-message-unable-to-connect-to-pinegrow-at-http-localhost-40001-editor-when-pinegrow-is-not-running/4130 "2020-05-18T09:18:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Robert](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/robert/32/2509_2.png) [@Robert](https://forum.pinegrow.com/u/Robert)\
**Post date:** [May 18, 2020, 9:18am UTC](https://forum.pinegrow.com/t/vs-code-repeatedly-message-unable-to-connect-to-pinegrow-at-http-localhost-40001-editor-when-pinegrow-is-not-running/4130/1 "2020-05-18T09:18:29Z")

</div>

Most of the time I work with VS Code only.

When I start VS Code with the Pinegrow plugin installed and active, I see the message “Unable to connect to Pinegrow at [http://localhost:40001/editor](http://localhost:40001/editor)…” after a short while. In all open editor windows. This keeps repeating itself (I don’t know at which interval though). I can only prevent this from happening when I disable the Pinegrow plugin.

**Is there a better way ?**

I would prefer the Pinegrow plugin to make one attempt, then optionally display this message.  
And then (through a button in the UI) to manually check for Pinegrow, after starting Pinegrow a few hours later.

ADDED screenshot :

 ![Unabel-to-connect-to-Pinegrow_20200515_083645](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/1/1b39112c049f6ce52a1c18a2d3f61e4326ecdf1c.png)