openbullet / openbullet/OpenBullet2

[Bug]: Unable to run Node

Open
#1,152 2 comments 0 reactions 1 assignee View on GitHub

@openbullet is already working on this.

Since Mar 1, 2025.

bug lib:rurilib
Dominant language
C#
Stars
2.4k
Forks
602
PR merge metrics
No merged PRs in 30d

Description

This issue respects the following points:
  • This is a bug, not a question or a configuration issue; Please visit our forum first to troubleshoot with volunteers, before creating a report. The links can be found here.
  • This issue is not already reported on GitHub (I've searched it).
  • I'm using an up to date version of OpenBullet2. We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
  • I agree to follow OpenBullet's Code of Conduct.
  • This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.
Description of the bug

Whenever I try to run any node Script I get an error and BOT returns ERROR

Reproduction steps
  1. Start OB2
  2. Open a config that has a Node Script
  3. Try to run config in stacker
What is the current bug behavior?

Logs show this error.

Script (InvokeNode) <<
[Executing block Script] ConnectionException: Process with ID 2983214 exited before connecting.

What is the expected correct behavior?

Script to be able to run.

Version of the client

0.3.2

Type of client

Web client

Environment
- OS: Pop!_OS 22.04 LTS x86_64
- Virtualization:
- Browser: Brave (Chrominium: 132.0.6834.111)
OpenBullet2 logs

Client / Browser logs

No response

Relevant screenshots or videos

No response

Relevant LoliCode if needed

Additional information

I have tried to see logs but I couldn't find anything relevant.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.