# org.sonar.plugins.javascript.nodejs.NodeCommandException: Failed to start server

**URL:** <https://community.sonarsource.com/t/org-sonar-plugins-javascript-nodejs-nodecommandexception-failed-to-start-server/99434>\
**Category:** Eclipse\
**Created:** [September 18, 2023, 2:45pm UTC](https://community.sonarsource.com/t/org-sonar-plugins-javascript-nodejs-nodecommandexception-failed-to-start-server/99434 "2023-09-18T14:45:42Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![anon67236913](https://avatars.discourse-cdn.com/v4/letter/a/c37758/32.png) [@anon67236913](https://community.sonarsource.com/u/anon67236913)\
**Post date:** [November 28, 2023, 2:45pm UTC](https://community.sonarsource.com/t/org-sonar-plugins-javascript-nodejs-nodecommandexception-failed-to-start-server/99434/36 "2023-11-28T14:45:51Z")

</div>

Hi Victor,

thanks for your patience and your support !  
Finally i’ve found the reason and the solution.

> [@victor.diez](#):
>
> SonarLint uses HTTP protocol to communicate with the Node.js server. Can you check if that port is actually accessible?

That triggered checkin me the network connnection settings.

 ![2023-11-28_15h28_21](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/1/7/17c7477c31c48963c05ffa3c57fb4b3bcde0324b.png)

It seems Eclipse automatically slurps the Windows system settings.

Setting the Active Provider to either Direct or Manual works.  
I choosed Direct which results in …\configuration.settings\org.eclipse.core.net.prefs

> eclipse.preferences.version=1  
> org.eclipse.core.net.hasMigrated=true  
> proxiesEnabled=false  
> systemProxiesEnabled=false

Now the analysis of the small testfile Person.js works as expected.

But Sonarlint Console shows

it takes 1,5 mins to deploy the bridge server  
it takes another 15 secs until the 7 issues for this really small file are seen in the on-the-fly view

which is enormous.

Is it really necessary to redeploy the bridge server every time ?  
It always seems to be deleted from `<workspace>\.sonarlint\default` when Eclipse is closed.

Wouldn’t it be sufficient to only delete when Sonarlint is updated !?  
With Sonarlint for IntelliJ the test with the same small Person.js is quicker.

Gilbert

---

<div class="post-metadata">

**Author:** ![victor.diez](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/victor.diez/32/38525_2.png) [@victor.diez](https://community.sonarsource.com/u/victor.diez)\
**Post date:** [December 5, 2023, 1:33pm UTC](https://community.sonarsource.com/t/org-sonar-plugins-javascript-nodejs-nodecommandexception-failed-to-start-server/99434/42 "2023-12-05T13:33:36Z")

</div>

Hello @anon67236913,

thanks for your feedback. We are aware that the current deployment is not optimal. We have created an internal ticket to improve that.

Cheers,  
Victor

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/system/32/31083_2.png) [@system](https://community.sonarsource.com/u/system)\
**Post date:** [December 14, 2023, 6:04pm UTC](https://community.sonarsource.com/t/org-sonar-plugins-javascript-nodejs-nodecommandexception-failed-to-start-server/99434/45 "2023-12-14T18:04:57Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

[Previous page](https://community.sonarsource.com/t/org-sonar-plugins-javascript-nodejs-nodecommandexception-failed-to-start-server/99434.md?page=1)