[Bug]: There are no button to run the debugger

priv2024 commented 4 months ago

This issue respects the following points:

[X] 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.
[X] This issue is not already reported on GitHub (I've searched it).
[X] 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.
[X] I agree to follow OpenBullet's Code of Conduct.
[X] This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.

Description of the bug

I am using the latest version of Openbullet 0.3.1 (it also occurs in 0.3.0).

When editing a Config, in the Stacker page and in the Debugger tab, I am able to define my settings (data, proxy and so on) but there are no "start" button like there was before 0.3.0

Reproduction steps

Start OpenBullet 2 web client
Log in as the admin user
Navigate to Configs
Select any Config. If there are not then create a new config.
Go to Stacker page
There are no button to start the Debugger.

What is the current bug behavior?

There are no button to start the debugger.

What is the expected correct behavior?

There should be a button named "Run" or "Start" like there was before 0.3.0

Version of the client

0.3.1 and 0.3.0

Type of client

Web client

Environment

- OS: Arch Linux
- Virtualization: KVM
- Browser: Firefox 127

OpenBullet2 logs

No response

Client / Browser logs

No response

Relevant screenshots or videos

Capture d’écran du 2024-07-15 17-01-34

Relevant LoliCode if needed

No response

Additional information

No response

openbullet commented 4 months ago

Can you please press F12 to open the browser console (or sometimes CTRL + I) and see if there are errors in it? Because it might be due to an error. Also maybe try restarting OB2 or selecting another config and then reselecting the old one

priv2024 commented 4 months ago

I solved the problem by changing my nginx configuration to allow websockets because I saw errors in the console saying that the connection was failing.

openbullet / OpenBullet2